create-github-action-workflow-specification

Create a comprehensive specification for the GitHub Actions workflow: ${input:WorkflowFile} . This specification serves as a specification for the workflow's behavior, requirements, and constraints. It must be implementation-agnostic, focusing on what the workflow accomplishes rather than how it's implemented. Save as: /spec/spec-process-cicd-[workflow-name].md For workflows with 5+ jobs, use subgraphs: Focus on creating a specification that serves as both documentation and a template for workflow updates. - Token Efficiency : Use concise language without sacrificing clarity - Structured Data : Leverage tables, lists, and diagrams for dense information - Semantic Clarity : Use precise terminology consistently throughout - Implementation Abstraction : Avoid specific syntax, commands, or tool versions - Maintainability : Design for easy updates as workflow evolves - Timeout : [Maximum execution time] - Concurrency : [Parallel execution limits] - Resource Limits : [Memory/CPU constraints] - Runner Requirements : [OS/hardware needs] - Network Access : [External connectivity needs] - Permissions : [Required access levels] - Success Rate : [Target percentage] - Execution Time : [Target duration] - Resource Usage : [Monitoring approach] - Execution Logs : [Retention policy] - Approval Gates : [Required approvals] - Change Control : [Update process] - Access Control : [Permission...