beads-architect

To plan an API design refactor with risk assessment, generate a structured architecture consult that outlines constraints, recommended approaches, trade-offs, alternatives, and step-by-step milestones for phased implementation. This provides a clear, handoff-ready plan for cross-cutting changes.

The best way to document architecture decisions for cross-cutting data-model changes is to draft a consult using an architect template. This captures boundaries, trade-offs, and an implementable plan that aligns cross-team decisions and guides subsequent subtasks.

Yes, you can use this architecture consult approach to guide refactors and API design for your platform. It generates structured guidance with risk analysis and step-by-step implementation plans specifically tailored for cross-cutting architectural changes.

The architecture consult workflow handles scope and constraints by reading task context and drafting a structured consult. It explicitly defines boundaries, constraints, alternatives considered, and milestones to ensure an implementable plan for data-model changes.

You need a structured architecture consult for API design when making cross-cutting architectural decisions that require risk assessment, clear boundaries, trade-off analysis, and a phased implementation plan ready for downstream execution.