Claude Code spec for requirements and failure cases

Clarify actors, triggers, normal flow, and failure cases, then review existing project patterns before producing a feature spec.

中文

Install in Claude Code

Open Claude Code with the feature request, repository conventions, and a writable specification location.

Review `.claude/skills/spec/SKILL.md` and its requirements at the pinned GitHub commit.
Create `.claude/skills/spec/` in your project and save the reviewed file as `.claude/skills/spec/SKILL.md`.
Start Claude Code from that project's root, then select `/spec` in the slash menu.

Example task

The request defines {action: 'Rename collection', nameLengthLimit: 40, blankNameAllowed: false}. Concurrent renaming behavior is still open.

What to check

Draft success and blank-name error cases with {nameLengthLimit: 40, concurrency: 'open'}. Keep the concurrency decision open and identify later tests.

Original SKILL.md on GitHub · Updated 2026-11-14

Frequently asked question

Should unresolved behavior appear in the document?

Mark unresolved rules as open and identify who should decide. Turn confirmed boundaries into verifiable cases.