spec-review

Name: spec-review
Availability: InStock
Author: basher83

Validate technical specifications through multi-round subagent reviews of control flow and cross-references.

Updated Feb 17, 2026

Search Tags:#design review #spec review #document validation #technical critique #implementability check #structured document analysis

Ready to run

npx skills add https://github.com/basher83/domain-chassis --skill spec-review-basher83

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses the challenge of ensuring technical specifications and design documents are sound, implementable, and free from critical errors before development begins.

Core Features & Use Cases

Structured Document Review: Provides a systematic, multi-round review process for technical documents.
Subagent Prompting: Leverages specialized subagent prompts to trace control flow, verify cross-references, and identify potential issues.
Use Case: A product manager provides a new feature specification. The spec-review skill is invoked to identify potential flaws in the logic, ensure all interfaces are correctly defined, and flag any ambiguities before the engineering team starts implementation.

Quick Start

Use the spec-review skill to critique the attached document 'api-design.md'.

Frequently Asked Questions about spec-review

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

FAQPage Schema

How do I validate technical specifications for correctness before implementation?▼

You can validate technical specifications for correctness by running a multi-round review process that analyzes control flow, state transitions, and cross-reference consistency to flag ambiguities and critical errors before development begins.

What is the best way to check if a design document is implementable?▼

Checking document implementability involves tracing control flow and verifying cross-references through detailed scenario simulation, ensuring all interfaces are correctly defined and logical flaws are identified for engineering teams.

How does structured document analysis find logical flaws in API designs?▼

Structured document analysis finds logical flaws by leveraging targeted subagent prompts to systematically trace control flow, verify cross-references, and output findings in a structured format, ensuring technical documents are sound.

Can I review state transitions and control flow in my feature specification?▼

Yes, you can review state transitions and control flow in a feature specification by applying a systematic review process that conducts detailed scenario simulations to identify potential issues and verify cross-reference consistency.

When do I need a multi-round spec review for my technical documents?▼

A multi-round spec review is needed when you must ensure technical specifications are sound and free from critical errors before development begins, verifying that all interfaces are correctly defined and implementable.

Does spec review require any specific dependencies or environment setup?▼

No, spec review does not require any specific dependencies or environment setup, allowing you to directly critique and validate structured technical documents without prerequisite components.