brainstorm

Use when a person wants to think an idea through and keep the discussion: a feature, a tool choice, an architecture question, before a plan or without one, with the agent through an interview. Produce

SKILL.md

GitHub

Brainstorm

The discussion lives in one Markdown file from the first question, never in chat. YYYY-MM-DD-<topic>.brainstorm.md, through the aiview skill: kind brainstorm, tags = topic, group = the topic. With a roadmap, the slot's slug is a tag. A resuming session reads the board before asking anything again.

Run the interview skill and write each answer into the board as it lands.

The person asks for a swarm of seats to brainstorm or debate it: the brainswarm skill runs it on this board.

The board, in this order:

  • Human part, written as the aiview skill's references/human-part.md says, refreshed at each settled decision.
  • Strategy, a brainswarm only.
  • Decisions table: the row core of the interview skill's references/decisions.md, plus Log (the entry Q7). The interview's experiments option is its first row.
  • Context being built on.
  • Diagrams, through the write-diagrams skill, drawn during the questions.
  • What ran: the recipes the experiments hand back.
  • Interview log, or a brainswarm's log, last: per question, verbatim, the options and the recommendation, then the answer as given.

No code in the repository for the thing being discussed.

Close by saying what is agreed and what is open.