How do I install the Check Prd Alignment skill?

Run npx skillmds@latest add tomevault-io/check-prd-alignment in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Check Prd Alignment safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Check Prd Alignment?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Check Prd Alignment free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Check Prd Alignment?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Check Prd Alignment by tomevault-io

Name: Check Prd Alignment
Author: tomevault-io

Check Prd Alignment

Compare current code changes against a PRD to find gaps, deviations, and opportunities. Use before opening a PR, after finishing a feature, or to verify requirement coverage. Use when this capability is needed.

tomevault-io c36882e 2 files · 3.3 KB Updated Sep 17, 2026

File contents

Check PRD alignment

Trigger

User wants to verify their implementation matches the product requirements and find opportunities to better achieve the PRD's goals.

Workflow

Identify what changed — run git diff against the base branch to see all modifications.
Find the relevant PRD:
- Ask the user which PRD to check against.
- Search ChatPRD documents using search_documents with keywords from the branch or commit messages.
- Also check the local prd/ directory for saved specs.
Fetch the full PRD using get_document.
Extract all requirements, acceptance criteria, and — critically — the user and business goals the PRD is trying to achieve.
For each requirement, assess:
- Covered: implemented and matching the spec
- Partial: started but incomplete or missing edge cases
- Missing: not addressed in the current changes
- Deviated: implemented differently than specified
Review the implementation through the lens of the PRD's stated goals. For each goal, identify Opportunity items — places where the UX or implementation could be improved to better achieve the goal. Examples:
- A flow that technically meets the spec but adds unnecessary friction
- An edge case where a better error message or fallback would improve the experience
- A place where the implementation could be more delightful or intuitive than what was specced
- A data model or API design choice that would better support the stated business goal
Produce a coverage report with:
- Requirement-by-requirement status
- Specific code references for covered items
- Actionable notes for gaps and deviations
- Opportunity items tied back to specific PRD goals

Guardrails

Be specific — cite file paths and line ranges, not vague summaries.
Distinguish between intentional trade-offs and accidental omissions.
Don't flag requirements that are explicitly marked as out-of-scope or future work in the PRD.
Keep Opportunity items grounded and actionable — tie each one to a specific PRD goal and explain the concrete improvement.

Output

Alignment report (covered / partial / missing / deviated)
Opportunity items with goal references and suggested improvements
Specific gaps with suggested next steps
Summary of overall coverage

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: check-prd-alignmentdescription: Compare current code changes against a PRD to find gaps, deviations, and opportunities. Use before opening a PR, after finishing a feature, or to verify requirement coverage. Use when this capability is needed.---# Check PRD alignment## TriggerUser wants to verify their implementation matches the product requirements and find opportunities to better achieve the PRD's goals.## Workflow1. Identify what changed — run `git diff` against the base branch to see all modifications.2. Find the relevant PRD: - Ask the user which PRD to check against. - Search ChatPRD documents using `search_documents` with keywords from the branch or commit messages. - Also check the local `prd/` directory for saved specs.3. Fetch the full PRD using `get_document`.4. Extract all requirements, acceptance criteria, and — critically — the user and business goals the PRD is trying to achieve.5. For each requirement, assess: - **Covered**: implemented and matching the spec - **Partial**: started but incomplete or missing edge cases - **Missing**: not addressed in the current changes - **Deviated**: implemented differently than specified6. Review the implementation through the lens of the PRD's stated goals. For each goal, identify **Opportunity** items — places where the UX or implementation could be improved to better achieve the goal. Examples: - A flow that technically meets the spec but adds unnecessary friction - An edge case where a better error message or fallback would improve the experience - A place where the implementation could be more delightful or intuitive than what was specced - A data model or API design choice that would better support the stated business goal7. Produce a coverage report with: - Requirement-by-requirement status - Specific code references for covered items - Actionable notes for gaps and deviations - **Opportunity** items tied back to specific PRD goals## Guardrails- Be specific — cite file paths and line ranges, not vague summaries.- Distinguish between intentional trade-offs and accidental omissions.- Don't flag requirements that are explicitly marked as out-of-scope or future work in the PRD.- Keep **Opportunity** items grounded and actionable — tie each one to a specific PRD goal and explain the concrete improvement.## Output- Alignment report (covered / partial / missing / deviated)- **Opportunity** items with goal references and suggested improvements- Specific gaps with suggested next steps- Summary of overall coverage---> Converted and distributed by [TomeVault](https://tomevault.io/claim/chatprd) — claim your Tome and manage your conversions.

Frequently asked questions