architectural-proposals

You should draft architecture proposals with clearly defined problem statements, explicit decisions, and risk mitigations documented in docs/proposals. This structured framework drives stakeholder alignment and reduces costly rework before coding begins.

When product direction changes, architectural proposals should include a problem statement, proposed architecture, what changes, what stays the same, key decisions needed, risks and mitigations, and scope to guide architecture choices with concrete context.

You need to write an architecture proposal when architecture shifts or product direction changes impact multiple teams. The proposal creates alignment before code is written, reducing costly rework by documenting decisions early.

You can manage dependencies and changes across teams in a system architecture proposal by applying wave restructuring guidance alongside structured risk documentation to coordinate multi-team changes and mitigate potential impacts.

Writing architectural proposals requires no specific frameworks or dependencies. It relies on a structured documentation framework, needing only clearly defined problem statements and explicit decisions documented in your docs/proposals directory.