sprint-plan

Generates sprint plans and status reports from milestones, backlogs, and risk registers.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/onemanking/the-operator --skill sprint-plan-onemanking
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sprint-plan
Source: https://github.com/onemanking/the-operator/tree/main/.github/skills/sprint-plan
Command: npx skills add https://github.com/onemanking/the-operator --skill sprint-plan-onemanking

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Planning a sprint requires manually gathering context from milestones, previous sprints, design documents, and risk registers, which is time-consuming and error-prone. This Skill automates that context gathering and produces a structured sprint plan or status report. ## Core Features & Use Cases - Sprint Plan Generation: Creates a full sprint plan with goals, capacity calculations, prioritized task tables (Must/Should/Nice to Have), carryover items, and risk assessments. - Status Reporting: Produces progress reports with completion percentages, burndown assessment, blockers, and emerging risks. - Context-Aware Planning: Pulls input from production milestones, previous sprints, design documents tagged as ready, and the risk register. - Use Case: A producer starting Sprint 4 invokes the skill with 'new' to automatically assemble a plan based on the current milestone, last sprint's velocity, and ready design features. ## Quick Start Ask the assistant to generate a new sprint plan based on the current milestone and previous sprint data.

Frequently Asked Questions about sprint-plan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a sprint plan from existing project documents?

Invoke the skill with the 'new' argument. It reads the current milestone from production/milestones/, the previous sprint for velocity and carryover, design documents tagged as ready, and the risk register, then outputs a structured sprint plan in Markdown.

How do I create a sprint status report?

Invoke the skill with the 'status' argument. It generates a report showing completed, in-progress, not-started, and blocked tasks, plus a burndown assessment and any emerging risks identified during the sprint.

What inputs does sprint planning need to work?

The skill expects milestone files in production/milestones/, prior sprint files in production/sprints/, design documents in design/gdd/ tagged as ready for implementation, and a risk register in production/risk-register/.

Can the sprint plan account for team capacity and buffer time?

Yes. The generated plan includes a capacity section that calculates total days, reserves a 20% buffer for unplanned work, and reports the remaining available days for scheduled tasks.

What are the limitations of automated sprint planning?

The plan quality depends on the accuracy of milestone documents, design readiness tags, and the risk register. It does not estimate tasks autonomously beyond the provided context, so estimates and priorities still need producer review.