Scrum Master

Scrum Master — Step 6 of Product Pipeline

Goal

Create a realistic, actionable development plan with clear epics, sprints, and estimates.

Input

Read all prior outputs, especially 03-product-requirements.md and 05-architecture.md

Output

Save to product-pipeline/06-sprint-plan.md

Deliverables

1. Epics

Group user stories into epics: | Epic ID | Epic Name | Description | Stories | Priority | |---------|-----------|-------------|---------|----------|

2. Sprint Plan

Assume 2-week sprints. For each sprint:

• Sprint goal
• Stories included
• Story points (Fibonacci: 1, 2, 3, 5, 8, 13)
• Dependencies
• Risks

3. Task Breakdown

For each story, break into technical tasks: | Task ID | Task Name | Assignee Role | Estimate (hours) | Dependencies | |---------|-----------|---------------|------------------|--------------|

4. Definition of Done

• Code complete
• Unit tests passing
• Code reviewed
• Acceptance criteria met
• Documentation updated
• Deployed to staging

5. Velocity Projection

• Estimated team velocity (story points/sprint)
• Total story points
• Projected completion date
• Buffer for unknowns (20%)

6. Risk Register

| Risk | Impact | Probability | Mitigation | |------|--------|-------------|------------|

Output Template

# Sprint Plan: [Project Name]

## Epics
### Epic 1: [Name]
[Description and included stories]

### Epic 2: [Name]
...

## Sprint Plan
### Sprint 1: [Goal]
[Stories and points]

### Sprint 2: [Goal]
...

## Task Breakdown
### Tasks for Sprint 1
| ID | Task | Role | Hours | Depends On |
|----|------|------|-------|------------|

## Definition of Done
[Checklist]

## Velocity Projection
- Estimated velocity: X points/sprint
- Total scope: Y points
- Projected completion: Z sprints (with 20% buffer)

## Risk Register
| Risk | Impact | Probability | Mitigation |
|------|--------|-------------|------------|

## Dependencies
[External dependencies and blockers]

## Notes
[Assumptions about team size and availability]

Rules

• Base estimates on the architecture, not guesses
• Assume a standard team: 1 PM, 1 Designer, 2-3 Devs, 1 QA (adjust if interview brief specifies)
• Keep sprints realistic — don't cram too much in
• Identify dependencies between stories to avoid blockers
• Flag stories with high uncertainty (spike tasks)
• Include setup/infrastructure sprints if needed
• Consider parallel workstreams where possible
• Be conservative with estimates — under-promise, over-deliver

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: itmbastawi
• Source: itmbastawi/product-skill-pack
• License: MIT

Install and usage instructions live in the source repository linked above.