plan-sprintlisted

# 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 [