vibe-check

Validate product requirements documents for coherence and quality gaps.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/metasaver/claude-marketplace --skill vibe-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vibe-check
Source: https://github.com/metasaver/claude-marketplace/tree/main/plugins/metasaver-core/skills/workflow-steps/vibe-check
Command: npx skills add https://github.com/metasaver/claude-marketplace --skill vibe-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates PRD quality and coherence before the innovation phase, identifying gaps and guiding remediation.

Core Features & Use Cases

  • Coherence checks: Consistency and completeness of PRD.
  • Issue listing: Returns issues and recommendations for next steps.
  • Decision gate: Supports auto-revise or human-in-the-loop remediation.

Quick Start

Run vibe-check after requirements; review coherence results and proceed to innovation or remediation.

Frequently Asked Questions about vibe-check

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

FAQPage Schema
How do I validate PRD quality and catch coherence issues before development starts?

PRD validation identifies quality gaps, consistency problems, and incomplete requirements before innovation begins. vibe-check analyzes your product requirements document, detects coherence issues, lists specific gaps, and provides recommendations for remediation—supporting both auto-revise and manual fix workflows.

What kinds of PRD problems does a quality gate catch?

A PRD quality gate checks internal consistency, requirement specificity, user story completeness with acceptance criteria, and detects gaps across the document. vibe-check produces a coherence verdict, an issues list, and next-step recommendations to guide remediation before proceeding.

Can I automatically fix PRD issues or do I need to revise manually?

vibe-check supports both workflows: auto-revise mode fixes issues automatically, or you can review the issues list and remediate manually. The Skill supports up to two iterations and outputs structured JSON results for tracking changes.

When in the product development cycle should I run a PRD quality check?

Run PRD validation after completing the requirements phase and before innovation starts. This gates quality at the critical handoff point, preventing incomplete or inconsistent requirements from downstream work.

What output does a PRD coherence check produce?

vibe-check produces a coherence verdict indicating overall PRD quality, a structured list of identified issues with context, and recommendations for next steps. Results export as structured JSON for integration into review workflows.