Agent skill · product strategy · klerith
spec
Designs and develops specs following the spec-driven method. Asks clarifying questions before proposing structure, and builds the spec section by section. Use it when starting a large feature, before writing code.
Why this skill is useful
Adds a structured approach to spec development with specific questioning techniques that the AI wouldn't reliably generate on its own.
What it needs
About 8k tokens when loaded. Last updated 2026-08-02. 151 stars on the source repository.
What this skill does
/spec — Guided spec designer Session context Today's date (use this for the spec header, never guess it): !date +%F Specs that already exist: !ls specs/ 2>/dev/null echo "The specs/ folder does not exist yet" --- This skill helps you produce a useful spec following the spec-driven method. You don't write code here. Your job is to help the user clarify what they want to build, ask questions when something is not well-defined enough, and develop the spec section by section until it is ready to be saved into specs/. Philosophy A spec is not decorative documentation. It is the contract that drives later execution. If the spec is vague, the code will improvise. That is why this flow is deliberately slow during the definition phase and fast during the writing phase. Read template.md (in the same directory as this skill) to see the full structure the spec will follow. Lean on it at every step. Command flow Follow the four phases in order. Never skip Phase 2 — the questions are the whole point. If the user wants to go faster, remind them that the cost of a bad spec gets paid later in code. (Phase 3 does have a fast path once Phase 2 is genuinely complete; see below.) Your replies must be in the same language as the initial prompt. E.g.: if the initial prompt is in Spanish, your replies must be in Spanish; if it is in English, your replies must be in English. Phase 1 — Understand the context Before asking questions about the feature, make sure you have project context: 1. Read the project-memory file, if one exists. Try in order and stop at the first hit: CLAUDE.md, AGENTS.md, GEMINI.md, README.md. This adapts the skill to whichever agent is running it (Claude Code, Codex, Gemini CLI, etc.). 2. Look at the specs/ listing in the session context above to see which specs already exist and how they are numbered. 3. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills klerith/spec