review-spec

Review software development phase specifications for conflicts and gaps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill addresses the critical need for high-quality, consistent, and implementable specifications by automating the review process, catching errors early, and ensuring alignment across different project phases.

Core Features & Use Cases

  • Automated Spec Review: Spawns dedicated agents to review individual phase specifications for quality, consistency, and implementability.
  • Cross-Phase Validation: Performs checks for shared file conflicts, dependency violations, duplicate tasks, and verification measure achievability across all phases.
  • Actionable Feedback: Consolidates findings into a clear report, prioritizing blocking issues and providing concrete suggestions for improvement.
  • Use Case: Before starting development on a new feature, use this Skill to automatically review all phase specifications, ensuring that no two phases attempt to modify the same file in conflicting ways and that all planned verification steps are covered by the implementation tasks.

Quick Start

Use the review-spec skill to review all phase specifications for the current project.

Frequently Asked Questions about review-spec

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

FAQPage Schema
How do I automate code review for phase specifications to ensure consistency?

Automated spec review validates software development phase specifications for quality, consistency, and implementability by analyzing spec files against project plans and cross-phase dependencies to identify conflicts and gaps.

How do I check for shared file conflicts across multiple project phases?

Cross-phase validation checks for shared file conflicts by verifying that no two phases attempt to modify the same file in conflicting ways, alongside detecting dependency violations and duplicate tasks.

What is the best way to validate that verification measures are addressed in development plans?

Spec validation ensures plan verification measures are addressed by checking that all planned verification steps are covered by the implementation tasks across all project phases.

Does automated spec review work without external dependencies?

Yes, automated spec review operates without external dependencies, spawning dedicated agents to analyze spec files and consolidate findings into a prioritized report of blocking issues.

When do I need to review software development phase specifications for quality?

You need spec review before starting development on a new feature to catch errors early, ensuring alignment across different project phases and confirming implementability of the planned tasks.

What limitations exist when reviewing cross-phase dependencies in project plans?

The review process requires existing spec files to analyze; it validates dependencies and shared resources but cannot generate missing specifications, only identifying gaps and providing improvement suggestions.