quick-spec — Claude Code command: what it does, how to install
quick-spec reads your codebase, asks up to 10 questions and writes a focused spec file. Built for plain features and refactors where a full elicitation round is overkill.
no license ★ 1,357 updated 2026-03-01
.claude/commands/quick-spec.mdWhat quick-spec does
The command takes a feature description and an optional output path: /quick-spec <feature-description> [output-path.md]. It starts by reading the repository on its own, with Glob, Grep and Read — directory layout, naming habits, data models, how tests are written. The frontmatter pins opus as the model.
Then it drafts its own answers: where the code should go, what the schema change looks like, which endpoints to add, how failures get handled. You get up to 10 questions, reserved for decisions where a wrong guess would cost real rework. Each one arrives with a suggested answer and the code that backs it.
Output is a markdown spec: scope, requirements, technical approach, edge cases, and a list of assumptions you can correct. Default path is spec.md; a file already sitting there gets updated instead of replaced. The 10-question ceiling is the trade-off: a vague request will not fit, and the command will not fall back to full spec-elicitation on its own.
What it helps with
- turn a rough feature idea into a spec file before writing code
- reuse the project's own conventions instead of inventing new ones
- cut the interview down to the decisions that actually matter
- refresh an existing
spec.mdfor the next task - see which assumptions the command made, so you can correct them
Example prompts for the agent
- /quick-spec add CSV export for the reports page, write it to
docs/csv-export.md - /quick-spec move avatar uploads to S3
- /quick-spec refactor the billing module into a service, output
spec.md
How to install quick-spec
Manually: put the files in place
.claude/commands/quick-spec.mdCall it with /quick-spec. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/quick-spec.mdCall it with /prompts:quick-spec. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/quick-spec.prompt.mdManually: put the files in place
.gemini/commands/quick-spec.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about quick-spec
How do I install quick-spec in Claude Code?
Save the command file as .claude/commands/quick-spec.md in your project, then call it as /quick-spec.
What does quick-spec do?
It studies the codebase first, suggests an approach, asks up to 10 targeted questions and writes the resulting spec to a markdown file.
How is it different from spec-elicitation?
It makes assumptions and recommends instead of asking about every dimension, and caps the interview at 10 questions. For a vague or wide-open feature that is not enough.