Files
channel-scope-skic/references/feature-set-completeness.md

22 lines
1.8 KiB
Markdown

# Epic feature-set completeness review
Use when a human asks whether an Epic covers its outcome or its product questions are documented.
## Evidence boundary
Assess the current intended outcome, full user journey, explicit exclusions and cited request. Label the result a proposal, never approval. Shared technical capabilities belong in existing acceptance outcomes unless independently valuable Features are evidenced. Epic approval never approves child Features.
## Review artifact, not duplicate reader sections
Keep the assessment in a governed review artifact linked from the canonical Epic record, not a second mutable completeness table or Canonical product questions section on the concise Epic reader. Record the canonical Scope revision and a journey-to-Feature coverage table:
| User journey outcome | Canonical Feature link | Coverage or gap |
|---|---|---|
| `<OUTCOME>` | `<RESOLVED-RECORD-URL>` | `<EVIDENCE-BOUNDED ASSESSMENT>` |
State shared acceptance expectations, excluded outcomes, any supported new Feature proposal, and the exact human decision needed. Link the Epic-owned canonical Question records; do not introduce a global question register or duplicate question bodies. Conditional approval must retain exact unresolved questions or equivalent conditions as Architecture risks.
## Validation and publication
Test the review's outcome coverage, canonical links, preserved exclusions and proposal label. Test that the Epic reader retains its mandated card and Questions/Features groups without duplicate review sections. Run targeted checks, the required full validation/build and review workflow; never manufacture a Feature to satisfy cadence. Reuse the existing authoritative Scope review when applicable, verify exact-head CI and remote readback, and re-read only approved channels for late substantive decisions.