spec-critique

Validates specification documents against requirements and produces a scored verdict with issues.

3|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/gabrielnsmnto/kord-aios --skill spec-critique-gabrielnsmnto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-critique
Source: https://github.com/gabrielnsmnto/kord-aios/tree/main/src/features/builtin-skills/kord-aios/analysis/spec-critique
Command: npx skills add https://github.com/gabrielnsmnto/kord-aios --skill spec-critique-gabrielnsmnto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Before implementation begins, specifications often contain gaps, contradictions, or infeasible approaches that cause rework later. This Skill systematically critiques a story's spec.md against its requirements.json, scoring five quality dimensions and producing a blocking gate verdict (APPROVED, NEEDS_REVISION, or BLOCKED) so weak specs are caught early. ## Core Features & Use Cases - Five-Dimension Scoring: Evaluates accuracy, completeness, consistency, feasibility, and alignment with weighted checks and 1-5 scores per dimension. - Structured Issue Reports: Generates critique.json with severity-tagged issues (HIGH/MEDIUM/LOW), locations, fix suggestions, and auto-fixable flags. - Pipeline Gate Integration: Acts as a blocking verification gate between the spec and plan phases, routing NEEDS_REVISION specs back to spec-write and escalating BLOCKED specs to the architect. - Use Case: After drafting a specification for STORY-42, run the critique to discover that two functional requirements lack test scenarios, receive an auto-fixable suggestion, and return the spec for revision before planning. ## Quick Start Ask the agent to critique the specification for story STORY-42 and report the verdict with any issues found.

Frequently Asked Questions about spec-critique

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

FAQPage Schema
How do I validate a specification document before implementation?▼

Run the critique phase on the story's spec.md together with its requirements.json. The process checks every functional and non-functional requirement for coverage, scores five quality dimensions, and outputs a critique.json with a verdict and issue list.

What quality dimensions should a software specification be checked against?▼

This workflow checks accuracy, completeness, consistency, feasibility, and alignment, weighted at 25, 25, 20, 15, and 15 percent respectively. Each dimension has specific checks such as requirement coverage, test coverage, ID reference validity, and architecture fit.

How is the spec approval verdict determined?▼

APPROVED requires no HIGH severity issues, an average score of at least 4.0, and all dimensions at 3 or above. NEEDS_REVISION applies to medium issues or averages between 3.0 and 3.9, while HIGH severity issues or averages below 3.0 produce BLOCKED.

What happens when a specification fails the critique gate?▼

A NEEDS_REVISION verdict returns the spec to the spec-write phase along with critique.json and auto-fix suggestions. A BLOCKED verdict halts the pipeline and escalates to the architect agent for resolution.

Can spec critique run without a requirements.json file?▼

No. Both spec.md and requirements.json are required inputs; missing either one halts the critique because accuracy cannot be validated. complexity.json and research.json are optional inputs that enrich the evaluation.