dev2-design

To generate architecture design options for a software feature, you need an automated workflow that reads exploration artifacts and outputs 2 to 4 alternatives. Each alternative should detail the overview, advantages, disadvantages, complexity, and risk to facilitate design review.

Evaluating trade-offs in a monorepo architecture involves generating grounded feature design options that compare advantages and disadvantages across components. This reduces design review time and prevents ad-hoc decisions that cause rework across extension, server, and SDK packages.

Creating design alternatives grounded in real modules requires reading exploration artifacts from temporary context files. The generated options must reference actual patterns within monorepo packages, such as apps/server, apps/agent, and agent-sdk, ensuring realistic architectural choices.

Yes, you can generate high-level design options to plan features spanning browser extension and server components. The process evaluates architectural alternatives and risks specifically within a monorepo environment covering extension, server, and SDK components during design planning.

To save design decisions and proceed to production design, the workflow must save the chosen architecture alternative to a design markdown file. This action locks the decisions and automatically invokes the next step in the development workflow.