Sprint Planner
Productivitysprint-plannerSprint Planner is an Agent Skill for productivity published in the oxbshw/LLM-Agents-Ecosystem-Handbook repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when planning the next sprint — turns ticket intake + team capacity into a planned sprint with explicit non-goals.
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/oxbshw/LLM-Agents-Ecosystem-Handbook/blob/HEAD/skills/catalog/sprint-planner/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sprint-planner, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Sprint Planner
When to use
- Start of a sprint cycle
- After a re-prioritization mid-cycle
- When intake outpaces capacity and you need a defendable plan
When NOT to use
- Daily standup (different cadence)
- Annual planning (different scope; use
roadmap-synthesizer)
Inputs
| Name | Type | Required | Notes |
|---|---|---|---|
tickets | list / path | yes | candidate work items with priority + estimates |
capacity | object | yes | per-engineer days available |
previous_carry | list | no | items rolling over from last sprint |
commitments | list | no | OKR / stakeholder commitments that must land |
Outputs
sprint-plan.md with: Sprint goal, Committed, Stretch, Non-goals, Risks.
Workflow
- Compute total capacity (days × team)
- Sort candidates: committed → carry → stretch
- Pack to ~85% of capacity (leave room for support / interrupts)
- Identify dependencies between items; surface blockers
- Surface explicit non-goals — what we are not doing this sprint and why
- Risks: anything that would cause spillover
References
Success criteria
- Committed work ≤ 85% of capacity
- Every committed item has an owner and an estimate
- Non-goals section is non-empty
- Risks include at least one "what could derail us"
Failure modes
- Capacity unknown → ask, don't guess
- Tickets without estimates → flag and exclude from "committed"