workflow-end

<!-- PROMPT-ENHANCE:STEP-TASK-ANCHOR:START -->

[BLOCKING] Execute skill steps in declared order. NEVER skip, reorder, or merge steps without explicit user approval. [BLOCKING] Before each step or sub-skill call, update task tracking: set in_progress when step starts, set completed when step ends. [BLOCKING] Every completed/skipped step MUST include brief evidence or explicit skip reason. [BLOCKING] If Task tools are unavailable, create and maintain an equivalent step-by-step plan tracker with the same status transitions.

<!-- PROMPT-ENHANCE:STEP-TASK-ANCHOR:END -->

Quick Summary

Goal: Close the active workflow with evidence-backed coverage, spec-sync, graph, and baseline checks (reusing the run's own coverage and spec-sync evidence when it exists); deliver a diff-gated one-way comprehension recap unless /watzup follows and owns it, then retain per-session recovery state until explicit /clear (which alone deletes it).

Summary:

• Purpose: Penultimate closure step before /watzup: close workflow evidence, trigger fresh detection next prompt, and explain changes without a diff reread.
• Main steps (ordered): (0) outcome-gate evidence check — block on missing evidence; (1) integration-test coverage check (reuse the run's cited coverage evidence, else scan); (2) spec ↔ TDD-test sync gate (spec-tdd-test-sync-gate) BEFORE task-completion verification (reuse a fresh in-run spec [mode=sync] result, else run it); (3) sync graph if .code-graph/ exists; (4) verify owned baseline and classify unowned/ambiguous changes; (5) verify preceding tasks; (6) print diff-gated recap (what / purpose / how / why) unless /watzup follows; (7) close only exact owned baseline and verify closed/deletionFailures; (8) announce Workflow [name] completed; (9) confirm state retained until explicit /clear.
• Blocking gates: missing evidence for any outcome gate (step 0) → refuse to close and name the gap; coverage gap OR unadjudicated spec-vs-code drift → MUST surface via AskUserQuestion; NEVER silent-skip or report completed while drift is unadjudicated. Baseline closure requires qualified, user-accepted ambiguity, or explicit N/A.
• Modes and terminal behavior: recap only with a diff; recap one-way/no quiz/no block. Completion is model-driven only after all tasks, sync recorded synced-or-accepted-as-is, and baseline closure qualified, user-accepted, or N/A; per-session state is retained until explicit /clear (which alone deletes it); no hook clears CK_TMP_DIR/workflow/{sessionId}.json except session-init on explicit /clear.

Workflow:

1. Detect — classify scope and target artifacts.
2. Execute — perform required evidence-backed steps.
3. Explain — print diff-gated recap (skip only with no changes, or when /watzup follows and owns it).
4. Verify — confirm constraints, output quality, and completion evidence.

Key Rules:

• MUST ATTENTION first check evidence for every outcome gate (step 0); review-converged runs review-receipt.cjs check and reads its JSON, or accepts a cited review report logged as a review-report deviation-log line. Missing evidence blocks the close.
• MUST ATTENTION when the workflow produced a diff and no /watzup occurrence follows, print the comprehension recap (what changed / purpose / how it works / why) — NEVER fully skip it when changes exist and nothing else owns the recap. A following /watzup owns it (its Session summary); record covered by watzup — if that /watzup is later skipped, the recap duty stays with workflow-end: print it at that point.
• MUST ATTENTION reuse the run's own evidence for steps 1–2 only when it is cited and fresh (step 0 evidence names the report or occurrence, no source/test/spec edit since); with no such evidence — standalone /workflow-end, or the run skipped that step — run the full check.
• MUST ATTENTION the recap is one-way — NO quiz, NO teach-back, NEVER blocks. Keep it concise and complete enough to explain the workflow result without routing to another skill.
• MUST ATTENTION run the spec ↔ TDD-test sync gate (spec-tdd-test-sync-gate) BEFORE task-completion verification when behavior-changing files are in the diff — the workflow MUST NOT report completed while a behavior-vs-spec divergence is unadjudicated; surface unsynced drift via AskUserQuestion, never silent-close.
• MUST ATTENTION close the workflow-owned baseline before announcing completion: run the bounded workflow-baseline.cjs report for the recorded run ID, classify owned versus unowned changes, and report AMBIGUOUS for unowned paths, endpoint-only ownership, or intermediate commits. Persist the final report and resolve the recap step (printed, or skipped as no changes to explain / covered by watzup) before running workflow-baseline.cjs close for that exact run; verify closed and deletionFailures, preserve any parent run, and never use broad cleanup. Never replace this with git diff attribution, claim every dirty file, restore user work, or read expired/sensitive snapshots.
• MUST ATTENTION keep claims evidence-based (file:line) with confidence >80% to act.
• MUST ATTENTION keep task tracking updated as each step starts/completes.
• MUST ATTENTION define success criteria before execution and loop until observable verification passes.
• MUST ATTENTION when creating/reviewing specs or tests, name Business Intent / Invariant Guarded or the protected business intent/invariant and ensure the test would fail if that intent breaks.
• NEVER skip mandatory workflow or skill gates.

When This Runs

This skill closes workflow state. In workflows with /watzup, it runs after final verification/docs and before /watzup, which owns the recap; with no /watzup after it, print the one-way recap itself. Then retain per-session tracking until explicit /clear.

NOT for: manual mid-workflow invocation; switch via /start-workflow.

---

What To Do

0. Outcome-gate evidence check (FIRST step, before anything else; BR-GWF-03). Read the run's outcomeGates from its Tier-2 manifest ([] → record N/A — no outcome gates declared). Cite evidence for every gate; a gate whose when does not hold is N/A with that reason. Missing evidence for any gate blocks the close: keep this task in_progress, name the gate and the missing evidence, and suggest the step that produces it.
   • review-converged: run node .claude/hooks/lib/review-receipt.cjs check (default target worktree) and read its JSON, not its exit code (it exits 0 when no receipt matches). ERROR blocks. CLEAN passes (nothing to review). CHANGED with a non-null review passes (a receipt); a skip receipt alone is not a receipt. CHANGED with review: null passes only when the run cites the review report written by the occurrence that satisfies this gate (a step whose skill is in the gate's outcomeGates[].satisfiedBy, e.g. workflow-review-changes, pbi --mode=review or integration-test --mode=review; an existing file under the project, e.g. in tmp/reports/): append <that occurrence-id> · review-report · <report path> to the run's deviation log tmp/workflow-runs/<runId>/skips.md and continue — never block or ask when a report is cited. Read the report's final status and compare its time with the run's last change-producing occurrence: when the final status is not converged/PASS, or the report predates that occurrence, the line's evidence says so (<report path> — not converged: <final status> or <report path> — stale: predates <occurrence-id>) and the close message repeats it. Neither a receipt nor a cited report → block, name the gap, and suggest running the review. When the close rests on a report, the close message states that a commit still needs the receipt (/workflow-review-changes --fix-loop mints it). On a host that cannot run the command, the cited report is the evidence, logged the same way — say so.
   • tests-pass: cite the test command and its output; those tests cover every behaviour the run changed and ran green in this run (BR-GWF-15). Unrelated green tests are not evidence. The green run must be on the final tree: an edit to any source or test file after the cited run invalidates it, so re-run the verify (SYNC:verify-last-order) before closing. Also cite the mutation-check result (mutants killed n/n, or N/A — reason); a code-changing run with neither is missing evidence.
   • spec-synced: cite the spec-sync diff, or a "no behavior change" statement with the diff stat.
   • root-cause-traced: cite the root-cause trace (file:line) from the investigation report.
   • plan-approved: cite the workflow's declared plan approval evidence, such as /plan --mode=validate, an explicit user decision, or another registry-declared approval gate.
   • run-closed: proved by steps 4–7 of this skill; confirm at step 9.
   • Plan checklist rows (optional evidence input, only when a /plan --mode=execute occurrence ran nested in this run AND its plan.md carries a ## Quality Gates & Concerns Checklist; otherwise record N/A — no plan checklist and add no gate): read that checklist and close each row the execute walk recorded PENDING-PARENT: <step> — evidence expected: … using the evidence cited for the gates above (test run, mutation result, review receipt or report). A row whose evidence is present → PASS; a row whose evidence is missing or failed → FAIL, which blocks the close like any missing gate evidence: name the row and suggest the step that produces it. A nested execute run covers one plan phase, so also scan the same checklist for rows still recorded DEFERRED-BY-PLAN: phase <n> at close: name them as unfinished plan phases: <n…> and treat them like missing gate evidence — the close is refused and surfaced via AskUserQuestion (Option A: "Continue the remaining phases" (Recommended); Option B: "Accept as-is — I will record the

---

Content truncated.