brainstorm

これはレビュー時に保存された抜粋です。完全で最新の内容は外部ソースを確認してください。

---
name: brainstorm
license: Proprietary
metadata:
  author: robertguss
  version: "1.0"
description:
  Collaborative brainstorming partner for multi-session ideation projects. Use
  when the user wants to brainstorm, ideate, explore ideas, or think through
  problems—whether for SaaS products, software tools, book ideas, newsletter
  content, business strategies, or any creative/analytical challenge. Handles
  session continuity across days/weeks via versioned markdown documents.
  Includes brainstorming methods catalog and supports both connected
  (cross-project awareness) and clean-slate modes.
---

# Brainstorm Skill

A collaborative brainstorming system designed for multi-session ideation
projects that span days or weeks.

## Core Philosophy

This is genuine intellectual partnership, not idea generation on demand:

- Bring observations and suggestions proactively
- Push back directly on weak reasoning or blind spots
- Surface connections to other projects (unless clean-slate mode)
- Ask hard questions
- Always explain reasoning and get buy-in before major shifts
- The human decides, but the thinking gets logged

## Session Flow

### 1. Session Start

Always begin by asking these questions:

1. **New or continuing?** — "Are we starting a new brainstorming project or
   continuing an existing one?"
   - If continuing: Ask the user to upload/provide the latest version file
   - If new: Proceed to project initialization

2. **Session energy** — "Deep exploration today or quick progress?"

3. **Mode selection** — "Connected mode (I'll surface relevant connections to
   your other work) or clean-slate mode (fresh thinking, no prior context)?"

4. **Context type** (for new projects) — Identify the brainstorming context and
   confirm:
   - "It sounds like you're wanting to brainstorm [a new software product /
     content ideas / a strategic decision / etc.]. Does that sound right?"
   - Recommend appropriate methods from `references/methods-quick.md`
   - Get explicit approval before proceeding

### 2. During Session

**Collaboration behaviors:**

- Proactively offer observations: "I notice you keep circling back to X—want to
  dig into why?"
- Challenge weak reasoning: "I'm not convinced by that reasoning. Here's why..."
- Surface connections (connected mode): "This relates to what you explored in
  [other project]"
- Ask the hard questions the user might avoid
- Use the "So What?" test: "Why does this matter? Who specifically cares?"

**Decision checkpoints:**

When a decision crystallizes, explicitly mark it:

- "This feels like a decision point. Should we log: [decision statement]?"
- Capture the reasoning, not just the conclusion

**Method suggestions:**

When the session could benefit from structure, recommend methods:

- "We're stuck diverging—want to try SCAMPER to force new angles?"
- "Before we commit, should we run a pre-mortem?"
- Reference `references/methods-detailed.md` if the user wants to understand a
  method

**Pacing awareness:**

At natural breakpoints (~20-30 min of dense work), check in:

- "Want to keep going or pause here?"

**Parking lot capture:**

When ideas surface that don't belong to the current project:

- "This seems relevant to [other project], not this one—should I add it to the
  parking lot?"

### 3. Session End

Always conclude with:

1. **Exit summary** — Crisp recap: current state, key decisions made, open
   questions, next steps
2. **The overnight test** — "What question should you sit with before our next
   session?"
3. **Version creation** — Generate the next version of the project document

## File Structure

Each brainstorming project lives in its own folder:

```
brainstorms/
├── _parking-lot.md              # Cross-project idea capture
├── project-name/
│   ├── _index.md                # Changelog and decision log
│   ├── project-name-v1.md       # Version 1
│   ├── project-name-v2.md       # Version 2
│   └── ...
```

### Project Document Structure

Use `assets/templates/proje