---
name: minimalist-specification
description: Use when an approved outcome needs bounded requirements, acceptance criteria, explicit exclusions, risks, dependencies, or a smallest valuable increment before story creation.
---

# Minimalist Specification

Turn an approved initiative into a bounded specification. Define what must be
true for value to exist and what is deliberately outside the current scope.

## Read

Use initiative.md or the equivalent discovery record. Resolve the reference
contracts and templates from <plugin-root>/references/ and
<plugin-root>/templates/, not from the caller's current directory. If the
initiative is missing or its outcome is not approved, return to
minimalist-brainstorming.

## Produce

Create spec.md with:

- feature identity and decision-maker;
- user and value statement;
- included behavior;
- excluded behavior;
- testable acceptance criteria;
- smallest demonstrable increment;
- risks, dependencies, and constraints;
- candidate story themes;
- approval decision.

Write acceptance criteria as observable behavior. Each criterion must make clear
the starting condition, action, and expected result. Keep implementation choices
out unless they are a constraint or a decision required to preserve existing
behavior.

## Minimalist filter

For every proposed requirement, classify it as:

- necessary to prove the outcome;
- risk-reducing;
- useful learning for the next iteration;
- deferred;
- removable.

Remove or defer requirements that do not support the current increment. Preserve
their reason in the exclusions or decision record.

## Gate

The specification is ready for story mapping when:

- one outcome is prioritized;
- scope and exclusions are explicit;
- acceptance criteria can be tested or demonstrated;
- dependencies and risks are visible;
- the smallest valuable increment is clear;
- the decision-maker has approved the boundary.

Do not create a complete product specification when the feature route can prove
value with a smaller slice.

## Handoff

Pass spec.md to minimalist-story-mapping. Include the exact acceptance criteria,
exclusions, and constraints; do not force the next skill to reconstruct them from
conversation history.