sdd-propose

To evaluate trade-offs for software architecture approaches, generate 2–3 distinct strategies and assess each on implementation complexity, reversibility, blast radius, and testability to identify the optimal path.

The best way to propose strategies for a planned system change is to construct 2–3 concrete approaches, evaluate their architectural trade-offs, and save the selected proposal to memory context for future reference.

Memory context improves system design decision-making by storing structured content payloads of selected proposals, allowing you to compare architectural options and retrieve past trade-off evaluations during future planning.

Yes, you can compare software design options by evaluating each approach against specific criteria including implementation complexity, reversibility, blast radius, and testability to determine the safest and most effective strategy.

You need to generate multiple approaches for software architecture tasks when a planned change requires careful trade-off evaluation, ensuring you have at least one viable alternative before committing to a specific system design.

Saving selected proposals to memory helps with future system design tasks by retaining a structured content payload of the evaluated trade-offs, enabling consistent decision-making and contextual reference for subsequent architectural changes.