← ClaudeAtlas

create-speclisted

Guide a collaborative discussion that produces a comprehensive specification document at .turbo/specs/<slug>.md. Use when the user asks to "create a spec", "write a spec", "discuss a project plan", "spec out a project", "design a system", "let's plan this project", "help me scope this", "architect a solution", or "let's discuss before building".
tobihagemann/turbo · ★ 419 · Testing & QA · score 89
Install: claude install-skill tobihagemann/turbo
# Create Spec Guide a collaborative discussion to explore a project idea, then synthesize the conversation into a comprehensive specification at `.turbo/specs/<slug>.md`. ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Capture the vision and pick a slug 2. Deep-dive discussion 3. Draft the spec 4. Run `/review-spec` skill 5. Run `/evaluate-findings` skill 6. Run `/apply-findings` skill 7. Review and finalize ## Step 1: Capture the Vision and Pick a Slug Absorb whatever the user has provided — a sentence, a paragraph, a brain dump. Do not interrupt or ask questions yet. Restate the vision back in two or three sentences to confirm understanding. Pick a slug for the spec file derived from the project or feature name: - Lowercase - Replace non-alphanumeric characters with hyphens - Collapse consecutive hyphens - Trim leading and trailing hyphens - Truncate to 40 characters at a word boundary Example: "Photo Sorter v2" → `photo-sorter-v2`. The user may pass an explicit slug; if so, honor it. If `.turbo/specs/<slug>.md` already exists, use `AskUserQuestion` to ask whether to overwrite, append a numeric suffix (`-2`, `-3`, ...), or pick a different slug. State the chosen slug and the resulting spec path before continuing. Then use `AskUserQuestion` to ask 1-4 focused opening questions targeting the biggest unknowns. Skip anything the user already answered. Prioritize from: - What problem does this solve, and for whom? - Is this greenfi