spec-review

Analyze tech specs to surface gaps and produce implementable updates.

11|Updated Sep 5, 2025
One-click install
npx skills add https://github.com/thrawn01/claude-dotfiles --skill spec-review-thrawn01
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spec-review
Source: https://github.com/thrawn01/claude-dotfiles/tree/main/skills/spec-review
Command: npx skills add https://github.com/thrawn01/claude-dotfiles --skill spec-review-thrawn01

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill analyzes an existing tech spec to identify gaps, inconsistencies, unresolved soft flags, and ambiguities that would force implementation decisions during build, then guides the user to produce an updated, implementable spec.

Core Features & Use Cases

  • Review and validate tech specs against PRD, ADRs, and domain glossary to surface blockers and decisions.
  • Orchestrate iterative review cycles, including pre-seeded drift findings, soft-flag triage, and goal-validation gating.
  • Produce a concrete, updated spec with recommended edits and a plan for follow-up decisions.

Quick Start

Provide a tech spec path to begin review and request an update to an implementable spec.

Frequently Asked Questions about spec-review

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

FAQPage Schema
How do I find ambiguities and gaps in a tech spec before implementation?

Review your tech spec against the PRD, ADRs, and domain glossary to surface inconsistencies, unresolved soft flags, and ambiguities. This process identifies blockers that would force decisions during build, allowing you to update the spec into an implementable plan.

What is a soft flag in tech spec review?

A soft flag is an unresolved issue or ambiguity in a tech spec that requires a decision before implementation. During spec review, soft flags are triaged to determine if they represent blockers or can be resolved through ADR handoffs and iterative validation.

How do I turn a vague tech spec into an implementable plan?

Transform a vague tech spec by orchestrating an iterative review cycle that validates goals against the PRD and coverage maps. This produces an updated spec with recommended edits, clear blockers, and decisions for engineers to proceed.

Can I validate a tech spec against a PRD and ADRs?

Yes, validating a tech spec against the PRD and ADRs is essential to surface gaps and inconsistencies. This review process checks for unresolved soft flags and ensures the spec aligns with domain context before implementation begins.

What is the best way to handle unresolved decisions in a tech spec?

Handle unresolved decisions by creating ADR handoffs that document the required choices. The spec review process triages these soft flags, gates goal validation, and outputs a concrete plan with recommended edits for engineers.

When do I need an iterative review cycle for tech specs?

You need an iterative review cycle when a tech spec contains ambiguities and gaps that block implementation. This cycle references the PRD, ADRs, and coverage maps to guide validation, triage soft flags, and hand off decisions.