# Auto Requirements Pipeline Completion Checklist

Use this checklist to validate the pipeline completed successfully.

## Artifact Validation

- [ ] **Requirements Analysis** — `{planning_artifacts}/requirements-analysis.md` exists and is complete
- [ ] **Architecture Analysis** — `{planning_artifacts}/current-architecture-analysis.md` exists and is complete
- [ ] **PRD Created** — `{planning_artifacts}/prd.md` exists with all required sections
- [ ] **PRD Validated** — PRD passed validation (all critical checks passed)
- [ ] **Epics Created** — `{planning_artifacts}/epics.md` exists with epic and story breakdown
- [ ] **Architecture Designed** — `{planning_artifacts}/architecture.md` exists with technical design

## Quality Validation

- [ ] **Requirements Traceability** — Every requirement in req.md is addressed in the PRD
- [ ] **Architecture Alignment** — Architecture design accounts for existing codebase patterns
- [ ] **Epic Coverage** — All PRD features are covered by at least one epic
- [ ] **Story Completeness** — Each epic has at least one user story with acceptance criteria
- [ ] **No Orphaned Requirements** — No requirements left unaddressed

## Pipeline-Level Validation

- [ ] **All Steps Completed** — Steps 1-8 all executed successfully
- [ ] **No HALT Conditions** — Pipeline completed without unresolved halts
- [ ] **Completion Report Generated** — Final summary with all output paths listed
- [ ] **Status File Generated** — `{planning_artifacts}/pipeline-status.json` exists with machine-readable completion data (including `warnings` array and `readiness_status`)
- [ ] **Workflow Prerequisites Verified** — All delegated workflows (create-prd, validate-prd, create-epics, create-architecture) were verified as accessible in step-01 before delegation
- [ ] **Implementation Readiness Verdict Recorded** — `{readiness_status}` is one of: `ready`, `gaps`, `blocked`, or `not_checked` (when the optional readiness skill is not installed)
- [ ] **Warning Prefix Tags Used** — Every entry in `pipeline-status.json.warnings[]` begins with a canonical `[step-NN]` prefix tag drawn from the dictionary in `workflow.md` → "Warning Prefix-Tag Convention". An empty list `[]` is also a pass. No entry omits the prefix, no entry has more than one prefix, and no entry is double-prefixed (a downstream `[phase-1]` wrap by `auto-full-pipeline/step-05-finalize` is additive — the original `[step-NN]` tag is preserved in this pipeline's own `pipeline-status.json`).
- [ ] **Traceability Verification Executed** — step-08 section 2.4 ran the lightweight cross-document traceability check (req → PRD → epics → architecture). Either (a) no orphans were found and no `[step-08] Traceability orphan...` warnings appear in `pipeline-status.json.warnings[]`, OR (b) orphans were found and explicitly logged with `[step-08] Traceability orphan detected: ...` entries, OR (c) the check was skipped due to inconsistent ID conventions and exactly one `[step-08] Traceability verification skipped...` summary warning is present. The check is best-effort and surfacing-only — its result is advisory, not gating.
