$npx -y skills add faizkhairi/claude-code-blueprint --skill sprint-planMUST use when user describes a multi-step feature to build, says 'let's build', 'new project', 'let's implement', or when a task clearly requires more than 3 steps and no plan exists yet. Do NOT trigger for simple additions like adding a comment, renaming a variable, or single-fi
| 1 | Create a sprint plan for: $ARGUMENTS |
| 2 | |
| 3 | 1. **Analyze the requirement**: Understand scope, constraints, dependencies |
| 4 | 2. **Check existing code**: Search codebase for related implementations that can be reused |
| 5 | 3. **Break into tasks**: |
| 6 | - Each task should be independently deliverable |
| 7 | - Include file paths that will be modified or created |
| 8 | - Estimate size: S (< 1hr), M (1-4hr), L (4-8hr), XL (> 1 day) |
| 9 | 4. **Sequence tasks**: Identify dependencies, mark blocking tasks, find parallelizable work |
| 10 | 5. **Identify risks**: What could go wrong? What needs clarification? |
| 11 | 6. **Output format**: |
| 12 | |
| 13 | ## Sprint Plan: [Feature Name] |
| 14 | |
| 15 | ### Tasks |
| 16 | | # | Task | Size | Depends On | Files | |
| 17 | |---|------|------|-----------|-------| |
| 18 | | 1 | ... | S | - | path/to/file | |
| 19 | |
| 20 | ### Risks |
| 21 | - [Risk description and mitigation] |
| 22 | |
| 23 | ### Definition of Done |
| 24 | - [ ] All tasks completed |
| 25 | - [ ] Tests written and passing |
| 26 | - [ ] Code reviewed |
| 27 | - [ ] Documentation updated |
| 28 | - [ ] No security vulnerabilities introduced |