spec-review

Reviews an existing specification through three isolated parallel legs and rewrites it in place.

Updated Aug 31, 2026
One-click install
npx skills add https://github.com/keefhub/travel-expense --skill spec-review-keefhub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/keefhub/travel-expense/tree/main/.claude/skills/spec-review
Command: npx skills add https://github.com/keefhub/travel-expense --skill spec-review-keefhub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Existing specifications often contain ambiguities, stale claims about the codebase, and hidden failure modes that only surface during implementation. This Skill hardens an already-written spec by subjecting it to three independent reviews and reconciling the findings into a single improved document. ## Core Features & Use Cases - Diamond fan-out review: Freezes the spec into a hashed packet, then runs three isolated legs — requirements analysis, verification against the real codebase, and adversarial stress-testing — so their conclusions stay comparable and independent. - Ground-truth verification: The verification leg opens actual repository files and checks every claim the spec makes about existing code, APIs, and conventions with file:line citations. - Reconciliation and gated rewrite: Merges duplicate findings, dispositions every Critical and Major issue, then rewrites the spec in place with a version bump, Review Findings table, and Open Questions table. - Use Case: After generating a feature spec with /feature-spec, run /spec-review on doc/features/005-record-expense/spec.md to catch contradictions, missing failure modes, and wrong assumptions about the codebase before implementation begins. ## Quick Start Ask the AI to run /spec-review on the path to your existing spec file, for example /spec-review doc/features/005-record-expense/spec.md.

Frequently Asked Questions about spec-review

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

FAQPage Schema
How do I review a feature specification before implementation?

Run /spec-review with the path to your spec file, such as /spec-review doc/features/005-record-expense/spec.md. It freezes the spec, runs three independent review legs, reconciles findings, and rewrites the spec in place with dispositions for every issue.

What is the difference between spec-review and feature-spec?

feature-spec creates a new specification from scratch, while spec-review only reviews and hardens a spec that already exists. If the target spec does not exist, spec-review stops and suggests using feature-spec instead.

Does spec-review modify code or only the specification?

spec-review is read-only outside the spec file itself. It never edits code, makes commits, or modifies other files; the only exception is its scratch directory used for the frozen packet and leg artifacts.

What happens if parallel subagents are not available?

The three review legs run sequentially instead, each still receiving only the untouched frozen packet with no output from earlier legs. The degradation to sequential execution is disclosed in the final report.

Why does spec-review hash the spec packet with SHA-256?

The hash proves all three legs reviewed the identical frozen document, making their findings comparable. Each leg recomputes the hash before starting and aborts on mismatch, so divergence is detected rather than assumed away.