specification

Generates fixed-structure technical specifications with measurable acceptance criteria from gathered inputs.

4|2|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/Arete-Consortium/ai-skills --skill specification-arete-consortium
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: specification
Source: https://github.com/Arete-Consortium/ai-skills/tree/main/workflows/specification
Command: npx skills add https://github.com/Arete-Consortium/ai-skills --skill specification-arete-consortium

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a decision is made, teams often produce vague specs with untestable requirements like "should be fast," leading to misaligned implementations and endless re-litigation of the premise. This Skill enforces a fixed-structure specification with measurable constraints and falsifiable acceptance criteria. ## Core Features & Use Cases - Structured Input Gathering: Collects required slots (artifact, objective, constraints, interfaces, acceptance, evidence base, exclusions) and asks before filling gaps with assumptions. - Fixed Output Format: Produces specs in a defined order — summary, MUST/MAY/MUST NOT requirements, measurable constraints, typed interfaces, falsifiable acceptance criteria, explicit out-of-scope items, and labeled open questions. - Failure-Condition Self-Check: Rewrites untestable requirements, adds missing error-case behavior, and removes exploratory language before emitting the spec. - Use Case: After deciding to build a new API endpoint, invoke the skill to produce a buildable spec with p95 latency thresholds, typed request/response schemas, and testable acceptance criteria an engineer can implement directly. ## Quick Start Ask the AI to run /specification and provide the artifact, objective, constraints, interfaces, and acceptance criteria for the thing you want specified.

Frequently Asked Questions about specification

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

FAQPage Schema
How do I write a technical specification with measurable acceptance criteria?▼

Invoke the specification skill and provide the artifact, objective, constraints, interfaces, and acceptance criteria. It produces a fixed-structure spec where every constraint includes a measurement method and every acceptance criterion is falsifiable.

What inputs does the specification skill require?▼

It requires seven slots: artifact, objective, constraints, interfaces, acceptance, evidence base, and exclusions. If any are missing, it asks before producing the spec rather than filling gaps with assumptions.

Can the specification skill handle non-code deliverables?▼

Yes, it supports non-code artifacts such as workflows and deliverables. The goal-loop sentinel is only armed for code or build artifacts; non-code specs use a custom evaluation rubric instead.

When should I not use specification mode?▼

Do not use it while the underlying decision is still open. The skill never re-argues the premise; if you want to reconsider alternatives, run the evaluation mode first and only specify after the decision is final.

Why does the spec reject requirements like "should be fast"?▼

Untestable requirements are a defined failure condition. The self-check rewrites them with explicit thresholds, such as "p95 latency under 200ms," so engineers can verify compliance objectively.