Validate PRD quality and coherence before innovation phase using vibe-check MCP tool. Checks for requirement clarity, user story completeness, and identifies gaps. Returns coherent flag and issues list.
Validates PRD quality and coherence before innovation using a vibe-check MCP tool. Triggers after requirements phase in /architect to check for clarity, completeness, and gaps, preventing wasted effort on incoherent specs.
/plugin marketplace add metasaver/claude-marketplace/plugin install core-claude-plugin@metasaver-marketplaceThis skill inherits all available tools. When active, it can use any tool Claude has access to.
ROOT AGENT ONLY - Uses vibe-check MCP tool, runs only from root agent.
Purpose: Validate PRD coherence before innovation Trigger: After requirements-phase, before innovate-phase Input: PRD content (from requirements-phase) Output: Validation result (coherent, issues, recommendation)
Quality gate using vibe-check MCP tool. Validates: (1) Internal consistency, (2) Clear/specific requirements, (3) User stories with AC, (4) No critical gaps. Prevents wasted innovation effort with incoherent PRD.
When: /architect only (skipped for /build and /audit with clearer requirements)
{projectFolder}/prd.mdvibe_check({ prdContent, projectContext? })coherent (boolean), issues (array), recommendation ("proceed" | "revise")| Dimension | Checks |
|---|---|
| Coherence | PRD makes sense as a whole |
| Clarity | Requirements specific and measurable |
| Completeness | All sections present |
| Stories | Acceptance criteria present |
| Gaps | Nothing missing or unclear |
| Conflicts | No contradictions |
{
"status": "passed" | "failed",
"coherent": true | false,
"issues": [
"User story prj-epc-003 missing acceptance criteria",
"Requirement R-005 is vague - 'fast performance' needs quantification",
"Gap: No error handling strategy defined"
],
"recommendation": "proceed" | "revise",
"iterations": 1
}
Failed:
Issues: prj-epc-003 missing AC, R-005 vague ("fast" needs metrics),
No error handling, Conflict: R-002 real-time vs R-007 batch
Action: AUTO (BA fixes) or MANUAL (user guidance)?
Passed:
✓ Coherent ✓ Clear ✓ Complete ✓ No gaps → Proceeding to innovation
| Issue | BA Fix |
|---|---|
| Missing AC | Add to affected stories |
| Vague requirements | Quantify with metrics |
| Conflicts | Resolve (ask user if needed) |
| Missing sections | Add based on context |
| Error handling gap | Add strategy |
Called by: /architect (Phase 3) | Calls: vibe-check MCP, business-analyst, AskUserQuestion Flow: requirements-phase → vibe-check → innovate-phase (success) OR requirements-phase (failure, max 2 loops)
Notes: Fast single MCP call. Validates coherence/clarity, not technical feasibility (architect's job). Escalate to user after 2 failed iterations.