Skip to content
← Back to the kit
Usage: /dwp-verify [plan <name> | all]

dwp-verify

Objectively check repository and plan conformance — read-only.

What it does

dwp-verify checks, mechanically, whether a repository is AI-first (DeepWorkPlan-conformant) and whether its plans are well-formed, then reports pass/fail. It changes nothing.

Usage

/dwp-verify            # verify the repository
/dwp-verify plan auth  # also verify a specific plan
/dwp-verify all        # repository + every plan

Behavior

  1. Check the repository: AGENTS.md with real, runnable commands; CLAUDE.md resolution; docs/ categories; .agents/ catalog matching disk; thin dwp-* delegators; gitignored .dwp/ and tmp/; a resolvable skill.
  2. Check a plan (when requested): every task has acceptance criteria and a validation gate, progress is persisted, the recorded Final Review is present (its security pass included), and tasks re-anchor to the goal.
  3. Report CONFORMANT or NOT CONFORMANT with each failure listed.
  4. Offer to capture gaps as a Deep Work Plan; never fix silently.

Generation-specific plan validation. The repository provenance checker accepts the current DWP standard 6.0.0, but plan checks remain generation-specific. A v6 plan is identified from its contract pointer, contract.json, or a contracts/ revision chain and is checked with the v6 contract, journal, and ledger validators. The retained plan_contract.py checker is v5-only and MUST NOT be run as the v6 plan validator. In v6, state.json is a generated snapshot projection; a mismatch with the journal is a finding. Both generations coexist and neither is migrated during verification.

Aliases

  • dwp:verify