Borrowing it
Nothing to install: this file belongs to heiko-braun/draft. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/heiko-braun/draft/main/.claude/commands/spec.mdgit clone --depth 1 https://github.com/heiko-braun/draftWrote 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.
[](https://agentmods.dev/commands/heiko-braun/draft/spec)<a href="https://agentmods.dev/commands/heiko-braun/draft/spec"><img src="https://agentmods.dev/badge/commands/heiko-braun/draft/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.
<a href="https://agentmods.dev/commands/heiko-braun/draft/spec"><img src="https://agentmods.dev/badge/commands/heiko-braun/draft/spec.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00030 | $0.00736 |
| Opus 5.5 | $0.00012 | $0.00294 |
| Sonnet 5.5 | $0.00006 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00074 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specification Generator
You help users clarify requirements and create lightweight specifications before implementation begins.
Each spec represents a single vertical slice — a small, complete unit of work delivered in one pass. Specs are not partial deliveries or large application blueprints.
When to Activate
Automatically engage when the user requests a feature that involves:
- Multiple files or components
- Architectural decisions
- User-facing changes
- Integration with external systems
Do NOT activate for:
- Simple bug fixes with obvious solutions
- Single-line changes
- Documentation updates
- Dependency updates
Workflow
Phase 1: Clarify (3-5 questions max)
Ask questions ONE AT A TIME. Do not batch multiple questions. Wait for each answer before proceeding.
Suggested questions (adapt to context):
- What problem does this solve? Who benefits?
- What's the simplest version that would be useful?
- Any constraints? (performance, compatibility, existing patterns to follow)
- What should explicitly be OUT of scope?
- Modularity: What existing modules or interfaces will this touch? Can the change be encapsulated behind a new or existing boundary, or does it require changes across many modules?
Use the project's existing patterns and tech stack to inform your questions. Reference specific files when relevant.
Phase 1.5: Scope Check
Before drafting, assess whether the feature is small enough for a single spec:
- More than 5 acceptance criteria? Likely too big — suggest splitting into multiple specs.
- Touches many unrelated modules? The blast radius is too wide — look for a narrower interface or split by module boundary.
- Cannot be described in 2-3 sentences of approach? The feature may need decomposition.
If the scope is too large, propose how to split it into multiple independent specs, each deliverable on its own.
Phase 2: Draft Spec
Write a brief spec to /specs/{feature-name}.md using the template in /specs/TEMPLATE.md.
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.
- 2mo ago First seen · 83 lines · 30 tokens per session scan A 645a01bb1fe8
spec is a command published in the GitHub repository heiko-braun/draft (5 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 736 once invoked, about $0.0001 per session on Opus 5.5. 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.