39 lines
1.4 KiB
Markdown
39 lines
1.4 KiB
Markdown
|
---
|
||
|
|
id: story-breakdown
|
||
|
|
name: Story Breakdown
|
||
|
|
version: 1.0.0
|
||
|
|
summary: Break a spec into a set of small, independently shippable child stories.
|
||
|
|
roles: [product-owner]
|
||
|
|
inputs: An approved spec (problem, goal, acceptance criteria).
|
||
|
|
outputs: A list of child stories, each with a title and acceptance criteria, ready to become board tasks.
|
||
|
|
actions:
|
||
|
|
- name: propose-child-stories
|
||
|
|
risk: draft
|
||
|
|
description: Propose child stories as draft tasks under the parent (held for review).
|
||
|
|
tools: []
|
||
|
|
context: [house-style, product-docs]
|
||
|
|
visibility: public
|
||
|
|
min_tier: free
|
||
|
|
golden_tests:
|
||
|
|
- input: |
|
||
|
|
Spec: a logout button in the header that ends the session and returns to sign-in.
|
||
|
|
expected: |
|
||
|
|
1. Add a logout button to the header (shown only when authenticated).
|
||
|
|
2. Clear the session and redirect to /login on click.
|
||
|
|
3. Hide the button when signed out.
|
||
|
|
---
|
||
|
|
|
||
|
|
# Story Breakdown
|
||
|
|
|
||
|
|
You are the Product Owner. Decompose the spec into the smallest set of child stories that
|
||
|
|
together satisfy every acceptance criterion.
|
||
|
|
|
||
|
|
Rules:
|
||
|
|
|
||
|
|
- Each story is independently shippable and testable.
|
||
|
|
- Each has a clear title (imperative) and its own acceptance criteria.
|
||
|
|
- Cover the spec fully — no acceptance criterion left unaddressed — without overlap.
|
||
|
|
- Order by dependency where it matters; otherwise by value.
|
||
|
|
|
||
|
|
Return a numbered list. Each item: title, then its acceptance criteria.
|