メニュー
Conducts structured brainstorming with divergent thinking and trade-off analysis. Use when the user asks "help me think through this," "what are the options," or is exploring tradeoffs. Produces docs with sparks. Not for quick ideas or shaping.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Documents how agents operate the Loaf CLI: command discovery via loaf --help, JSON diagnosis surfaces, guided config maintenance, and troubleshooting. Use when unsure which loaf command to invoke or how to validate project state. Not for workflow guidance (workflow skills own their CLI contracts) or build internals.
Orchestrates standalone releases from already-landed work: release readiness, version selection, changelog curation, release commit, tag, GitHub Release, install verification, and post-release follow-up. Use when the user says "cut a release," "publish a version," "release from main," or asks whether enough landed work should become a release. Not for reviewing or merging a PR (use ship).
Shapes messy input into a bounded, reviewable Change under docs/changes/YYYYMMDD-slug/, validated by loaf change check. Runs a fog-routed narrowing protocol — gather context, an optional blindspot pass, grilling for known unknowns, reaction artifacts for unknown-knowns — decomposes Implementation Units ordered by likelihood-of-change, runs a critique gate, and offers an opt-in draft PR. Use when the user asks "shape this," "turn this into a Change," or an idea has accumulated enough constraints to bound. Recognizes journal entries, sparks, ideas, brainstorms, Linear issues, PR conversations, and plain conversation as input. Produces a Change, never a numbered spec or task file. Not for quick capture (use idea) or open-ended divergent thinking before scope exists (use brainstorm).
Documents how agents operate the Loaf CLI: command discovery via loaf --help, JSON diagnosis surfaces, guided config maintenance, and troubleshooting. Use when unsure which loaf command to invoke or how to validate project state. Not for workflow guidance (workflow skills own their CLI contracts) or build internals.
Orchestrates standalone releases from already-landed work: release readiness, version selection, changelog curation, release commit, tag, GitHub Release, install verification, and post-release follow-up. Use when the user says "cut a release," "publish a version," "release from main," or asks whether enough landed work should become a release. Not for reviewing or merging a PR (use ship).
Shapes messy input into a bounded, reviewable Change under docs/changes/YYYYMMDD-slug/, validated by loaf change check. Runs a fog-routed narrowing protocol — gather context, an optional blindspot pass, grilling for known unknowns, reaction artifacts for unknown-knowns — decomposes Implementation Units ordered by likelihood-of-change, runs a critique gate, and offers an opt-in draft PR. Use when the user asks "shape this," "turn this into a Change," or an idea has accumulated enough constraints to bound. Recognizes journal entries, sparks, ideas, brainstorms, Linear issues, PR conversations, and plain conversation as input. Produces a Change, never a numbered spec or task file. Not for quick capture (use idea) or open-ended divergent thinking before scope exists (use brainstorm).
| name | brainstorm |
| description | Conducts structured brainstorming with divergent thinking and trade-off analysis. Use when the user asks "help me think through this," "what are the options," or is exploring tradeoffs. Produces docs with sparks. Not for quick ideas or shaping. |
| version | 2.0.0-alpha.5 |
Generative thinking — expanding possibilities before narrowing through structured exploration.
Always
loaf journal log "skill(brainstorm): <topic>"loaf spark capture --scope <scope> --text <text>; brainstorm summaries may render or summarize themloaf journal log "decision(scope): direction chosen and rationale"Never
After work completes, verify:
loaf spark capture and optionally summarized in ## Sparks| Input Pattern | Mode | Output |
|---|---|---|
| Idea file reference | Idea Processing | Deep dive on captured idea |
| Problem/question | Problem Exploration | Exploratory options |
| Empty | Open Brainstorm | "What should we think about?" |
## Sparks
- **Title** -- one-line description
- **Title** -- one-line description
Sparks are: lightweight, byproducts, worth remembering. Mark as *(promoted)* or *(abandoned)* after processing.
Brainstorm documents are archived after sparks are processed — never deleted, since the exploration context has lasting value. SQLite spark state is the lifecycle source; draft markdown is a projection or narrative summary.
After brainstorming, suggest /shape if a clear idea emerged, or /idea to capture sparks for later. /idea invoked without arguments scans brainstorm docs for unprocessed sparks, bridging the brainstorm → idea pipeline.
| Topic | Reference | Use When |
|---|---|---|
| Brainstorm Template | templates/brainstorm.md | Creating structured brainstorm documents |
| Strategic Context | strategy/references/ | Grounding exploration in project direction |