agentmods.dev

spekka: Command for Claude Code

.claude/commands/spekka/create-spec.md

create-spec is a command for Claude Code from johnreitano/spekka. It costs 0 tokens per session (500 once invoked), scanned A, original, MIT.

A guided process for creating a complete specification, meaning a written description of a feature and its requirements.

In plain words
What is it for?
It initializes a dated specification folder, researches requirements, writes the specification, and reports when it is complete.
Why use it?
It gives a feature idea a structured path from initial setup through research and final writing.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

This is johnreitano/spekka's own configuration. It tells Claude Code how to work on spekka itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything spekka configures →

not rated 5repo 9mo ago A scan 0 tokens original MIT
View source ↗ johnreitano/spekka
Reuse

Borrowing it

Nothing to install: this file belongs to johnreitano/spekka. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/johnreitano/spekka/main/.claude/commands/spekka/create-spec.md
Clone the repo
git clone --depth 1 https://github.com/johnreitano/spekka

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for create-spec

README.md
[![agentmods](https://agentmods.dev/badge/commands/johnreitano/spekka/create-spec/github.svg)](https://agentmods.dev/commands/johnreitano/spekka/create-spec)
Your own site
<a href="https://agentmods.dev/commands/johnreitano/spekka/create-spec"><img src="https://agentmods.dev/badge/commands/johnreitano/spekka/create-spec/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for create-spec

Your own site · 80×15
<a href="https://agentmods.dev/commands/johnreitano/spekka/create-spec"><img src="https://agentmods.dev/badge/commands/johnreitano/spekka/create-spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 500 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00500
Opus 5.5 $0.00000 $0.00200
Sonnet 5.5 $0.00000 $0.00100
Haiku 4.5 $0.00000 $0.00050

Measured 2mo ago against content hash e8a025ab5f14, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-spec scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/spekka/create-spec.md · 66 lines

How it starts

The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Spec Creation Process

You are helping me create a complete specification for a new feature. This combines the spec shaping and spec writing processes into one seamless workflow.

This process will follow 4 main phases, each with their own workflow steps:

Process overview (details to follow)

PHASE 1. Initialize spec PHASE 2. Research requirements for this spec PHASE 3. Write the specification document PHASE 4. Inform the user that the spec is complete

Follow each of these phases and their individual workflows IN SEQUENCE:

Multi-Phase Process:

PHASE 1: Initialize Spec

Use the spec-initializer subagent to initialize a new spec.

IF the user has provided a description, provide that to the spec-initializer.

The spec-initializer will provide the path to the dated spec folder (YYYY-MM-DD-spec-name) they've created.

PHASE 2: Research Requirements

After spec-initializer completes, immediately use the spec-shaper subagent:

Provide the spec-shaper with:

  • The spec folder path from spec-initializer

The spec-shaper will give you several separate responses that you MUST show to the user. These include:

  1. Numbered clarifying questions along with a request for visual assets (show these to user, wait for user's response)
  2. Follow-up questions if needed (based on user's answers and provided visuals)

IMPORTANT:

  • Display these questions to the user and wait for their response
  • The spec-shaper may ask you to relay follow-up questions that you must present to user

PHASE 3: Write Specification Document

After requirements gathering is complete, use the spec-writer subagent to create the specification document:

Provide the spec-writer with:

  • The spec folder path from Phase 1
  • The requirements from planning/requirements.md
  • Any visual assets in planning/visuals/

The spec-writer will create spec.md inside the spec folder.

PHASE 4: Inform the User

After all steps complete, inform the user:

Spec creation is complete!

✅ Spec folder created: `[spec-path]`
✅ Requirements gathered
✅ Visual assets: [Found X files / No files provided]
✅ Spec document created: `[spec-path]/spec.md`

NEXT STEP 👉 Run `/spekka:create-tasks` to generate your tasks list for this spec.

Read the full file on GitHub · 66 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 66 lines · 0 tokens per session scan A e8a025ab5f14

Subscribe to this mod's changes

create-spec is a command published in the GitHub repository johnreitano/spekka (5 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 500 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Planning
Related

create-spec compared with commands from other repositories

create-spec next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
create-specjohnreitano/spekkaCommand59mo agoMITA0Claude Code
checklistgithub/spec-kitCommand148kyesterdayMITA13Claude Code
clarifygithub/spec-kitCommand148kyesterdayMITA27Claude Code
specifygithub/spec-kitCommand148kyesterdayMITA13Claude Code
analyzegithub/spec-kitCommand148kyesterdayMITA26Claude Code
convergegithub/spec-kitCommand148kyesterdayMITA35Claude Code
implementgithub/spec-kitCommand148kyesterdayMITA14Claude Code