linear-brasa-brainstorm

To brainstorm design specs and save them to a Linear issue, you can use a structured brainstorming flow that writes the approved design directly into the issue description under a ## Design section using Linear MCP tools. This keeps decisions and context in one place.

Yes, the brainstorming workflow preserves existing sections like Implementation Plan when updating a Linear issue. It only appends or modifies the ## Design section within the issue description, ensuring your current implementation plans remain intact.

You can enforce an approval gate before saving a design to Linear issue tracking. The workflow requires a review gate before persisting the brainstormed design options, ensuring alignment with product goals before any updates are made.

The best way to run a guided brainstorm for WIL-X design iterations is to provide a specific WIL-X issue and execute a structured brainstorming session. The approved design is then persisted directly into the issue description under a ## Design section.

To keep scattered brainstorming conversations centralized in Linear, you can harness a formal brainstorming flow that persists the final design directly inside the issue as a ## Design section. This ensures all decisions and context are kept in one place.

A limitation when persisting design specs into Linear issue descriptions is that the workflow applies specifically to WIL-X workflows and brasa project design iterations. It requires Linear MCP tools for all fetch and update actions, limiting use outside this environment.