rb-brainstorm

To turn a fuzzy idea into a design doc, you can use a brainstorming workflow that runs an interactive Q&A loop to define goals, non-goals, and constraints, ultimately producing a structured document ready for kanban planning.

The best way to discover requirements before creating board cards is through a structured, one-question-at-a-time discovery process that identifies goals, constraints, key uncertainties, and prior art to ensure alignment.

Board-aware brainstorming prevents duplicate work by reading existing kanban board cards and prior project documentation before starting the design exploration, keeping the discussion aligned with the current project status.

Yes, you can compare approach tradeoffs during design document generation by producing two to three candidate approaches and evaluating them with clear pros and cons before making a final selection.

To hand off a validated design doc to a planning workflow, you save the finalized document into the .agent-history directory and optionally trigger the downstream planning tool using the generated design doc as input.