plastic-intent-brainstorming

# Brainstorming Ideas Into Designs Help turn ideas into fully formed designs through natural collaborative dialogue. Announce: "I'm using the brainstorming skill to explore the design for intent {id}: {name}." Start by understanding the current project context, then ask questions one at a time, in prose, to refine the idea. Once you understand what you're building, present the design and collect the owner's rulings on it. This skill's product is the enriched Why, not spec.md. <HARD-GATE> Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has ruled on it. This applies to EVERY project regardless of perceived simplicity. </HARD-GATE> ## Active Intent Gate Before proceeding, resolve the active intent: 1. **Detect store:** Read `~/.plastic/projects.yml`, match CWD against registered project paths. If match → project store at `~/.plastic/projects/{slug}/store/`. If no match → global store at `~/.plastic/store/`. 2. **Find active intent:** Read `INDEX.md` from the detected store. Look under `## Active`. If exactly one → use it. If multiple → ask which. If none → refuse: "No active intent. Create one first with /plastic-intent-creating" 3. **Resolve intent directory:** `{store}/store/{id}--{slug}/` All artifacts go to the intent directory. Never write to external paths. ## Anti-Pattern: "This Is Too Simple To Need A Design" Every project goes through this process. A ...