Brainstorming Conventions

Overview

REQUIRED SUB-SKILL: Invoke superpowers:brainstorming — it owns the actual design process (spike/bounded/architectural classification, clarifying questions, approaches). This skill is a required pre/post layer around it: native Plan Mode wiring, trigger-phrase recognition, and where the resulting spec lives.

Trigger Phrases

An invitation to jointly think through an architectural/creative decision — in whatever language this developer communicates in (this developer's own trigger: «давай подумаем» / "let's think about this", «подумаем над этим» / "let's brainstorm this") — is a direct trigger to launch superpowers:brainstorming immediately, not a reason to answer with a short inline opinion in exploratory-question format. Keep the literal phrase in its original language alongside an English duplicate, since matching happens against real user input in that language, not its translation.

Plan Mode Wiring

• Enter native Plan Mode before invoking superpowers:brainstorming — not after.
• Native Plan Mode's turn-ending rule applies throughout, including the design-writing steps: every turn while Plan Mode is active ends with ExitPlanMode or AskUserQuestion — never a plain-text question or statement asked as chat prose without one of those two tools.
• Once the design is approved conversationally, call ExitPlanMode to trigger the review gate — a plain-text confirmation doesn't substitute for it.
• Each document on its own approval cycle. If a single task produces several separate documents for approval in sequence (a design spec, then an implementation plan), each gets its own independent EnterPlanMode → draft → ExitPlanMode → save cycle. Don't append the next document to the same Plan Mode service file that still holds an already-approved one — the approval UI shows the whole file, and the already-approved document would be shown for "re-approval." Before starting the next document, make sure the service file holds only its draft.

Spec Placement