arc-brainstorm

To structure scattered brainstorming ideas into architecture decisions, this Skill identifies project constraints and goals, then proposes 2-3 bounded design approaches with clear trade-offs for user approval before capturing the final plan.

The best way to compare design planning approaches is using a guided loop that explores project context and surfaces trade-offs between 2-3 bounded options, ensuring alignment before proceeding to implementation.

You capture design constraints and non-goals for decision traceability by documenting the approved bounded design approach, which records all decisions and context for future reference and audits.

Yes, you can register approved designs with arc planner. The Skill captures the approved design in docs/plans, registers it with arc plan, and surfaces the plan-id and planner URL for immediate handoff.

Yes, arc brainstorming requires user approval before proceeding. It presents 2-3 bounded design approaches with their respective trade-offs and explicitly requests user approval before capturing the final design.

Converting brainstorming sessions into planner-ready artifacts ensures teams align on constraints and goals, establishes decision traceability, and enables seamless handoff to arc-plan workflows before implementation begins.