spec

Create a feature implementation spec for: $ARGUMENTS

Spec Numbering & Path

Every spec path starts with a zero-padded 3-digit prefix mirroring its roadmap phase number, so spec order matches roadmap order at a glance.

• Single spec: docs/specs/NNN_<slug>.md
• Sliced spec: docs/specs/NNN_<slug>/ containing README.md (index) and MMM_<slice>.md files. The directory-vs-file distinction is how sliced specs are identified — the NNN prefix stays on the directory, never moves to the children.
• Separator between prefix and slug is _; within the slug, words are joined by - (e.g., 003_atlassian-integration.md, never atlassian_integration.md and never without the prefix).

Picking NNN:

• If this spec implements a task in docs/roadmap/NNN_<phase>.md, use that same NNN. Check the roadmap file before picking.
• Multiple specs in one phase → disambiguate with letter suffixes NNN.A_<name>.md, NNN.B_<name>.md, in task order. A lone spec in a phase has no suffix.
• No roadmap yet → scan docs/specs/ and use max(existing) + 1. Don't renumber later when a roadmap is added.
• Never renumber an existing spec — commits, PRs, and issues reference specs by path.

Before writing any file, state the target path and confirm it satisfies the rules above.

Context Gathering

Read what already exists before interviewing:

1. Existing docs: docs/PRD.md or docs/prd/, docs/ARCHITECTURE.md, docs/TECHNICAL_DESIGN_DOCUMENT.md, docs/THREAT_MODEL.md, README.md, CLAUDE.md.
2. Roadmap and specs directory: list docs/roadmap/ and docs/specs/ to pick the correct NNN per the rules above.
3. Existing spec for this feature — if the user is revising, don't start from scratch.
4. Inherited project with no docs: read README.md, explore directory structure, read key entry points, check git log --oneline -20, read package.json / Cargo.toml / pyproject.toml / equivalent. Summarize what you learned to the user before the interview — "Here's what I understand about this project so far: ..."