clavix-verify

Audit code and documentation against PRD and plan requirements.

1|Updated Jan 26, 2026

Search Tags:#documentation #verification #audit #quality-assurance #prd #code-review #tasks.md

Ready to run

npx skills add https://github.com/alysonhower/dupcheck --skill clavix-verify

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: clavix-verify
Source: https://github.com/alysonhower/dupcheck/tree/main/.agent/skills/clavix-verify
Command: npx skills add https://github.com/alysonhower/dupcheck --skill clavix-verify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies that an implementation aligns with the defined PRD and task plan by performing a structured, rule-based audit across documentation and code.

Core Features & Use Cases

Load and compare tasks.md (Plan) and full-prd.md (Requirements) with the actual codebase to identify gaps.
Inspect and analyze source files referenced by the plan to validate coverage and correctness.
Generate prioritized review comments and a consolidated verification report to guide remediation.

Quick Start

Run clavix-verify after implementing features to audit your work against the PRD and plan.

Frequently Asked Questions about clavix-verify

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

FAQPage Schema

How do I verify code implementation against PRD requirements?▼

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.

What is the best way to audit code for compliance with a project plan?▼

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.

How do I check if my source files deviate from the defined tasks.md plan?▼

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.

Can I generate a verification report showing exact file paths for code review findings?▼

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.

When do I need to run a PRD alignment audit on my codebase?▼

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.

What limitations exist when auditing implementation against a PRD and task plan?▼

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.