review-spec

Review multi-file technical specifications for inconsistencies, gaps, and over-engineering.

Updated Nov 9, 2025
One-click install
npx skills add https://github.com/msalganik/torchtune_config_writer --skill review-spec
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-spec
Source: https://github.com/msalganik/torchtune_config_writer/tree/main/.claude/skills/review-spec
Command: npx skills add https://github.com/msalganik/torchtune_config_writer --skill review-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solves? This Skill automates the rigorous review of technical specifications, identifying over-engineering, inconsistencies, and incompleteness. It helps teams simplify designs, reduce scope, and focus on delivering core value, preventing costly delays and rework, ultimately helping you ship products faster.

Core Features & Use Cases

  • Scope & Complexity Assessment: Pinpoints over-scoped features and suggests MVP reductions, ensuring your project stays on track.
  • Consistency & Completeness Checks: Verifies terminology, design decisions, cross-references, and missing sections across multi-file specifications.
  • Simplification & Removal Opportunities: Actively identifies "gold plating," premature optimization, and features to defer or eliminate, saving development resources.
  • Use Case: A product manager has a detailed technical specification for a new feature with several appendices. They use this skill to get an objective review, ensuring the spec is lean, clear, and focused on the most critical functionality for a timely launch.

Quick Start

Review the attached technical specification document 'new_feature_spec.md' and its appendices 'appendix_a.md' and 'appendix_b.md'. Focus on identifying opportunities for simplification and scope reduction for an MVP.

Frequently Asked Questions about review-spec

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

FAQPage Schema
How do I review a technical specification for scope and complexity issues?

Technical specification review identifies over-engineered features, inconsistencies, and gaps across multi-file docs. Analyze terminology consistency, cross-document references, and dependencies to pinpoint opportunities for simplification, MVP reduction, and scope clarification before development begins.

What should I check in a spec to ensure it's ready for MVP planning?

Verify functional requirements are complete, terminology is consistent across all files and appendices, design decisions are justified, and cross-references are accurate. Assess which features are essential for MVP launch versus candidates for deferral or removal to reduce complexity.

How do I identify over-engineered features and gold plating in technical specifications?

Specification review pinpoints premature optimization, unnecessary complexity, and features beyond core functionality. Compare stated requirements against proposed solutions to surface deferrable work, enabling teams to focus development resources on critical value delivery.

Can I use spec review to reduce project delays and rework?

Yes. Early specification review catches inconsistencies, missing sections, and scope creep before implementation, preventing costly design conflicts and development rework. Simplified, validated specs accelerate handoff to engineering teams and reduce time-to-ship.

What file formats and appendices does specification review support?

Specification review handles multi-file technical documentation with appendices, assessing organization, dependencies, and completeness across the full specification package. It works with markdown and similar structured formats to ensure all sections align and support actionable refinement.

Why should product managers review specifications for completeness before handoff?

Specification review ensures all functional requirements are documented, design decisions are justified, and terminology is consistent before engineering begins. Complete, validated specs reduce ambiguity, accelerate development, and prevent scope disputes that delay shipping.