plan-sprint

Solid

Create a sprint plan for a new development cycle. Use when starting a new sprint, after completing wrapup-sprint, or when initializing Sprint 1 for a new project.

Data & Documents 15 stars 0 forks Updated 1 weeks ago MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
40
Recency 20%
90
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# Plan Sprint Create a sprint plan for a new development cycle. ## When to Use - Starting a new sprint - After completing `wrapup-sprint` for previous sprint - When initializing Sprint 1 for a new project ## Required Inputs 1. **Sprint number** (e.g., 1, 2, 3) 2. **Sprint goal** (1-2 sentence objective) 3. **Deliverables or user stories** with acceptance criteria ## Workflow ### Step 1: Determine Sprint Context Check current project state: ```bash # Get current date date +%Y-%m-%d # Check latest version git describe --tags --abbrev=0 2>/dev/null || echo "No tags yet" # Check previous sprint (if any) ls docs/sprints/sprint-*-plan.md 2>/dev/null | tail -1 # Check current roadmap phase cat docs/roadmap/roadmap.md 2>/dev/null | head -30 ``` Calculate: - **Sprint number**: Previous + 1, or 1 if first sprint - **Target version**: Current patch + 1 (e.g., v0.1.2 → v0.1.3) - **Current phase**: From roadmap (e.g., "Phase 1: Foundation") - **Start date**: Today ### Step 2: Choose Sprint Plan Format Two formats are available. Choose based on project type: - **Minimal** — for technical/infrastructure projects or highly focused sprints: deliverables with acceptance criteria, no user stories - **Structured** — for user-facing projects or projects needing traceability: user stories with acceptance criteria ### Step 3: Create Sprint Plan Create `docs/sprints/sprint-NNNN-plan.md` (4-digit zero-padded, e.g., `sprint-0001-plan.md`): #### Minimal Format ```markdown # Sprint [...

Details

Author
jrjsmrtn
Repository
jrjsmrtn/project-orchestration-skills
Created
8 months ago
Last Updated
1 weeks ago
Language
N/A
License
MIT

Bundled in these plugins

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

sprint-planning

Use when the user wants to plan a sprint before it starts — set the sprint goal, pull committed scope from the backlog and epic tasks.md files, account for carry-over and capacity, and record dependencies, risks, and the sprint definition of done at docs/work/sprint-{id}/plan.md. Triggers on "plan sprint 3", "what should we commit to", "set up the next sprint", "sprint planning". Do NOT use to review a finished sprint (sprint-retro), write stories or task Gherkin (tasks), groom the backlog (backlog-refine), re-sequence delivery phases (roadmap), or sign off an epic (validate).

2 Updated 3 weeks ago
carinyaparc
Web & Frontend Listed

sprint-plan

Plans a sprint — goal, capacity, story selection by priority and dependencies, risks, QA plan link; triages the dependency-update queue (Dependabot/Renovate PRs: green patch/minor merged at sprint start, majors become stories); writes production/sprints/sprint-NN.md and roadmap markers. Use at sprint start.

0 Updated yesterday
gonimar
AI & Automation Listed

sprint-plan

MUST use when user describes a multi-step feature to build, says 'let's build', 'new project', 'let's implement', or when a task clearly requires more than 3 steps and no plan exists yet. Do NOT trigger for simple additions like adding a comment, renaming a variable, or single-file changes. Produces: task breakdown with S/M/L/XL size estimates, dependency ordering, risk analysis, and a Definition of Done checklist; output is a structured markdown plan ready for implementation.

70 Updated 1 months ago
faizkhairi