Architect Skill

Design architecture for high-complexity changes with ADRs, DDD mapping, and C4 diagrams.

4|1|Updated Oct 8, 2025
One-click install
npx skills add https://github.com/deMGoncalves/arq-specs-template --skill architect-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architect Skill
Source: https://github.com/deMGoncalves/arq-specs-template/tree/main/.claude/skills/architect
Command: npx skills add https://github.com/deMGoncalves/arq-specs-template --skill architect-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

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

Frequently Asked Questions about Architect Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
When should I use architecture design before building a feature?

Architecture design is essential for high-complexity changes affecting multiple bounded contexts, cross-cutting concerns, or external integrations. Use it when a proposal marks Complexity: HIGH or Requires Design Phase: YES to prevent costly rework and establish a solid technical foundation before detailed specification.

How do I document architectural decisions and trade-offs?

Architecture Decision Records (ADRs) systematically identify, evaluate at least two alternatives, and document significant decisions with pros, cons, and risks. This ensures decisions are transparent, justified, and traceable throughout the project lifecycle.

What is Domain-Driven Design component mapping and why use it?

DDD component mapping structures complex systems by defining bounded contexts, aggregates, entities, and value objects in a co-located, tactical design. This approach ensures code remains maintainable and aligns domain concepts with implementation architecture.

How do C4 diagrams help visualize complex software architecture?

C4 Model diagrams—System Context, Container, and Component levels—provide layered visualization of system structure and interactions. They communicate architecture clearly to stakeholders and help identify dependencies across complex changes.

Can I use this approach for integrating external systems like payment gateways?

Yes. The Architect Skill handles high-complexity integrations by designing the complete solution: selecting the gateway via ADR, defining aggregates via DDD, and visualizing interactions via C4 diagrams to ensure a robust, well-reasoned architecture.

What quality validations are included in the architecture design process?

Architecture design includes quality validations that ensure the solution meets project principles, addresses performance-critical requirements, and satisfies documentation needs including ADRs, DDD mappings, and C4 diagrams for comprehensive architectural coverage.