Execute Sprint
Execute all tasks for a sprint with parallel execution and synthesis
Loading actions...
Skill content
Main instructions and any bundled files for this skill.
Prompt Playground
1 VariableFill Variables
Preview
--- description: Execute all tasks for a sprint with parallel execution and synthesis argument-hint: [sprint-number] allowed-tools: Task, Read, Write, TodoWrite, Bash --- # Execute Complete Sprint You are executing the `/execute-sprint` command to run all 6 tasks for a sprint. ## Purpose Execute all 6 tasks for a sprint with parallel execution of Tasks 01-05, followed by sequential execution of Task 06 (synthesis), ensuring efficient research completion while maintaining quality. ## Steps to Execute ### Step 1: Validate Sprint Check $1 is valid sprint number 01-99 Verify sprint directory exists: sprints/$1-*/ Verify all 6 task files present Confirm temp directory ready: temp/$1-*/ Validate context files populated ### Step 2: Load Configuration Read config/project-config.yml for max_parallel_tasks, git_enabled settings Read config/sprint-config.yml for sprint metadata Read all context files for skill agents ### Step 3: Initialize Progress Tracking Output verbose startup message: ``` π SPRINT EXECUTION STARTING ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ Sprint: [sprint-name] Number: [sprint-number] Total Tasks: 6 Expected Duration: 30-60 minutes Configuration: β Sprint directory validated β Context files loaded β Output directory ready: temp/[sprint-number]-*/ β Parallel execution enabled (5 tasks simultaneously) Tasks to Execute: 1. Technical Requirements Research 2. Market & Competitive Analysis 3. Solution Architecture Design 4. Certification Pathway Analysis 5. Implementation Roadmap 6. Final Report Synthesis (after tasks 1-5 complete) ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ ``` Create progress tracking list with 6 tasks, mark all as pending initially ### Step 4: Execute Tasks 01-05 in Parallel Output progress message: ``` π PHASE 1: PARALLEL RESEARCH (Tasks 01-05) ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ Launching 5 research agents simultaneously... π¬ Agent 1: Technical Researcher β Analyzing technical requirements, regulations, and SMT feasibility β Output: temp/[sprint]/01-technical/ π Agent 2: Market Analyst β Researching TAM/SAM/SOM, competitors, and customer needs β Output: temp/[sprint]/02-market/ ποΈ Agent 3: Solution Architect β Designing system architecture and POC specifications β Output: temp/[sprint]/03-architecture/ β Agent 4: Compliance Analyst β Researching certification pathways and testing requirements β Output: temp/[sprint]/04-compliance/ πΊοΈ Agent 5: Roadmap Planner β Creating implementation roadmap and partnership strategy β Output: temp/[sprint]/05-roadmap/ Expected completion: 20-40 minutes (agents work in parallel) ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ β³ Research in progress... (updates will appear as agents complete tasks) ``` Launch 5 skill agents concurrently using Task tool: - Task tool β technical-researcher (Task 01) - Task tool β market-analyst (Task 02) - Task tool β solution-architect (Task 03) - Task tool β compliance-analyst (Task 04) - Task tool β roadmap-planner (Task 05) Each agent operates independently, creating research files in temp/$1-*/ ### Step 5: Monitor Parallel Execution Track completion of each skill agent and provide real-time updates: ``` β±οΈ PROGRESS UPDATE [MM:SS elapsed] ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ Agent Status: π¬ Technical Researcher: β Complete (8 files, 12,340 words) π Market Analyst: β³ In Progress (5 files so far...) ποΈ Solution Architect: β³ In Progress (3 files so far...) β Compliance Analyst: β³ Starting research... πΊοΈ Roadmap Planner: β³ Starting research... Overall: 2/5 agents complete (40%) Total files created: 16 ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ ``` Update progress tracking as each task completes Collect file counts and word counts Handle any errors gracefully with detailed error messages When each agent completes, output: ``` β Agent X completed: [Task Name] β Files created: [count] β Total words: [count] β Key finding: [brief summary] ``` ### Step 6: Execute Task 06 (Synthesis) Wait for all Tasks 01-05 to complete Output transition message: ``` β ALL RESEARCH AGENTS COMPLETE ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ Total research files created: [count] Total research words: [count] Research quality: All agents completed successfully π PHASE 2: REPORT SYNTHESIS ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ Starting final report generation... Tasks: 1. Reading all research files from temp/[sprint]/ 2. Analyzing findings across all research areas 3. Applying scoring rubric (0-100 scale) 4. Generating executive summary 5. Creating strategic recommendations 6. Compiling final report (5,000-7,500 words) Expected completion: 5-10 minutes β³ Synthesis in progress... ``` Mark Task 06 as in_progress Launch Task tool β report-synthesizer Report synthesizer reads all temp/$1-*/ files Applies scoring rubric from config/scoring-rubric.yml Generates comprehensive strategic report (5,000-7,500 words) Writes to reports/$1-*-report.md During synthesis, output periodic progress: ``` β±οΈ Synthesis progress... [MM:SS elapsed] β Read 28 research files β Analyzed 45,230 words of research β Calculated opportunity score: 84/100 β Writing executive summary... ``` ### Step 7: Validate Sprint Completion Check all 6 tasks completed successfully Verify research file count meets minimum (25+ files typical) Ensure final report exists and meets length requirement Confirm report includes go/no-go recommendation Validate scoring completed ### Step 8: Git Workflow If git_enabled in config: - Create feature branch: git flow feature start sprint-$1-execution - Stage all generated files: git add temp/$1-*/ reports/$1-*.md - Commit with descriptive message - Finish feature: git flow feature finish sprint-$1-execution - Push to remote: git push origin develop ### Step 9: Generate Sprint Summary Output comprehensive completion summary: ``` β SPRINT COMPLETE ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ Sprint: [sprint-name] Number: [sprint-number] Execution Time: [HH:MM:SS] π Research Output: β Research files created: [count] files β Total research words: [count] words β Final report: reports/[sprint]-report.md ([word-count] words) β Quality validation: PASSED π― Opportunity Assessment: β Overall Score: [score]/100 ([GO/NO-GO/CONDITIONAL]) β Market Opportunity: $[amount] ([timeframe]) β Investment Required: $[amount] ([timeframe]) β Technical Feasibility: [High/Medium/Low] β Recommendation: [brief statement] π Generated Files: β temp/[sprint]/01-technical/ ([X] files) β temp/[sprint]/02-market/ ([X] files) β temp/[sprint]/03-architecture/ ([X] files) β temp/[sprint]/04-compliance/ ([X] files) β temp/[sprint]/05-roadmap/ ([X] files) β reports/[sprint]-report.md π Git Status: β Feature branch created: sprint-[XX]-execution β All files committed β Merged to develop branch ββββββββββββββββββββββββββββββββββββββββββββββββββββββββββ Next Steps: 1. Review report: cat reports/[sprint]-report.md 2. Export findings: /export-findings [sprint-num] pdf 3. Execute next sprint: /execute-sprint [next-num] 4. Compare opportunities: /compare-sprints π Sprint execution successful! ``` List all files created with detailed statistics Provide key findings from report Show opportunity score and recommendation Display execution metrics (time, file count, word count) ### Step 10: Update Configuration Update sprint status in config/sprint-config.yml to "completed" ## Success Criteria - All 6 tasks completed successfully - Minimum 25 research files created - Final report exists (5,000-7,500 words) - Opportunity score calculated (0-100) - Go/no-go recommendation provided - Git commits created (if enabled) ## Error Handling If sprint not found, guide user to run /create-sprint If prerequisites missing, specify what's needed If task execution fails, provide diagnostic info and recovery options ## Expected Output User receives comprehensive sprint summary with file statistics, opportunity score, recommendation, and next steps.
Related Skills
Frontend Typescript Linting.mdc
TypeScript and ESLint rules that MUST be followed when creating, modifying, or reviewing any file under apps/frontend/, including .ts, .tsx, .js, and .jsx files. Also apply when discussing frontend li...
2. Apply Deepthink Protocol (reason about dependencies
risks