wf-verifier

Verify built code and documentation against intended design, outputting verification.md.

1|Updated Jan 25, 2026
One-click install
npx skills add https://github.com/JSai23/claude-tooling --skill wf-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wf-verifier
Source: https://github.com/JSai23/claude-tooling/tree/main/compiled/wf/agentskills/wf-verifier
Command: npx skills add https://github.com/JSai23/claude-tooling --skill wf-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that built code, design documents, and living docs meet the intended design and production-readiness criteria.

Core Features & Use Cases

  • Multi-dimensional verification spanning design review, larp detection, code cleanliness, and production readiness.
  • Delegation via Task tool to spawn specialized agents for each verification dimension, then synthesize findings into a unified verification report.
  • Living-doc alignment ensures ARCHITECTURE.md, decisions, and verification artifacts stay in sync with shipped code and docs.

Quick Start

Confirm a completed plan and run the verifier agent to generate design-docs/plans/{name}/verification.md for the current release.

Frequently Asked Questions about wf-verifier

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify built code against design documents for production readiness?

You verify built code against design documents by running an agent that checks design review, larp detection, code cleanliness, and production readiness, outputting a verification.md report alongside your plan.

What is larp detection in software verification?

Larp detection in software verification is a multi-dimensional check that identifies discrepancies between living documentation and the actual shipped code to ensure alignment and quality.

How do I ensure living documentation stays in sync with shipped code?

To ensure living documentation stays in sync, you run a verification agent that aligns ARCHITECTURE.md and decisions with shipped code, then synthesizes findings into a unified verification report.

Can I use the Task tool to coordinate specialized agents for code quality checks?

Yes, you can use the Task tool to spawn specialized agents for each verification dimension, including design review and code cleanliness, and synthesize their findings into a single report.

Do I need a completed plan before running an end-to-end build verification?

Yes, you need a completed plan along with the latest source code and documentation, because the verifier requires access to these to evaluate production readiness and output the verification.md file.

Where does the verification report get saved after checking code cleanliness and design?

The verification report is saved as verification.md alongside the plan in the design-docs/plans/{name}/ directory after the agent completes its multi-dimensional checks.