name: sprint-planning
description: Universal workflow for planning and executing features, bug fixes, and improvements. Works across any tech stack. Enables parallel agent execution with proper task decomposition.
license: MIT
metadata:
author: thesimpleapp
version: "1.0"

Sprint Planning

Universal system for planning sprints, features, and bug fixes.

The Universal Workflow

┌────────────────────────────────────────────────────────────┐
│                    DEVELOPMENT CYCLE                        │
├────────────────────────────────────────────────────────────┤
│  SPEC → DESIGN → TASKS → IMPLEMENT → TEST → SHIP          │
│                                                             │
│  [Human]  [Human+AI]  [AI]    [AI Parallel]  [AI]  [Human] │
└────────────────────────────────────────────────────────────┘

Phase 1: Specification

Feature Template

# Feature: [Name]

## Problem
What user problem are we solving?

## Solution
How are we solving it?

## User Stories
- As a [role], I want [action] so that [benefit]

## Acceptance Criteria
- [ ] Given [context], when [action], then [result]
- [ ] Given [context], when [action], then [result]

## Out of Scope
- What we are NOT building

## Dependencies
- External: [APIs, services]
- Internal: [other features]

## Success Metrics
- How will we measure success?

Bug Report Template

# Bug: [Title]

## Current Behavior
What's happening now?

## Expected Behavior
What should happen?

## Steps to Reproduce
1. Go to...
2. Click...
3. See error...

## Environment
- Device:
- OS:
- App Version:

## Evidence
[Screenshots, logs, error messages]

## Impact
- Severity: Critical / High / Medium / Low
- Users affected: [number or %]

Phase 2: Design

Technical Design Template

# Technical Design: [Feature]

## Overview
[1-2 paragraph summary]

## Architecture

### Components

[Component Diagram]

### Data Flow

User Action → Handler → Service → Repository → Database
↓
Response ← Transform ← Query Result

### Database Changes
```sql
-- New tables/columns

API Changes

POST /api/feature
Body: { ... }
Response: { ... }

Implementation Approach

Files to Create

• [ ] feature/components/NewComponent.tsx
• [ ] feature/hooks/useNewHook.ts

Files to Modify

• [ ] app/router.ts - Add route
• [ ] shared/types.ts - Add types

Testing Strategy

• Unit: [what to unit test]
• Integration: [what to integration test]
• E2E: [user flows to test]

Rollout Plan

1. Deploy to staging
2. QA verification
3. Deploy to production
4. Monitor metrics

## Phase 3: Task Decomposition

### Breaking Down Work

```markdown
## Task Breakdown: [Feature]

### Batch 1 (Parallel Safe)
These tasks have no dependencies on each other:

- [ ] Task 1: Create data models
  - Files: types.ts
  - Est: 30min

- [ ] Task 2: Create API endpoint
  - Files: api/route.ts
  - Est: 1hr

- [ ] Task 3: Create UI components
  - Files: components/*.tsx
  - Est: 2hr

### Batch 2 (Sequential - depends on Batch 1)
These need Batch 1 complete:

- [ ] Task 4: Connect UI to API
  - Files: hooks/useFeature.ts
  - Depends on: Task 1, 2, 3

- [ ] Task 5: Add error handling
  - Files: components/*.tsx
  - Depends on: Task 4

### Batch 3 (Parallel Safe)
Testing can happen in parallel:

- [ ] Task 6: Unit tests for components
- [ ] Task 7: API tests
- [ ] Task 8: E2E tests

Task Template

## Task: [Name]

### Objective
What this task accomplishes

### Files
- Create: [files to create]
- Modify: [files to modify]

### Implementation Steps
1. Step 1
2. Step 2
3. Step 3

### Acceptance Criteria
- [ ] Criteria 1
- [ ] Criteria 2

### Tests Required
- [ ] Test 1
- [ ] Test 2

Phase 4: Implementation

Parallel Execution Rules

SAFE to parallelize:
✓ Different features/modules
✓ Independent components
✓ Separate test files

NOT safe to parallelize:
✗ Shared utilities
✗ Database migrations
✗ Core infrastructure

Agent Assignment

## Implementation Session

### Agent A: Frontend Components
Working on: Batch 1 - Task 3
Status: In Progress

### Agent B: Backend API
Working on: Batch 1 - Task 2
Status: In Progress

### Agent C: Data Layer
Working on: Batch 1 - Task 1
Status: Complete

### Blocked
None

### Next
When Batch 1 complete → Start Batch 2

Phase 5: Testing

Test Categories

Unit Tests        → Single functions/components
Integration Tests → Multiple components together
E2E Tests         → Full user flows

Testing Checklist

## Test Coverage: [Feature]

### Unit Tests
- [ ] Component renders correctly
- [ ] Component handles loading state
- [ ] Component handles error state
- [ ] Hook returns expected data
- [ ] Service functions work correctly

### Integration Tests
- [ ] API endpoint returns correct data
- [ ] Form submission works
- [ ] State updates correctly

### E2E Tests
- [ ] User can complete main flow
- [ ] Error cases are handled
- [ ] Mobile responsive

Phase 6: Shipping

Pre-Ship Checklist

## Pre-Ship: [Feature]

### Code Quality
- [ ] All tests passing
- [ ] No linting errors
- [ ] Types are complete
- [ ] No console.logs
- [ ] Error handling complete

### Review
- [ ] Self-reviewed diff
- [ ] Checked on mobile
- [ ] Tested edge cases

### Documentation
- [ ] README updated if needed
- [ ] API docs updated if needed
- [ ] CHANGELOG updated

### Deployment
- [ ] Staging deploy successful
- [ ] QA sign-off
- [ ] Production deploy
- [ ] Monitoring in place

Commit Strategy

# Feature development
git commit -m "feat(feature): add data models"
git commit -m "feat(feature): add API endpoint"
git commit -m "feat(feature): add UI components"
git commit -m "test(feature): add unit tests"
git commit -m "test(feature): add e2e tests"

# Bug fixes
git commit -m "fix(auth): handle session expiry"
git commit -m "test(auth): add session expiry test"

Sprint Tracking

Sprint Board Template

# Sprint [Number]: [Date Range]

## Goals
- [ ] Goal 1
- [ ] Goal 2

## Backlog
| Task | Status | Assignee | Est | Actual |
|------|--------|----------|-----|--------|
| Feature A | In Progress | Agent A | 4hr | - |
| Bug B | Done | Agent B | 1hr | 45min |
| Feature C | Todo | - | 8hr | - |

## Blockers
- None

## Notes
- [Daily updates]

## Retrospective
### What went well
### What to improve
### Action items

Integration with Other Skills

/project-init        → Set up project standards
/codebase-analysis   → Understand existing code
/sprint-planning     → Plan the work
/flutter-excellence  → Implement Flutter features
/react-excellence    → Implement React features
/supabase-mastery    → Optimize database
/architecture-cleanup → Clean up after