review-spec

Review LP spec packages for vagueness, gaps, and edge-case risks.

Updated Apr 14, 2026

Search Tags:#planning #validation #multi-agent #contract #spec-review #lp-spec

Ready to run

npx skills add https://github.com/daudaudinang/vibecode --skill review-spec-daudaudinang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-spec
Source: https://github.com/daudaudinang/vibecode/tree/main/.agents/skills/review-spec
Command: npx skills add https://github.com/daudaudinang/vibecode --skill review-spec-daudaudinang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews one canonical LP spec package to identify vagueness, gaps, and edge-case risks before planning.

Core Features & Use Cases

Independent dual-mode review in standard mode with four independent personas (Senior PM, Senior UI/UX Designer, Senior Developer, System Architecture) for thorough evaluation.
Fast mode for delta-review using a single multi-persona pass to focus on changes, while preserving guardrails and publication of a contract.
Outputs include a detailed review report and a validation contract published to the designated pipeline path.

Quick Start

Invoke the worker with the PLAN_<NAME>/spec.md package to generate the 00-review-spec outputs.

Frequently Asked Questions about review-spec

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

FAQPage Schema

How do I review a spec package to identify gaps and edge-case risks before planning?▼

Standard mode uses four independent personas—Senior PM, Senior UI/UX Designer, Senior Developer, and System Architecture—for thorough spec evaluation. Fast mode uses a single multi-persona pass to focus on delta-review changes while preserving guardrails and publishing a contract.

What is multi-persona spec review and when do I need it for project validation?▼

Multi-persona spec review evaluates a specification package from independent professional perspectives to identify vagueness and edge-case risks. You need it before planning to ensure the spec is rigorous enough to pass gating validation.

How do I generate a validation contract status from a spec.md file?▼

You generate a validation contract by invoking the review process with your PLAN_<NAME>/spec.md package. It outputs a contract.json file containing a gating status of PASS, NEEDS_REVISION, or FAIL to the designated pipeline path.

Can I use a fast delta-review for spec changes instead of a full evaluation?▼

Yes, you can use fast mode for delta-review changes. It executes a single multi-persona pass focused on the updates while preserving evaluation guardrails and still publishing a validation contract to the pipeline.

What does the spec review output include for gating decisions?▼

The spec review output includes a detailed review report at 00-review-spec.output.md and a validation contract at 00-review-spec.output.contract.json, providing a PASS, NEEDS_REVISION, or FAIL status to accelerate gating.