pipeline-finalize

name	pipeline-finalize
description	Use after review-and-plan to verify the full pipeline ran, implementation aligns with the spec, final gates pass, and human plus agent journey coverage exists.

Pipeline Finalize

Stage 6: review -> finalize.

This is a hard closeout gate. Do not declare a pass unless pipeline evidence, alignment, review closure, journey coverage, and gates are all clean.

Process

1. Confirm pipeline evidence:
   • spec.md exists.
   • plan.md exists.
   • tasks.yaml exists and all tasks are done.
   • Every task file exists.
   • Review summary.md, validation.md, and implementation-plan.md exist.
2. Check review closure:
   • Confirm findings are fixed, deferred by explicit decision, or absent.
   • If code changed after review, require review evidence to be refreshed.
3. Audit alignment:
   • Compare implementation against spec success criteria.
   • Confirm plan outcomes and task invariants are represented in the final implementation.
   • Reject public contract drift.
4. Audit journey coverage:
   • Require a human workflow test or documented executable check.
   • Require an agent/headless workflow test or documented executable check.
5. Run mandatory gates:
   • Feature final_gate from tasks.yaml.
   • Contract/codegen/docs/UI gates when the changed surface requires them.

Blocking Rules

Block finalization if artifacts are missing, tasks are incomplete, review findings remain unresolved, implementation contradicts the spec, journey coverage is missing, or any required gate fails or is skipped.

Output

Write .pipeline/<feature>/finalize.md:

# Finalize: <Feature>

## Result
PASS | BLOCKED

## Pipeline Evidence

## Alignment

## Journey Coverage

## Gates
| Command | Result | Notes |
|---|---|---|

## Remaining Blockers