Individual skill

spec

Turn a vague feature or product idea into an agreed, persisted specification through relentless structured questioning. Never assumes — every gap, ambiguity, or "probably" becomes a question to the developer, and the spec cannot be approved while open questions remain. Produces docs/specs/<NNN>-<slug>.md with acceptance criteria that /plan, /scaffold, and /tdd consume. Use when: "spec", "write a spec", "spec this out", "requirements", "PRD", "acceptance criteria", "define the feature", "user stories", "what should we build", or before planning any feature too big to describe in one sentence.

skills/spec/SKILL.md

Read pinned source

Source commit 23300897f4d1a276bc475e373ecfe886e43dd7c5

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: No
Observed behavior: Instructions only
Last checked: Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 807
Repository last updated: Nov 4, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

engineering Derived category
testing Derived category
docs Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 8,040 bytes

Read excerpt


# /spec — Relentless Specification Workflow

## What

Converts an idea into a written, versioned specification that both the developer
and Claude explicitly agree on — before any planning or code. The contract:

- **Never assume.** Every gap in the idea becomes a question. If Claude catches
  itself thinking "probably", "presumably", or "the usual way" — that thought is
  a question to ask, not a decision to make.
- **Relentless, but structured.** Questions come in focused rounds (3–5 at a
  time) across nine dimensions — not one overwhelming dump, and not a single
  polite round that stops early.
- **Agreement is explicit.** Specs have a status lifecycle: Draft → In Review →