architecture-review

You can validate separation of concerns by assessing component boundaries and modularity across your project design docs. This architecture review process enforces clear interfaces, evaluates API consistency, and documents design trade-offs during planning and verification phases.

Reviewing API design and design patterns during project planning involves evaluating interfaces and API consistency against defined design principles. This ensures plan-to-implementation coherence and proactively documents architectural risks before development begins.

Checking architecture plan alignment involves verifying plan-to-implementation coherence during the verification phase. This process assesses component boundaries, documents architectural risks, and ensures the actual implementation matches the defined design principles.

Yes, you can use architecture review in an ultrawork session to assess component boundaries. Invoking the review during planning or verification phases enforces separation of concerns, validates API design, and enables evidence collection for design trade-offs.

You need to document architectural risks and design trade-offs during the planning and verification phases of your project. Documenting these risks ensures modularity, validates API consistency, and maintains separation of concerns across component boundaries.

Architecture review requires defined design principles to validate decisions effectively. Without these principles, the process cannot enforce separation of concerns, evaluate design patterns, or verify that component boundaries and API design meet the required standards.