Architect Skill

What problem does it solve?

This Skill addresses the challenge of designing complex software changes by systematically evaluating architectural alternatives, documenting trade-offs, and ensuring alignment with project principles. It prevents costly rework by establishing a solid technical foundation before detailed specification.

Core Features & Use Cases

• Architecture Decision Records (ADRs): Guides the identification, evaluation (min. 2 alternatives), and documentation of significant architectural decisions, including pros, cons, and risks.
• Domain-Driven Design (DDD) Component Design: Maps bounded contexts, aggregates, entities, and value objects, ensuring a DDD Tactical Co-Located structure for maintainable code.
• C4 Model Visualization: Creates appropriate C4 diagrams (System Context, Container, Component) to visualize the system's structure and interactions for complex changes.
• Use Case: For a high-complexity feature like integrating a new payment gateway, this Skill designs the entire solution, from choosing the gateway (ADR), to defining the payment aggregate (DDD), and visualizing the system's interaction (C4), ensuring a well-thought-out and robust architecture.

Quick Start

When proposal.md indicates Complexity: HIGH and Requires Design Phase: YES, invoke the Architect: @skill architect