メニュー
Use when an artefact is new or a stub without enough information to start making specific decisions. Explores the idea through collaborative Q&A, writes content into the artefact, then hands off to refine.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | shaping:brainstorm |
| description | Use when an artefact is new or a stub without enough information to start making specific decisions. Explores the idea through collaborative Q&A, writes content into the artefact, then hands off to refine. |
Takes an artefact that has no shape yet and explores it through collaborative Q&A. The output is an artefact with enough content to start making specific decisions, at which point it hands off to refine.
Do NOT write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it.If you don't have an artefact path and transcript path from the parent skill, read and follow shaping/assess first to set up the session.
brain_read(resource="router")). If the idea relates to existing artefacts, read them. Assess scope — if the idea describes multiple independent things, help decompose into separate artefacts before diving in.shaping/assess.brain_edit once the user approves each section.When the artefact has enough shape to start working through specific decisions, suggest the transition in plain language: "The design has enough shape to start working through specific decisions — want to continue?" If yes, read and follow shaping/refine.
Identify changed code and dispatch reuse, quality, and efficiency reviewer agents in parallel; return the raw findings list.
Review changed code for reuse, quality, and efficiency, and produce a triaged list of findings (no edits). Use after writing code, for simpler code with fewer bugs and better performance.
Provides guidance on good software design principles, with trade-off calibration, examples, and common failure modes. Applies when making decisions while writing, designing, or refactoring code, or evaluating trivial code for clarity, maintainability, and common mistakes.
Reviews code with a team against established software design principles, and returns triaged findings (no edits). Use when evaluating code, or after writing or refactoring complex code, systems or technical designs: for code that is clearer, easier to maintain, and avoids common mistakes.
Shared setup for shaping sessions. Determines if an artefact exists or needs creating, creates it if needed, starts the transcript, reads the type taxonomy. Called by the parent router or by any sub-skill invoked directly.
Shape an artefact through structured Q&A. Routes to the right sub-skill: brainstorm (new/unclear artefacts), refine (open decisions), or discover (exploration-driven artefacts like People and Ideas).