requirements-gap-finder

Reviews project briefs and PRDs for missing requirements, contradictions, and untestable acceptance criteria.

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/vmitsaras/Agent-Skills --skill requirements-gap-finder-vmitsaras
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: requirements-gap-finder
Source: https://github.com/vmitsaras/Agent-Skills/tree/main/skills/project-planning/requirements-gap-finder
Command: npx skills add https://github.com/vmitsaras/Agent-Skills --skill requirements-gap-finder-vmitsaras

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project briefs and PRDs often contain hidden gaps, unresolved decisions, contradictions, and vague acceptance criteria that only surface during implementation, causing rework and misaligned expectations. This Skill systematically reviews requirements documents before planning begins and converts every finding into an answerable question or decision. ## Core Features & Use Cases - Gap and Contradiction Detection: Identifies missing requirements, unresolved decisions, hidden assumptions, and conflicts between goals, scope, and constraints, each traced to source evidence. - Acceptance Criteria Verifiability Check: Flags subjective or untestable criteria and proposes testable rewrites only when the source supports them. - Prioritized Readiness Verdict: Classifies findings as blocker, high, medium, or low, and issues a readiness verdict scoped to a named next stage. - Use Case: Before handing a feature PRD to engineering, run this Skill to receive a findings table, a decision queue with owners, and a clear verdict on whether the document is ready for estimation. ## Quick Start Review the attached product brief for missing requirements, contradictions, and untestable acceptance criteria, then give me a prioritized findings table and a readiness verdict.

Frequently Asked Questions about requirements-gap-finder

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

FAQPage Schema
How do I find gaps in a product requirements document?▼

Submit the PRD or brief for a structured gap review that maps goals, users, scope, constraints, and acceptance criteria, then flags omissions, contradictions, and unresolved decisions. Each finding includes source evidence, delivery impact, and an answerable clarification question.

How to check if acceptance criteria are testable?▼

Testable acceptance criteria name an observable outcome, relevant conditions, and a clear pass/fail boundary. The review flags subjective terms like fast, intuitive, or seamless when no measurable standard exists, and proposes rewrites only when the source supports them.

When should requirements be reviewed before implementation?▼

Review requirements before roadmap, estimation, design, or implementation begins, and whenever stakeholders disagree about scope or meaning. The review issues a readiness verdict scoped to the specific next stage rather than claiming universal completeness.

What types of requirement gaps does a gap analysis cover?▼

The analysis covers missing actors, error and recovery flows, permissions, data handling, integrations, accessibility, security, performance, migration, and rollback, but only when each category plausibly matters to the project. It avoids adding generic enterprise requirements by default.

Can this review handle conflicting requirements documents?▼

Yes, when multiple artifacts disagree, the review cites each source and reports both sides of the conflict without assuming which is authoritative. It identifies the owner or decision needed to resolve the contradiction.

When should I not use a requirements gap review?▼

Do not use it to create a new brief from a rough idea, to sequence already-stable requirements into an implementation plan, or to compare a plan against completed work. It also does not perform copyediting or summarization without requirements analysis.