spk-run-verdict-capture

# spk-run-verdict-capture Use this skill whenever an agent (any of the 13 slash-command harnesses or the shared Agent-Skill harnesses) needs to **record the outcome of a WP review** — approve, reject, or otherwise. It documents the single deterministic seam so verdicts never diverge by harness. ## The authoritative seam The **sole** authority for a WP's review verdict is the `review_result` event in the mission's `status.events.jsonl` (read back via `specify_cli.status.event_sourced_review_result`). The `review-cycle-N.md` render is **non-authoritative prose** — do not hand-edit it to change a verdict, and never treat it as the source of truth. Because the verdict is an event, it is append-only, deterministic, and identical across every agent. ## How to set a verdict (use the CLI — do not write the event by hand) - **Approve** a WP under review: ```bash spec-kitty agent tasks move-task <WP> --to approved --mission <slug> --note "<why>" ``` - **Reject** a WP (send it back with structured feedback): ```bash spec-kitty agent tasks move-task <WP> --to planned \ --review-feedback-file <path/to/review-feedback-N.md> --mission <slug> ``` - **Terminal (done) with an explicit review triple** (reviewer / verdict / reference): ```bash spec-kitty agent status emit <WP> --to done --actor <name> \ --evidence-json '{"review": {"reviewer": "<name>", "verdict": "approved", "reference": "<PR/commit>"}}' ``` Each command emits the `review_result` (or review-beari...