Critical Journey Documentation
Create one canonical journey record in the repository's established product-documentation location.
Workflow
- Confirm what makes the journey critical, its actor, goal, trigger, scope, owner, risk, and canonical document location.
- Inspect existing requirements, code, contracts, tests, telemetry, and documentation; reuse repository identifiers and terminology.
- Split multiple actors or goals into separate records only when independently useful.
- Document the ordered journey, decisions, state changes, success, meaningful failures, recovery, ownership, and evidence links.
- Add acceptance, telemetry, blueprint, portfolio, coverage, or story-map sections only when a named consumer or delivery gate requires them.
- Record unresolved facts only when the task permits them and names the decision owner and resolution condition.
- Use
text-improve on the completed record without changing agreed contracts, identifiers, or domain terms.
Acceptance sections describe product acceptance; test-design owns executable tests. Telemetry sections record agreed contracts rather than inventing events. repo-context-document owns implemented-system flows under docs/context/; rollout-readiness-review owns deployment readiness; spec-update owns semantic decisions.
Do not create a parallel canonical document, mandatory identifier system, speculative telemetry, or an artifact suite by default.
Finish when the record has evidence links, named ownership, explicit unknowns, and only sections with current consumers.
1---2name: critical-journey-document3description: Create one concise evidence-linked product journey record for one actor pursuing one goal. Use when product behavior needs traceable ownership, acceptance, telemetry, or service-flow documentation for a current decision or delivery gate.4---56# Critical Journey Documentation78Create one canonical journey record in the repository's established product-documentation location.910## Workflow11121. Confirm what makes the journey critical, its actor, goal, trigger, scope, owner, risk, and canonical document location.132. Inspect existing requirements, code, contracts, tests, telemetry, and documentation; reuse repository identifiers and terminology.143. Split multiple actors or goals into separate records only when independently useful.154. Document the ordered journey, decisions, state changes, success, meaningful failures, recovery, ownership, and evidence links.165. Add acceptance, telemetry, blueprint, portfolio, coverage, or story-map sections only when a named consumer or delivery gate requires them.176. Record unresolved facts only when the task permits them and names the decision owner and resolution condition.187. Use `text-improve` on the completed record without changing agreed contracts, identifiers, or domain terms.1920Acceptance sections describe product acceptance; `test-design` owns executable tests. Telemetry sections record agreed contracts rather than inventing events. `repo-context-document` owns implemented-system flows under `docs/context/`; `rollout-readiness-review` owns deployment readiness; `spec-update` owns semantic decisions.2122Do not create a parallel canonical document, mandatory identifier system, speculative telemetry, or an artifact suite by default.2324Finish when the record has evidence links, named ownership, explicit unknowns, and only sections with current consumers.
yarlson