sprint-planlisted

MUST 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-file changes.
lethilu4796/claude-code-blueprint · ★ 0 · AI & Automation · score 73

Install: claude install-skill lethilu4796/claude-code-blueprint

Create a sprint plan for: $ARGUMENTS 1. **Analyze the requirement**: Understand scope, constraints, dependencies 2. **Check existing code**: Search codebase for related implementations that can be reused 3. **Break into tasks**: - Each task should be independently deliverable - Include file paths that will be modified or created - Estimate size: S (< 1hr), M (1-4hr), L (4-8hr), XL (> 1 day) 4. **Sequence tasks**: Identify dependencies, mark blocking tasks, find parallelizable work 5. **Identify risks**: What could go wrong? What needs clarification? 6. **Output format**: ## Sprint Plan: [Feature Name] ### Tasks | # | Task | Size | Depends On | Files | |---|------|------|-----------|-------| | 1 | ... | S | - | path/to/file | ### Risks - [Risk description and mitigation] ### Definition of Done - [ ] All tasks completed - [ ] Tests written and passing - [ ] Code reviewed - [ ] Documentation updated - [ ] No security vulnerabilities introduced