Brainstorming

Brainstorming is the space for exploring options before you commit to implementation.

Use it when the problem is still open, the architecture is not settled, or you want several realistic directions before turning one of them into a spec.

What Brainstorming Is For

Brainstorming is not the best surface for immediate code edits. It is the best surface for decision work.

Typical uses:

• compare multiple implementation strategies
• explore tradeoffs before a refactor
• evaluate architecture options for a new feature
• turn an ambiguous request into a written spec

How Brainstorming Works

Brainstorming runs as a dedicated workflow instead of a normal chat loop.

It moves through phases such as:

• intent
• divergence
• simulation
• convergence
• crystallization
• completed

In practice, Knotic starts from your intent, explores the codebase with read-only analysis, proposes branches, lets you compare them, and then generates a spec from the branch you approve.

When you approve a spec, Knotic saves it under .knotic/spec/<slug>.spec.md. That spec can then be loaded into Architect.

At the moment, starting a Brainstorming session requires a Knotic license key.

How To Use Brainstorming

1. Open Brainstorming with Ctrl+Alt+B.
2. Submit a clear intent such as the decision you need to make.
3. Review the proposed branches.
4. Reject weak directions and select promising ones.
5. Expand a branch if you need deeper options.
6. Generate a spec from the approved direction.
7. Send the result to Architect when you are ready to execute.

How To Read The UI

Brainstorming is organized around decision-making rather than chat alone.

• input area: where you define the original intent
• decision tree or graph: where branches and alternatives are displayed
• analysis and message timeline: where you follow the reasoning and grounding work
• session history: where you return to earlier brainstorming sessions
• spec view: where the generated spec is reviewed and approved

When To Use Brainstorming Instead of Sessions

Use Brainstorming when the main problem is choosing the right direction.

• Use Sessions when you already know what you want to do.
• Use Architect when the direction is chosen and the next step is execution.

Good Practices

• Phrase the intent as a decision, not as a vague area of interest.
• Keep only the branches that are meaningfully different.
• Generate a spec only after one direction is genuinely approved.
• Treat the spec as the handoff point between exploration and execution.