sprint-plan

Solid

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. Produces: task breakdown with S/M/L/XL size estimates, dependency ordering, risk analysis, and a Definition of Done checklist; output is a structured markdown plan ready for implementation.

AI & Automation 67 stars 21 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 82/100

Stars 20%
61
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
48
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

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

Details

Author
faizkhairi
Repository
faizkhairi/claude-code-blueprint
Created
4 months ago
Last Updated
1 weeks ago
Language
Shell
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

sprint-plan

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.

0 Updated 2 days ago
lethilu4796
Code & Development Listed

sprint-planning

Use when the user wants to plan a sprint before it starts — set the sprint goal, pull committed scope from the backlog and epic tasks.md files, account for carry-over and capacity, and record dependencies, risks, and the sprint definition of done at docs/work/sprint-{id}/plan.md. Triggers on "plan sprint 3", "what should we commit to", "set up the next sprint", "sprint planning". Do NOT use to review a finished sprint (sprint-retro), write stories or task Gherkin (tasks), groom the backlog (backlog-refine), re-sequence delivery phases (roadmap), or sign off an epic (validate).

2 Updated yesterday
carinyaparc
AI & Automation Listed

sprint-plan

Creates a sprint plan aligned to requirements phases and progress tracker. Use at sprint start or when scoping the next delivery slice.

0 Updated 1 months ago
rajurayhan