---
name: minimalist-sprint-planning
description: Use when selected user stories need an executable implementation plan with tasks, tests, dependencies, risks, a timebox, and a Definition of Done.
---

# Minimalist Sprint Planning

Turn the selected sprint scope into executable work. Plan the increment, not the
entire product backlog.

## Produce

Resolve sprint-plan.md and verification.md from <plugin-root>/templates/ and
use <plugin-root>/references/artifact-contracts.md for field names.

Complete the sprint record and, when useful, create plan.md and tasks.md. Include:

- Sprint Goal and timebox;
- selected story IDs only;
- one task list per selected story;
- acceptance criterion covered by each task;
- test or evidence expected from each task;
- dependencies and risk controls;
- implementation order;
- Definition of Done;
- demonstration path;
- explicit exclusions.

A task has one observable result and a clear story ID. Prefer vertical slices
that can be checked independently. If a task serves no selected story, remove it
or classify it as an approved scope change.

## Planning sequence

1. Read the selected stories and their acceptance criteria.
2. Identify the smallest end-to-end slice for the Sprint Goal.
3. Write the failing test or verification intent before implementation where the
   technology and change permit it.
4. Decompose only the work needed for that slice.
5. Name dependencies, risks, and the evidence that will reduce them.
6. Order tasks so an early task exposes the most important uncertainty.
7. Define the demonstration and acceptance path.
8. Record what will not be built in this sprint.

## Definition of Done

Use the project-specific Definition of Done when one exists. Otherwise require:

- acceptance criteria checked;
- relevant tests or checks executed with fresh results;
- no unresolved failure hidden by a status label;
- increment demonstrable;
- story and sprint history updated;
- review decision still pending until the user evaluates the increment.

“Code compiles” is not a complete Definition of Done.

## Gate

Planning is ready for execution when every task points to a selected story,
every selected story has acceptance evidence, the order is executable, risks have
owners or mitigations, and exclusions are explicit.

If planning reveals that the Sprint Goal does not fit the timebox, return to
minimalist-sprint-selection and reduce scope. Do not enlarge the sprint to save
the plan.

## Handoff

Pass plan.md or the completed sprint record to minimalist-sprint-execution.
Preserve the exact selected IDs and exclusions.