#1
We should keep the meeting bot for recaps, but give brainstorm sessions a live board with notes, tasks, and repo context.
Live transcript
What Marvin is hearing right now, with emphasis on actionable phrases.
#2
The board should surface the active repo first, then let the session generate spec text and task candidates without waiting for the end of the call.
#3
If the request is clear, Marvin should update Linear immediately. If it is ambiguous, it should ask in Discord and keep the session moving.
#4
For Blue Dolphin, the board should read the repo rules first, then update spec, todo, and diagrams as the conversation evolves.
Next move
Update the brainstorm board with the repo-scoped spec, then surface any clear Linear action immediately.