dev2-design

Generate 2-4 high-level feature design options by referencing the original feature request to ground each choice. Each option includes a descriptive name, overview, advantages, disadvantages, estimated complexity, and risk to support trade-off discussions.

Comparing design options during a review is best done by evaluating a structured set containing 2-4 high-level choices. Each choice provides a narrative overview, pros, cons, estimated complexity, and risk to help stakeholders reach consensus faster.

Yes, generating multiple feature design options reduces back-and-forth in product planning by providing clear trade-offs. Presenting 2-4 structured choices with pros, cons, complexity, and risk helps teams quickly align on the best design direction.

Yes, you need the original feature request and exploration findings to ground the generated options. Referencing these inputs ensures the 2-4 high-level design choices accurately reflect the scope and technical constraints for stakeholder decisions.

Record the chosen design for handoff after evaluating the trade-offs of the generated options. The process outputs a structured option set that captures the selected architecture, ensuring downstream teams have the finalized design direction.