Skip to main content

/sprint - Sprint Management Command

Manage time-boxed sprints for CODITECT projects with velocity tracking and burndown metrics.

Usage

# Create sprint
/sprint create P001 "Sprint 1" --start 2025-12-16 --end 2025-12-30 [--goal "Goal"]

# List sprints
/sprint list [P001] [--status planning|active|completed]

# Show sprint details
/sprint show S01

# Start sprint
/sprint start S01

# End sprint
/sprint end S01

# Sprint burndown
/sprint burndown S01

# Add items to sprint
/sprint add S01 F001 F002 T0001

# Remove from sprint
/sprint remove S01 F001

# Plan sprint (interactive)
/sprint plan S01

# Retrospective
/sprint retro S01

System Prompt

System Prompt

⚠️ EXECUTION DIRECTIVE: When the user invokes this command, you MUST:

  1. IMMEDIATELY execute - no questions, no explanations first
  2. ALWAYS show full output from script/tool execution
  3. ALWAYS provide summary after execution completes

DO NOT:

  • Say "I don't need to take action" - you ALWAYS execute when invoked
  • Ask for confirmation unless requires_confirmation: true in frontmatter
  • Skip execution even if it seems redundant - run it anyway

The user invoking the command IS the confirmation.


You are managing CODITECT sprints using the Work Item Hierarchy system (ADR-006).

ID Convention:

  • Sprints: S{NN} (S01, S12, S23)

Sprint Status: planning, active, completed, cancelled

Key Metrics:

  • Velocity Planned: Story points committed
  • Velocity Actual: Story points completed
  • Burndown: Daily remaining points

Available Actions:

Create Sprint

python3 scripts/work_items.py sprint create "$PROJECT_ID" "$NAME" \
--start "$START_DATE" --end "$END_DATE" --goal "$GOAL"

Start Sprint

python3 scripts/work_items.py sprint start "$SPRINT_ID"

End Sprint

python3 scripts/work_items.py sprint end "$SPRINT_ID"

Sprint Burndown

python3 scripts/work_items.py sprint burndown "$SPRINT_ID"

Add Items to Sprint

python3 scripts/work_items.py sprint add "$SPRINT_ID" $ITEM_IDS

Output Format:

Sprint S01 created successfully.

ID: S01
Name: Sprint 1
Project: P001 (CODITECT v2.0)
Status: planning
Duration: 2025-12-16 to 2025-12-30 (14 days)
Goal: Complete user authentication

Capacity:
Planned: 0 points
Committed: 0 items

Next steps:
/sprint add S01 F001 F002 - Add features
/sprint plan S01 - Interactive planning
/sprint start S01 - Begin sprint

Examples

Create and Plan Sprint

# Create sprint
/sprint create P001 "Sprint 1" --start 2025-12-16 --end 2025-12-30 --goal "MVP Authentication"

# Add work items
/sprint add S01 F001 F002 F003

# Start sprint
/sprint start S01

View Sprint Progress

/sprint show S01

Output:

S01: Sprint 1 (active)
Project: P001 (CODITECT v2.0)
Duration: Dec 16 - Dec 30 (Day 5 of 14)
Goal: MVP Authentication

Progress:
Points: 21/34 (62%)
Items: 8/12 completed
Velocity: 21 (trending: 30)

Work Items:
├── F001: Login Flow (100%) ✓ [8 pts]
├── F002: Registration (100%) ✓ [8 pts]
├── F003: Password Reset (60%) [5 pts]
│ ├── T0010: Email service (100%) ✓
│ ├── T0011: Reset form (100%) ✓
│ └── T0012: Token validation (0%)
└── F004: OAuth (20%) [13 pts]
└── 1/5 tasks complete

Blockers: 1
└── T0015: API credentials pending

Sprint Burndown

/sprint burndown S01

Output:

S01 Burndown (Day 5 of 14)

Points Remaining:
34 |************************************
30 |******************************* ·
25 |************************** ·····
20 |********************* ··········
15 |**************** ··············· ← Actual
13 |************** ················· ← Ideal
10 |*********** ····················
5 |****** ·························
0 +----------------------------------
D1 D2 D3 D4 D5 D6 D7 ... D14

Velocity: 21 pts completed (62%)
Projection: 30 pts by sprint end (88%)
Status: On Track ✓

Sprint Retrospective

/sprint retro S01

Output:

S01 Retrospective

Velocity:
Planned: 34 points
Actual: 30 points (88%)

Completion:
Features: 3/4 (75%)
Tasks: 11/14 (79%)

Time Tracking:
Estimated: 48h
Actual: 52h (+8%)

Carryover:
F004: OAuth Integration (8 pts remaining)

Recommendations:
- Reduce commitment by 10% next sprint
- OAuth blocked 2 days - improve dependency tracking

Success Output

When sprint operation completes:

✅ COMMAND COMPLETE: /sprint
Action: <create|start|end|show>
Sprint: S<NN>
Status: <planning|active|completed>
Velocity: X/Y points (Z%)

Completion Checklist

Before marking complete:

  • Sprint data loaded/created
  • Metrics calculated
  • Status updated
  • Output displayed

Failure Indicators

This command has FAILED if:

  • ❌ Project not found
  • ❌ Invalid sprint ID
  • ❌ Script execution error
  • ❌ No output displayed

When NOT to Use

Do NOT use when:

  • No project exists (create project first)
  • Single task (sprint overhead unnecessary)
  • Just tracking time (use /work-log)

Anti-Patterns (Avoid)

Anti-PatternProblemSolution
OvercommitSprint failsUse velocity data
Skip retroNo improvementAlways run retrospective
Ignore blockersVelocity lossTrack and remove blockers

Principles

This command embodies:

  • #9 Based on Facts - Velocity-based planning
  • #3 Complete Execution - Full sprint lifecycle
  • #6 Clear, Understandable - Visual burndown

Full Standard: CODITECT-STANDARD-AUTOMATION.md


Script: scripts/work_items.py Standard: CODITECT-CORE-STANDARDS/CODITECT-STANDARD-WORK-ITEMS.md Version: 1.0.0