Brainstorming

You lead, the AI maps

The brainstorming skill guides an agent from reading the codebase to a decision map: open questions, their consequences and dependencies. You edit the map, then work through a few questions at a time. The agent states what it has established from the code and asks you to decide the direction and scope.

The session ends in two committed artifacts on the feature's epic: a short decision log — decisions, assumptions, architecture notes — and a feature brief composed from your answers (vitrinka task brief <epic>), whose work packages are the plan. The build starts from the brief; the log is the approval. A brainstorm runs at the default level (one to three rounds) or deep (board from the start, architectural path). The last question asks how to build — here, in a fresh session, or with subagents.

The brainstorm studio

Heavy visual questions move from the terminal to a brainstorm, which opens in its own app, the studio: one chapter per decision, top to bottom, with the competing layouts or design directions side by side as real mockups at readable size, and the options right under them. Brainstorms in the Boards module lists every brainstorm grouped by what waits for you. Inside one, you:

• Pick — click a take or its option; picks stage and go together when you press ↑ Send in the header (how staging works). A note opens under your pick.
• Write in — every question carries an "Other" escape; typing is answering.
• Ask for more — ask about any decision and the agent's answer streams into the chapter: what the codebase says, the tradeoffs, why the recommendation.
• ↻ Regenerate — when your answers change the direction, regenerate (with a few seconds to undo): the agent retracts the stale open questions and composes the next frontier in their place.
• Add to a chapter — a note, idea, pro, con or risk, an image or an HTML mockup; or mark a region of a take and say what should change. Marked regions go to the agent with your next send.

The outcome panel on the right is the live decision table: it jumps to any chapter, and holds the decision log and the plan once they exist. While the agent works, the header says so, and new chapters arrive marked without moving what you are reading.

The record survives the session

Questions, answers, notes and author information stay on the board after submission. Retracted questions remain marked, so you can revisit discarded options and the reasons behind a decision.

Bind the session to a sprint or no sprint before filing feature work. Accepted decisions and retained original attachments can later appear as evidence in Product history.

From the brief to a merged feature

The epic carries the feature from the first question to the last artifact:

• The build — in Claude Code, /vitrinka-experimental:make-idea <idea> maps the terrain the idea stands on, runs this brainstorm with you, then builds unattended: slices implemented in the feature's worktree, one quick check, a draft pull request. You decide twice — in the brainstorm and with the feature in front of you, when /vitrinka-experimental:test picks the device pass.
• The test plan — the epic's qa task and its journeys are the plan; vitrinka task qa-board <id> returns its board with the living journeys diagram (QA plans and test runs).
• The final artifact — vitrinka task final <epic> composes the feature board and a versioned final page from everything the epic carries.