feature-spec-critic

Evaluate engineering specs against a startup rubric for over-engineering and simplicity.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/pcortes/swarm-attack --skill feature-spec-critic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feature-spec-critic
Source: https://github.com/pcortes/swarm-attack/tree/main/default-skills/feature-spec-critic
Command: npx skills add https://github.com/pcortes/swarm-attack --skill feature-spec-critic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tedious and time-consuming manual process of reviewing engineering specifications by automatically evaluating them against a detailed quality rubric. It ensures high-quality, implementable specs, significantly reducing rework, preventing costly errors, and improving overall development efficiency.

Core Features & Use Cases

  • Automated Spec Evaluation: Scores engineering specifications on critical dimensions like clarity, coverage, architecture, and risk.
  • Detailed Issue Identification: Pinpoints critical, moderate, and minor issues within the spec, providing actionable descriptions and suggestions for improvement.
  • Quality Gate: Acts as a crucial quality gate before development begins, ensuring all requirements are met and potential problems are identified early.
  • Use Case: A new feature specification is drafted. This Skill reviews it, identifies a critical security vulnerability (e.g., missing rate limiting for an API endpoint), and suggests a specific fix, preventing a major issue from reaching production.

Quick Start

Review the engineering specification located at 'specs/new-feature/spec-draft.md' against the quality rubric and provide a detailed critique in JSON format.

Frequently Asked Questions about feature-spec-critic

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

FAQPage Schema
How do I review engineering specifications to catch quality issues before development?

Spec review identifies critical gaps, architectural risks, and clarity problems early. This Skill evaluates drafts against a startup-focused rubric, scoring clarity, coverage, architecture, and risk to surface issues like missing rate limiting or incomplete requirements before implementation starts.

What makes a specification ready for development?

A ship-ready spec must be clear, complete, architecturally sound, and free of critical risks. This Skill grades specs on these dimensions, pinpointing which areas need refinement so teams move forward with confidence and minimal rework.

Can I automate spec quality checks into my development workflow?

Yes. This Skill delivers deterministic JSON outputs and machine-readable metadata that integrate into RAG indexing, decision automation, and downstream review workflows, acting as a quality gate before code begins.

How do I identify architectural over-engineering in early-stage specs?

Over-engineering wastes time in startups. This Skill prioritizes simplicity and evaluates architecture against startup constraints, flagging unnecessary complexity so teams ship faster with implementable, focused designs.

What specific issues does a spec critique surface?

Spec review categorizes issues by severity—critical (blocking risks like security gaps), moderate (incomplete coverage), and minor (clarity improvements)—with actionable descriptions and targeted suggestions for each.