← ClaudeAtlas

shapinglisted

Turns a raw idea into an approved spec by questioning the user first. Use when the user has a new feature or product idea, says "I want to build...", or a request is vague with a design choice open. Not for clear small edits or bugs.
t8jwscc7qy-sketch/foma-skills · ★ 2 · AI & Automation · score 78
Install: claude install-skill t8jwscc7qy-sketch/foma-skills
Turns a raw idea into an approved spec. You ask and propose; the user decides, and their words go in the spec. Nothing gets built here. Uses: foma-skills:documenting (a decision that outlives the spec: a library chosen, an approach rejected). ## Steps 1. *Always.* Look before you ask: read the CLAUDE.md contract, `$ARGUMENTS`, anything the user pointed at, and the code or material the idea touches (grep, then ranges). If a spec for this idea exists, continue it. Never ask what the project or the conversation already answers. 2. *Always.* Pick the path and say it in one line. - Small, clear change (1-2 files, no design choice): say "small change, doing it directly" and stop; do the task. - Everything that matters is in the request: play it back in ≤5 lines with a short design (approach, why not the others), ask for ok, then hand off. No spec file unless asked. - The conversation already settled it: go to step 6, no re-interview. - Otherwise: the full path below. 3. Why first. Play the idea back as a problem in 2-3 lines, then ask open discovery questions, one per message, with no options attached: the last concrete time this hurt, what they do today instead, what success looks like to them. Then the appetite: how much time it is worth, and what gets cut first if it runs over. 4. Grill the decision tree in rounds. Track coverage internally, never print it: problem, user, workaround, success, appetite, scope, not-doing, constraints, risks, assumptions (clear / part