---
name: minimalist-story-mapping
description: Use when a bounded specification must be decomposed into independent user stories with value, acceptance criteria, dependencies, and traceable history.
---

# Minimalist Story Mapping

Convert the approved specification into candidate stories that can be discussed,
ordered, selected, implemented, and reviewed independently. Keep user value
visible in every story; technical work is supporting detail.

## Produce

Resolve user-story.md and backlog.md from
<plugin-root>/templates/ when creating project records.

Create one stories/US-###-slug.md record per story and update backlog.md. Each
story must include:

- a unique stable ID;
- a user, capability, and value;
- acceptance criteria;
- included and excluded behavior;
- priority and status;
- dependencies;
- links to initiative and specification;
- implementation and review history sections;
- a next action.

Use the smallest story that still delivers recognizable value. A technical task,
database table, or UI fragment is not a user story unless it supports a
reviewable user outcome. A story may contain technical tasks later.

## Slicing rules

Prefer vertical slices that cross the minimum required boundaries. Split a story
when it has multiple independent outcomes, multiple decision-makers, or a
timebox risk. Merge stories only when separate delivery would produce no
meaningful behavior or evidence.

Preserve constraints from spec.md in every affected story. Do not silently
remove security, authorization, compatibility, data, or acceptance requirements
to make a story appear smaller.

## Story quality gate

A story is refined when:

- its value can be explained in one sentence;
- its acceptance criteria are observable;
- its scope and exclusions are explicit;
- its dependencies are named;
- it can be selected without selecting the whole backlog;
- its review result can be recorded independently.

If a story cannot meet the gate, split or return it to specification. Do not
mark it refined merely because it has a title.

## Handoff

Pass the candidate stories and updated backlog to minimalist-backlog-refinement.
The full backlog is a product view; it is not permission to implement every
story in the first sprint.