clavix-verify

To verify code implementation against PRD requirements, you run a structured audit that loads `full-prd.md` and `tasks.md`, inspects source files, and outputs severity-labeled findings referencing exact file paths to surface gaps and deviations.

The best way to audit code for compliance with a project plan is to compare `tasks.md` against the actual codebase, inspecting referenced source files to validate coverage and correctness, and generating a consolidated verification report with prioritized review comments.

You check for deviations from the `tasks.md` plan by inspecting source files referenced by the plan, validating coverage and correctness, and producing severity-labeled findings that highlight gaps between the plan and the implementation.

Yes, you can generate a consolidated verification report that references exact file paths for reproducibility, outputs severity-labeled findings, and provides prioritized review comments to guide remediation of gaps between documentation and code.

You need to run a PRD alignment audit after implementing features to ensure your work aligns with the defined PRD and task plan, validating that source files meet requirements and surfacing any deviations that require remediation.

When auditing implementation against a PRD, the audit targets the specified phase by inspecting code and documentation, relying on `tasks.md` and `full-prd.md` to surface gaps and deviations, ensuring compliance through structured, rule-based verification.