review-spec

Verify feature specs against relevance, edge cases, and established patterns.

25|4|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/CaptainCrouton89/crouton-kit --skill review-spec-captaincrouton89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-spec
Source: https://github.com/CaptainCrouton89/crouton-kit/tree/main/plugins/rpi/skills/review-spec
Command: npx skills add https://github.com/CaptainCrouton89/crouton-kit --skill review-spec-captaincrouton89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams verify feature specs against relevance, edge cases, and consistency with established patterns, preventing scope creep and misinterpretation.

Core Features & Use Cases

  • Spec validation: Checks relevance, edge cases, and architectural consistency against established guidelines.
  • Pattern compatibility: Cross-references with CLAUDE.md and referenced rules to ensure alignment.
  • Quality gate for specs: Used after creating a spec to surface gaps before implementation.

Quick Start

review-spec path/to/your/spec.md

Frequently Asked Questions about review-spec

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

FAQPage Schema
How do I validate a feature spec for edge cases before implementation?

To validate a feature spec for edge cases, teams use this skill to check relevance, architectural consistency, and pattern compatibility during the spec-review phase. It cross-references established guidelines to surface gaps and prevent scope creep before implementation begins.

What is the best way to check architecture patterns against established project guidelines?

Checking architecture patterns against established guidelines involves cross-referencing the spec with project rules like CLAUDE.md. This skill enforces criteria for pattern compatibility and abstraction level, ensuring new features align with existing architectural constraints.

How do I review a spec file for scope creep and misinterpretation risks?

Reviewing a spec file for scope creep involves validating relevance and edge-case coverage against established patterns. By running review-spec on the spec file, teams can surface gaps in the spec-review phase, preventing misinterpretation before implementation starts.

Can I use spec validation for projects of varying size and complexity?

Spec validation applies across projects of varying size and complexity. It operates during the spec-review phase to verify feature specs against relevance, edge cases, and consistency with established patterns, regardless of project scale.

What limitations exist when enforcing abstraction level and pattern compatibility in specs?

Limitations when enforcing abstraction level and pattern compatibility depend on the referenced rules available. This skill cross-references with CLAUDE.md and established guidelines to enforce criteria, but requires these referenced rules to exist for proper validation.