explore-idea

Topics in the source

• Explore-idea Workflow
• When to load
• Steps
• Step 1: Size the request — out loud
• Step 2: Explore context before asking anything
• Step 3: Check scope early
• Step 4: Ask one question at a time
• Step 5: Gate on research instead of guessing

Talk an idea into shape with an owner who may not be an expert, one decision at a time, until the direction is agreed. The skill ends at the hand-off: it writes no spec, no plan and no code. It owns one durable file, status/ideas.md — the ideas backlog and decision log, committed so the next session starts from it. Any other scratch goes in tmp/, never in status/. CANARY: explore-idea-loaded-2026-09-29-fb78d23e-0a0a801de422d737 Load when there is an idea but no problem statement yet — a new project, a "what if we…", a choice the owner cannot frame — or a pile of ideas to sort and keep for later. Use it rather than another plugin's brainstorming skill, which tends to skip the annotated review specify requires. A stated problem goes to specify; an approved spec goes to design. Capture mode — /explore-idea capture , or several ideas dumped at once: read status/ideas.md if it exists, file each idea under a lettered group with the next I-N id, propose sub-projects (S-N) built from the groups, write the file, and ask only which sub-project to explore first, if any. No deep questioning; unchosen sub-projects stay parked. Load ideas backlog before writing the file. Classify before explorin

This is an excerpt. Refer to the complete source and its current requirements.