# quick-spec

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.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 1357 repo stars
- Author: qdhenry
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/spec-workflow/quick-spec.md
- Updated: 2026-03-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/quick-spec

## What it 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.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/quick-spec.md` — Call it with /quick-spec. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/quick-spec.md` — Call it with /prompts:quick-spec. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/quick-spec.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/quick-spec.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/spec-workflow/quick-spec.md

## When to use it
- 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.md` for the next task
- see which assumptions the command made, so you can correct them

## Example prompts
- /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`

## Similar
- [spec](https://affpapa.org/en/nevibecode/skills/spec.md) — skill · 5000 installs
- [bmad-tech-spec](https://affpapa.org/en/nevibecode/skills/bmad-tech-spec.md) — skill · 114 installs
- [bmad-spec](https://affpapa.org/en/nevibecode/skills/bmad-spec.md) — skill · 108 installs
- [interview](https://affpapa.org/en/nevibecode/commands/jarrodwatts-interview.md) — command · ★ 1064 repo stars
- [spec-writer](https://affpapa.org/en/nevibecode/skills/spec-writer.md) — skill · ★ 29 repo stars
- [absolute-spec](https://affpapa.org/en/nevibecode/skills/absolute-spec.md) — skill · 176 installs

From the same set: [qdhenry/claude-command-suite](https://affpapa.org/en/nevibecode/by/qdhenry/claude-command-suite.md) — 112 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
