pmatch

Verifying codebase alignment with a design specification involves comparing the source-of-truth document against implementation files. The tool orchestrates matcher agents to parse both inputs using Read, Glob, and Grep, generating a consensus report with matched items, gaps, and an overall verdict.

Plan-implementation alignment validation checks a project plan against an actual codebase to catch gaps or mismatches early. It ensures required deliverables are covered by scanning source and target artifacts, deduplicating claims, and flagging ambiguities in a markdown report.

Generating an alignment report between requirements and source code requires executing the validation command with the document path and target directory. Matcher agents scan inputs, merge findings, and produce a detailed markdown report showing matched items, gaps, and an overall verdict.

You can validate an entire codebase directory against a specification document. The validation leverages Glob and Grep tools to parse the full implementation directory, orchestrating matcher agents to scan and compare it comprehensively against the source-of-truth document.

Alignment validation works for sanity-checking documentation against a repository. It compares documentation as the source-of-truth against repository files, using matcher agents to identify mismatches, missing information, or extra implementation details not covered in the docs.

The best way to catch gaps between a design and its implementation is automated consensus scoring. Multiple matcher agents scan the design specification and codebase, deduplicate findings, and flag mismatches or ambiguities, producing a detailed markdown report for early detection.