1. Habit
  2. Skills
  3. Spec skill
klerith · 4K installs

Spec skill
Runs by itself, when you start a big feature.

Every big feature starts with a clear plan.

Install the Spec skill and make it a habit: follow https://gethabit.dev/skills/klerith/spec.md

  1. 1Copy
  2. 2Paste into Claude Code, Codex or Cursor
  3. 3It runs by itself

4K installs327 starsMIT licenceSource on GitHub ↗

Spec

by klerith · 4K installs

The skill

Asks you questions, then writes a plan for a big feature.

Only when you ask.

Less rework

Every big feature starts with a clear plan. Less guessing and less rework.

↻ Runs by itselfwhen you start a big feature

How the habit works.
You don't have to.

Three questionsWhen does it start? How does it check its work? What does it remember?

01

It starts by itself

you start a feature. Runs in Claude Code slash command.

  • ↻ you start a feature
  • run /spec with a description

02

It checks its work

spec saved as draft. If a check fails, it tries again.

  • ✓the three closing questions are answerable without assuming: which files change, first and last step, how to verify
  • ✓the spec file exists at specs/NN-slug.md
  • ✓the state is Draft, not Approved
  • ✓listed dependencies exist in specs/

03

It remembers

specs folder. The next run reads it first: the two most recent specs for numbering, language and conventions.

specs/

One run, step by step.
Then it stops.

Stop ruleStops after one spec is written and saved per run.

  1. 01

    Understand the context

    Read the project-memory file and the two most recent specs for conventions and numbering.

  2. 02

    Clarify by questions

    Ask 3 to 5 concrete questions per block on scope, data, integration, persistence, states and risks until nothing is assumed.

  3. 03

    Write the spec

    Follow template.md: header, scope, data model, implementation plan, acceptance criteria, decisions and risks.

  4. 04

    Save as draft

    Write specs/NN-slug.md with the next number and the session date, state Draft, and seed .spec-config.yml if missing.

  5. 05

    Confirm and stop

    Report the path and that /spec-impl runs once the user approves; propose no further action.

What it may do.
Nothing more.

Safe by defaultIt writes only in its own folder and asks you before anything goes out.

Is it for you?
Use it when it fits.

Quick checkRead both lists. If the left one sounds like you, the Spec skill helps.

Use it when

  • ✓ You start a large feature
  • ✓ You want a spec before code
  • ✓ You need clarifying questions drawn out

Skip it when

  • – You want code written now
  • – The change is a small tweak

Questions

Spec skill, answered.

Does it write code?

No. This loop produces only the spec file; /spec-impl implements it once you approve.

Why so many questions first?

A vague spec makes the code improvise, so the definition phase is deliberately slow.

How do I install the Spec skill?

Copy the prompt at the top into your agent. It installs the skill from klerith/fernando-skills and sets up the habit. Or run npx skills add klerith/fernando-skills --skill spec.

Is the Spec skill free?

Yes. It is published under MIT. Habit is free too.

Spec. Now as a habit.

Install the Spec skill and make it a habit: follow https://gethabit.dev/skills/klerith/spec.md

  • Free
  • No account
  • Undo in one line

All klerith skills →More planning skills →

Works in

  • Claude Code
  • Codex
  • Cursor
  • ChatGPT
  • Claude app

Made by klerith, published under MIT. Habit links to the original and never changes it. Is this your skill?

Copying didn't work here. Select the line and copy it by hand.