ck:brainstorm

Evaluate architecture trade-offs by generating 2-3 distinct approaches with clear pros, cons, and recommended trade-offs. This process surfaces hidden risks and grounds monolith to microservices decisions in feasibility and maintainability rather than assumptions.

Facilitate system design decisions by guiding stakeholder-aligned designs through iterative clarification and scope decomposition. This requires documenting a design approval and performing readiness checks before any implementation begins.

Yes, you can use this for feasibility assessments and feature design under tight deadlines. It evaluates architectural options against constraints like a 6-month timeline or a 3-person team to produce pragmatic, stakeholder-approved designs.

Identify technical debt and operational risks by analyzing proposed architecture options for hidden flaws. The analysis proposes mitigation strategies and success metrics to ensure long-term maintainability before implementation approval.

Avoid this system design brainstorming approach when you need immediate implementation without stakeholder alignment or scope decomposition. It requires iterative clarification and documented design approval, making it unsuitable for rapid, undocumented prototyping.