start-sprint

Start Sprint Workflow

Usage: /start-sprint <type> or /start-sprint $ARGUMENTS

Sprint Types:

• technical-debt - Address TODO items and tech debt
• feature - Implement new features
• bug-fix - Fix bugs and issues
• documentation - Documentation improvements
• refactoring - Code refactoring sprint

---

📋 Sprint Initialization Workflow

Step 1: Load Context

Read the following context files to understand current state:

# Recent work
cat .claude/context/recent-work.md

# Active TODOs
cat docs-internal/TODO_CATALOG.md

# Testing patterns
cat .claude/context/testing-patterns.md

# Code patterns
cat .claude/context/code-patterns.md

Analyze:

• Recent commits (last 15)
• Current TODO status
• Test coverage status
• Active work areas

---

Step 2: Create Sprint Plan

Use the sprint planning template:

# Copy template to new sprint document
cp .claude/templates/sprint-planning.md docs-internal/SPRINT_PLAN_$(date +%Y%m%d).md

Fill in Sprint Plan:

1. Sprint Type: $ARGUMENTS (technical-debt, feature, etc.)
2. Sprint Duration: Based on scope (1-5 days)
3. Primary Goal: Clear, measurable objective
4. Sprint Backlog: Prioritized items (HIGH/MEDIUM/LOW)
5. Success Criteria: Specific, measurable criteria

---

Step 3: Perform Ultrathink Analysis

For complex sprints, use extended thinking:

For technical-debt sprints:

ultrathink: Analyze all TODO items in docs-internal/TODO_CATALOG.md and recent code.
Create a comprehensive implementation plan with:
1. Categorization by priority (CRITICAL/HIGH/MEDIUM)
2. Effort estimation per item
3. Dependencies and blockers
4. Risk assessment
5. Recommended order of execution

For feature sprints:

ultrathink: Analyze the feature requirements and codebase.
Create a comprehensive technical design with:
1. Architecture approach (ADR if needed)
2. Files to modify vs create
3. Testing strategy
4. Migration/rollback plan
5. Performance and security considerations