executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
sprint-plannerTurn a list of user stories or backlog items into a prioritized 2-week sprint plan with effort estimates and capacity check. Use when the user wants to plan a sprint, prioritize stories, or figure out what fits in two weeks.
Independent GitHub snapshot · Automated classification · Original documentation governs
Ask the user:
Then produce:
Sprint goal: [one sentence] Capacity: [N engineers × 10 days = N story points / days available]
| Story | Effort (S/M/L) | Owner hint | Notes |
|---|---|---|---|
| [story] | [S=0.5d, M=1-2d, L=3-5d] | [FE/BE/Full] | [dependency or risk] |
Committed total: [X days] of [Y available]
Stories that are next in priority but can slip to next sprint without breaking the goal.
Stories deliberately deferred — with one-line reason for each.
Risks:
Suggested check-ins: [mid-sprint review suggestion]
Flag any story that is too vague to estimate — ask for clarification before committing it.