Sprint Plan

Sprint Plan

Use this skill to produce a concise sprint planning document for engineering or product alignment.

Workflow

1. Identify the sprint outcome in one sentence.
2. Add a concise bullet summary beneath the goal.
3. State why this work matters now, using one concrete example if available.
4. Separate current gaps from proposed work.
5. Keep scope explicit: In Scope and Out Of Scope.
6. Break work into 4-8 workstreams.
7. For each workstream, include Goal, Deliverables, and Done when.
8. Add decision principles only when they clarify tradeoffs.
9. End with definition of done, success metrics, and risks/open questions.

Avoid day-by-day plans unless the user explicitly asks for scheduling.

Template

# 

## Sprint Goal


## Summary

- 
- 
- 

## Context


## Current Gaps

- 

## In Scope

- 

## Out Of Scope

- 

## Workstreams

### 1. 

Goal: 

Deliverables:

- 

Done when: 

### 2. 

Goal: 

Deliverables:

- 

Done when: 

## Decision Principles

- 

## Definition Of Done

- 

## Success Metrics

- 

## Risks / Open Questions

- 

Style

• Be direct and readable.
• Prefer concise bullets over long paragraphs.
• Keep the doc focused on alignment, not exhaustive execution detail.
• Avoid grand strategy unless the sprint depends on it.
• Preserve user-provided language when it is clearer than generic planning jargon.