ck:brainstorm

To brainstorm architecture trade-offs, provide a concise problem statement with constraints and desired outcomes. The process generates two to three alternative approaches, each with clear pros, cons, risk assessments, and maintainability considerations for your system design.

Evaluating technical feasibility requires a structured ideation process that surfaces hidden assumptions through probing questions. This approach produces multiple design alternatives with explicit success metrics and risk assessments before any implementation begins.

Structuring technical decision-making involves enforcing a mandatory design approval gate before implementation. You provide the infrastructure scenario, and the process outputs a concise design summary requiring explicit user approval to proceed.

Yes, you can compare frontend and backend architecture choices. The process applies to design discussions across backend, frontend, infrastructure, and product scenarios, generating alternative approaches with comparative pros and cons.

You should not use structured brainstorming when you need to bypass design approval gates and immediately implement code. The process strictly insists on an explicit design summary and mandatory user approval before any implementation begins.