artifact-frontmatterlisted

# Artifact Frontmatter The single schema contract for the pipeline's durable state: every artifact under `docs/plans/<id>/`, its YAML frontmatter, and the design-review record mechanics that gate the DESIGN transition. Phase discipline — what each phase does and when it advances — lives in `skills/qrspi-workflow/SKILL.md`. This skill owns the schema. The schema exists because files are the contract between phases (`skills/principle-files-are-the-contract/SKILL.md`). ## Artifact inventory All phase artifacts live under `docs/plans/<id>/`, where `<id>` is one of: - **Ticket-prefixed**: `<TICKET>-<kebab-topic>` (e.g., `ENG-1234-add-rate-limiting`) - **Date-prefixed**: `<YYYY-MM-DD>-<kebab-topic>` (e.g., `2026-05-01-add-rate-limiting`) The executable definitions of the `<id>` pattern (`ID_RE`) and the phase-file list (`PHASE_FILES`) live in `hooks/session-start-recover.mjs` — that hook is the canon. Reference it rather than forking the pattern here. One definition, one owner, every other surface consults it (`skills/principle-single-source-of-truth/SKILL.md`). | Artifact | Path | Created By | Required? | |-----------|-----------------------------------|-------------------------|-----------| | Task | `docs/plans/<id>/task.md` | questioner agent | yes | | Questions | `docs/plans/<id>/questions.md` | questioner agent | yes | | PRD | `docs/plans/<id>/prd.md` | questioner agen