Generate sprint plans and status reports from milestones, backlog, capacity, and risks.
npx skills add https://github.com/easonlao/jiazi-game --skill sprint-plan-easonlao
Please help me install this Agent Skill. Skill: sprint-plan Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/sprint-plan Command: npx skills add https://github.com/easonlao/jiazi-game --skill sprint-plan-easonlao
It solves the problem of unclear sprint scope and mismatched capacity by generating a feasible sprint plan and coordinating the required gates (producer feasibility and QA plan availability) using the latest milestone, backlog signals, and risk context.
/qa-plan sprint or clearly blocks test-undefined progression by adding an explicit warning.production/sprint-status.yaml after plan creation so downstream tools (like /sprint-status and /story-done) can operate without markdown parsing.Generate a new sprint plan with a lean review by asking: sprint-plan new --review lean.
High-intent search queries and answers about installing and using this skill.
Generate a sprint plan by synthesizing current production milestones, previous sprint velocity, design docs flagged as ready, and the risk register to produce a feasible sprint scope. Running sprint-plan new initiates plan creation, coordinating backlog signals with capacity context for delivery readiness.
Feasibility gating is a producer review process that checks if proposed stories are realistic against available capacity. You need it when running full review mode, where it performs a PR-SPRINT check and revises the task mix if the proposed sprint stories are unrealistic for the team.
QA plan enforcement detects whether a QA plan exists for the sprint number and either prompts the user to run qa-plan sprint or blocks test-undefined progression by adding an explicit warning. This ensures production-ready delivery by preventing sprints from advancing without test coverage.
Yes, sprint planning writes and updates production/sprint-status.yaml after plan creation, providing a machine-readable format for story tracking. This allows downstream tools like sprint-status and story-done to operate without markdown parsing, enabling automated status reporting.
Yes, creating a sprint plan requires reading production milestones and sprints, scanning design docs for implement-ready items, and checking risk registers. These inputs provide the backlog signals, capacity context, and risk information needed to generate a feasible sprint scope.
Update an existing sprint plan by feeding new risk register information and current milestone data back into the sprint planning workflow. The process synthesizes these signals to refresh the plan, running feasibility checks and updating the sprint-status.yaml file to reflect the adjusted task mix.
pixel-cellarGenerate or update sprint plans from milestones, completed work, and capacity.
co-cddoGenerate sprint-status.yaml from Markdown epic files and story data.
polseguGenerate sprint plans aligned with milestones, capacity, and backlog readiness.
markus41Facilitate Scrum ceremonies and manage sprint backlog with agile estimation.