Architect Skill

Document architecture decisions by creating ADRs with alternatives and trade-offs, mapping bounded contexts using DDD tactical patterns, and generating C4 diagrams within an Arc42-based design.md to reduce risk and rework.

You need a formal architecture design phase when proposal.md indicates Complexity: HIGH or Requires Design Phase: YES, signaling that changes affect multiple bounded contexts and require infrastructure decisions before detailing specifications.

Map bounded contexts by applying DDD Tactical Co-Located patterns to define aggregates, entities, and value objects, ensuring a structured domain model that validates against project specs and quality rules before specification.

Communicate system architecture to stakeholders by producing C4 diagrams and Arc42-based documentation that visualize the system structure, ensuring the design.md is ready for Gatekeeper review before proceeding to the Specification phase.

Yes, the architecture design process specifically targets high-complexity changes affecting multiple bounded contexts, requiring documented Architecture Decisions, DDD tactical design, and C4 diagrams to validate infrastructure decisions.

Validate your architecture design by formalizing decisions in ADRs and structuring the design.md with DDD tactical design and C4 diagrams, ensuring it passes Gatekeeper review before moving to the Specification phase.