# Auto Story Pipeline Completion Checklist

Use this checklist to validate the pipeline completed successfully for each story.

## Per-Story Validation

- [ ] **Story Created** — Story file exists at `{implementation_artifacts}/{story_key}.md`
- [ ] **Story Validated** — PM validation passed (GO decision, readiness score >= 7/10)
- [ ] **Implementation Complete** — All tasks/subtasks marked [x] in story file
- [ ] **Tests Pass** — All unit, integration, and regression tests pass
- [ ] **Code Review Passed** — All CRITICAL, HIGH and MEDIUM issues resolved (per step-05 §4 pass criteria; LOW issues may remain as documented tech debt)
- [ ] **QA Test Passed** — All acceptance criteria verified with real data
- [ ] **Status Updated** — Story status set to "done" in story file
- [ ] **Sprint Status Synced** — `sprint-status.yaml` updated with "done" for story key

## Pipeline-Level Validation

> **Scope note:** ASP is the **single-story** pipeline — it processes one story (or resumes one story) per run. The items below validate this run's effect on `sprint-status.yaml`. For batch-wide validation that **every** backlog story has been processed, see `auto-story-pipeline-batch/checklist.md` → "Scheduler-Level Validation".

- [ ] **This Story Processed** — The story selected for this run (`{current_story_key}`) has progressed through all required steps and `sprint-status.yaml` reflects its final `"done"` status. (Batch-wide "every backlog story processed" validation lives in ASPB's checklist.)
- [ ] **No Orphaned States** — No stories stuck in intermediate states (in-progress, review)
- [ ] **Sprint Status Consistent** — All story statuses in sprint-status.yaml match story files
- [ ] **Fix Iterations Within Limits** — No story exceeded `{max_fix_iterations}` fix iterations (default: 5, configurable via config.yaml)
- [ ] **Epic Completion Verified** — All epics where every story is "done" have been marked "done" in sprint-status.yaml
- [ ] **Sprint-Status Write Safe** — step-08 used temp-file-then-rename to update sprint-status.yaml (no half-written file)
- [ ] **Machine-Readable Status Written** — `{implementation_artifacts}/story-pipeline-status.json` exists with full run metadata (mode, story_key, fix_iterations_used, epic_just_completed, sprint_snapshot, warnings)
- [ ] **Steps Completed Rendered Unambiguously** — Final report shows `{steps_completed}` as `N / 9` (resume runs may legitimately have N < 9)
- [ ] **Warning Prefix Tags Used** — Every entry in `story-pipeline-status.json.warnings[]` starts with a canonical `[step-NN]` prefix tag (dictionary lives in `workflow.md` → "Warning Prefix-Tag Convention"; empty list `[]` also passes)
- [ ] **AC-Test Traceability Executed** — step-08 §1.5 ran (either no `[step-08] AC-test traceability orphan...` warnings were emitted, or they were explicitly logged for downstream review, or the verification was skipped with exactly one `[step-08] AC-test traceability check skipped...` summary entry). Advisory-only; orphans do not block done-status.
