Sprint Planner

Automatically decompose complex epics into structured sprint tasks with story points, AC, and dependency maps.

Install
cmdop skills install agensi-sprint-planner

The Sprint Planner skill decomposes high-level feature requests and epics into structured, execution-ready sprint plans. Given a description such as “build a payment gateway integration,” it generates atomic, actionable tasks scoped so that one developer can finish each in one to three days. Every task includes story points assigned through a structured Fibonacci rubric, explicit acceptance criteria, and a developer role designation such as Frontend, Backend, Fullstack, or DevOps. The skill analyzes dependencies to ensure foundational tasks like data modeling are scheduled before user interface implementation, and it uses industry-standard velocity calculations to propose a realistic timeline. When complexity or risk is high, it flags the item for further refinement rather than assigning a misleading estimate. The final deliverable is a SPRINT_PLAN.md file that can be committed directly to a repository or pasted into project tracking systems such as Jira or Linear. By automating the breakdown and estimation phase, the skill aims to reduce the overhead of sprint planning within the software development lifecycle.

Use cases

  • Break down an epic like "payment gateway integration" into atomic tasks with story points and acceptance criteria
  • Generate a dependency-sequenced sprint plan that orders backend data modeling before frontend UI work
  • Produce a SPRINT_PLAN.md file ready to commit to a repo or import into Jira or Linear
  • Assign Frontend, Backend, Fullstack, or DevOps roles to tasks for resource planning
  • Flag high-risk or overly complex items that need refinement before estimation

When to use it

  • You need to turn informal feature requests into structured sprint tasks
  • Your team spends significant time on manual estimation and breakdown during sprint planning
  • You want a markdown sprint plan that integrates with Jira, Linear, or Git repositories

When not to use it

  • You require integration with a specific project management API rather than markdown export
  • Your workflow does not use story points, Fibonacci estimation, or role-based assignments
  • You need real-time collaboration or editing features not described in the skill