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 7.0.0, but plan checks remain generation-specific. A v6 or v7 plan is identified from its manifest’s contract pointer, contract.json, or a contracts/ revision chain and is judged read-only against its own records by conformance.sh --plan: every contract revision validates, the manifest pairs with the contract’s generation, the journal is untorn and valid, an approval cites the live contract, and state.json agrees with the journal projection (a stale snapshot is advisory and is regenerated, never hand-edited). The v5 lifecycle checks apply to v5 and older plans only, and the v5 finalization refuses a v6 or v7 plan. Generations coexist and none is migrated during verification.

Aliases

  • dwp:verify