← ClaudeAtlas

spec-specifylisted

Use when someone describes a feature, a behaviour, or something the product should do - "we need refunds", "users should be able to reset their password", "add a way to export bookings". Turns it into that capability's living spec and goes straight into the clarify questions. Reach for this before writing the code, not after it.
repository-standards/core · ★ 3 · Testing & QA · score 76
Install: claude install-skill repository-standards/core
<!-- Vendored from github/spec-kit v0.13.2 (MIT - scripts/spec/LICENSE). PATCHED(repository-standards) hunks are marked inline. --> <!-- PATCHED(repository-standards): em and en dashes normalised to ASCII hyphens throughout. standard/docs/conventions.md forbids them, and this file ships into every adopting repo, so the vendored punctuation would have carried a rule break into each one. Prose only - no instruction, path or example changed. Enforced by tools/prose-check.mjs. --> <!-- PATCHED(repository-standards): ADR-010 - clarify chains automatically after specify --> **Clarify chains automatically after specify.** When this command completes, immediately continue into the clarify loop (`/spec-clarify`) in the same session - do not stop and wait to be asked. The loop is AI-led: propose answers, ask the user only what genuinely needs their call, and record every deferral ("leaving this to the technical side") in the spec's `## Clarifications` section instead of dropping it. Plan and tasks are gated: they refuse a spec that has no `## Clarifications` section or still contains open markers of the `[NEEDS ...` family (that gate is what earns `Status: ready-to-develop`). <!-- PATCHED(repository-standards): ADR-033 - a record that already governs the request is read before the request is drafted, not discovered afterwards --> **Decision intake (before drafting, and before the dossier).** Read `docs/decision-records/`'s index - the README table, not every record