architect

To create an implementation plan, you need to generate multiple design options by evaluating technical and operational trade-offs. This process produces structured documentation comparing alternatives based on complexity, performance, cost, and migration effort.

Analyzing system design risks involves assessing potential operational and technical trade-offs across multiple implementation plans. This approach identifies named mitigations and suggests the most appropriate path forward for your project documentation.

Documenting system design decisions requires generating structured files like plan.md or design.md. These documents outline design alternatives, risk assessments, and recommendations, making them suitable for future reference and team collaboration.

Yes, comparing system architecture alternatives involves evaluating at least two or three design options. This comparison assesses factors like complexity, performance, and cost to deliver structured documentation outlining the recommended path forward.

You need to generate design documentation during the architecture phase of a software feature or bug fix. It enables informed decision-making by providing detailed implementation plans with trade-offs and risk analysis for system design.