atmos-specs-brainstormlisted

# Atmos Specs · Brainstorm Help the user think out loud about a feature before it becomes a PRD. The output goes into a single file: `specs/<ZONE>/<ZONE>-NNN_<title>/BRAINSTORM.md`. ## What this skill owns — and what it does not - **Owns**: the BRAINSTORM.md of exactly one spec directory. - **Does not own**: PRD.md, TECH.md, TEST.md. Do not create or edit them in this skill — even if the conversation drifts toward product requirements or architecture. Note promising material at the bottom of BRAINSTORM.md as "Ready to promote to PRD / TECH" bullets instead. Why: brainstorm is the divergent step. Mixing in PRD language collapses the option space too early, and mixing in tech design commits to a solution before we know the problem is worth solving. ## Read these before you write 1. `specs/AGENTS.md` — the canonical conventions (zones, naming, 4-file rule). 2. `specs/README.md` — the Current Specs inventory table. 3. If updating an existing spec, read that spec's existing `BRAINSTORM.md` + `PRD.md` (if any) so you don't rehash or contradict. ## Workflow ### 1. Decide the spec location - **Zone** (`APP` / `Landing` / `Docs`): derive from what the feature ships to. When ambiguous, ask once. - **Number**: look at `ls specs/<ZONE>/` and take the next unused `NNN`. - **Title**: short, kebab-case, noun-ish (`terminal-session-sharing`, not `feat-share-v2`). - Final path: `specs/<ZONE>/<ZONE>-NNN_<title>/BRAINSTORM.md`. If the directory doesn't exist yet, create the full 4-fil