user-story-review-doc

name	user-story-review-doc
description	Author compact canonical source for a USER STORY review (artifact_type user-story-review) — acceptance criteria, personas, journey states, dependencies, scope gaps. Produces content-only YAML/JSON validated against the base + user-story overlay schema; render with render-branded-html. Use for PM/design story reviews.

user-story-review-doc

Authors content only for a user-story review. Emit canonical YAML/JSON — no HTML/CSS/JS. Target 2–12 KB. The renderer owns all chrome.

Required & overlay fields

• Base: schema_version: 2, artifact_type: user-story-review, title.
• Overlay: acceptance_criteria[] (required), plus as_a, i_want, so_that, personas[], journey_states[], dependencies[].

Section shape (default)

1. scope — prose: what's in/out of scope, key assumptions.
2. journey — mermaid journey (one diagram, < 40 lines): the shopper/user path.
3. acceptance — table: columns [criterion, status, notes], one row per AC.

Use summary[] for the 2–4 bullet executive summary (scope gaps, open questions). Cite sources in evidence[] as {label, href}.

Widgets (schema v2)

Beyond prose/mermaid/table, sections may use: callout (note/tip/warning/danger), (KPI numbers), , (generic/decision/rejected/persona), , (+), (2–6 alternatives), (collapsible deep-dive), , , . Pick the widget that matches the data — and show restraint: per document; prefer when nothing structural is gained. Give every section a ; pairs small sections side by side under the skin.