superpowers-sage:architecting

To define architecture before building, you capture Architecture Decision Records (ADRs), map data flows, and establish component boundaries to guide implementation. This process ensures design system readiness and produces actionable architecture documentation for multi-block workstreams.

The best way to plan system design for multi-block workstreams is to orchestrate discovery and planning steps, validate design system readiness, and generate architecture documentation. This approach identifies system boundaries, dependencies, and produces actionable implementation plans.

You need architecture discovery and design validation when starting multi-block Sage/Acorn features. It identifies system boundaries and data dependencies early, ensures alignment with design system readiness, and produces the ADRs required to guide subsequent implementation phases.

Yes, the architecture planning process validates design system readiness as a core pre-implementation check. It ensures your architecture decisions, data flows, and component boundaries align with design requirements before you generate the final implementation plan.

Yes, you can generate an actionable implementation plan directly from your architecture decisions. The plan generation step takes your defined ADRs, data flows, and component boundaries and translates them into a structured guide for building.

Capturing component boundaries and data flows before writing code prevents architectural drift and integration conflicts. It provides clear constraints for implementation, validates dependencies, and ensures the final feature adheres to the planned system design.