analyze-spec

Identify quality issues in specs and generate structured improvement plans.

42|8|Updated Jan 25, 2026

Search Tags:#documentation #consistency #quality #review #spec #analyze #depth-aware

Ready to run

npx skills add https://github.com/sequenzia/claude-alchemy --skill analyze-spec

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: analyze-spec
Source: https://github.com/sequenzia/claude-alchemy/tree/main/plugins/sdd/skills/analyze-spec
Command: npx skills add https://github.com/sequenzia/claude-alchemy --skill analyze-spec

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyzing specs to identify inconsistencies, missing information, ambiguities, and structural gaps enables teams to produce higher-quality documents and reduce rework.

Core Features & Use Cases

Detects conflicting requirements and cross-section mismatches to surface inconsistencies.
Flags missing attributes such as acceptance criteria, dependencies, personas, and edge cases.
Highlights ambiguous language and structural issues to improve readability and maintainability.
Use cases include validating user stories, architecture notes, and API sections, then generating actionable improvement plans.

Quick Start

Provide the spec path to begin analysis and generate a structured improvement report.

Frequently Asked Questions about analyze-spec

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

FAQPage Schema

How do I check a software spec for missing acceptance criteria and ambiguities?▼

To check a software spec for missing acceptance criteria and ambiguities, provide the spec path to apply depth-aware analysis that surfaces inconsistencies, missing attributes, and structural gaps, then outputs a structured findings list and improvement plan.

What is depth-aware spec analysis and how does it detect inconsistencies?▼

Depth-aware spec analysis is an auditing process that applies layered criteria to identify conflicting requirements, cross-section mismatches, and ambiguous language across user stories, acceptance criteria, dependencies, and architecture notes to produce actionable remediation plans.

How do I validate user stories and architecture notes for completeness?▼

Validate user stories and architecture notes for completeness by running a spec audit that flags missing personas, edge cases, and dependencies, generating a structured improvement report suitable for immediate remediation.

What is the best way to generate an improvement plan for a requirements document?▼

The best way to generate an improvement plan for a requirements document is to analyze the spec for quality issues like ambiguities and structural gaps, which automatically produces an actionable remediation plan targeting the identified deficiencies.

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

No, this spec review tool requires no specific dependencies or environment setup, allowing you to directly provide a spec path and immediately generate a structured findings list without additional configuration.

What types of issues can a spec audit identify in API documentation?▼

A spec audit can identify issues in API documentation such as missing attributes, conflicting requirements, ambiguous language, and structural gaps, surfacing them in a structured findings list for targeted improvement.