§ reference · skill

validate

Independently re-runs each phase's success criteria against the working tree and emits a pass/fail validation report — catches half-finished phases the implement loop missed.

arguments [plan-path]

§ 01 · purpose

Purpose

A post-implementation audit. validate re-reads the plan, re-runs every - [ ] success-criterion against the actual working tree, and emits a structured report — pass/fail per criterion plus drift notes and follow-up tickets. Trust-but-verify after implement declares done.

§ 02 · when to use

When to use it

implement has finished and you want third-party confirmation of completion.
You suspect drift between the plan's claims and the working tree.
Skip when there is no plan to validate against — there is nothing for validate to anchor on.

§ 03 · inputs

Inputs

Name	Required	Source
`plan path`	no	Path to `.rpiv/artifacts/plans/*.md` — when omitted, recent commits are searched for a plan reference

§ 04 · outputs

Outputs

Artifact	Path	Format
Validation report	`stdout / session message`	structured pass/fail report with drift notes

§ 05 · key steps

Key steps

Discover context — current session OR fresh Why: Validation works either as an immediate audit (same session) or a cold audit (later run). Detecting the mode picks the right evidence-gathering path — session memory vs git log + diff.
Spawn parallel verification agents Why: One general-purpose agent verifies code matches the plan; one verifies it follows codebase conventions. Running both catches "implemented but wrong shape" failures that single-axis checks miss.
Re-run automated verification commands Why: Every plan command (make check test, etc.) is re-run against the working tree, independent of whatever implement claimed. The plan's checklist is treated as a contract to be re-verified, not as ground truth.
Walk each phase and re-check its - [x] claims Why: A checked box without matching code is a drift signal. Drift notes surface mid-phase pivots and unfinished work the implement loop signed off prematurely.
Emit pass/fail report with follow-ups Why: Output is structured for action — every failure gets a follow-up note so nothing falls through the cracks between validation and the next pass.

§ 06 · related skills

upstream implement