Sprint Planner

Most sprints go wrong at planning: the team pulls in more than it can finish, one person ends up on the critical path, and nobody notices until the last two days. This plugin checks the plan against real capacity before the sprint starts.

/plan-sprint reads a backlog (a Markdown table, or a CSV export from Jira, Linear or similar) and a short team file with availability and recent velocity. A bundled Node.js helper works out capacity and shows the arithmetic, then compares it with the proposal. It flags overcommitment, people over their share, items that are not ready or have no estimate, oversized items, and tickets that block others. Claude turns that into a recommended sprint, an order of work and questions for the planning meeting.

/standup drafts yesterday, today and blockers from your commits since the last working day, uncommitted work and TODO comments. /retro groups the team's notes into themes, checks last retro's actions and proposes up to three actions with owners and checks. /burndown draws a text chart with the ideal line, scope changes and a projection.

Inside: four commands, a skill that keeps the backlog, team and progress files up to date, the helper script, and a full sample sprint with the output of every command.

For small dev teams and tech leads. It works on plain files and git only. It does not sync with Jira or other tools, and it cannot know people's skills, so reassignments are suggestions.