architect

Evaluate architecture patterns and produce ADRs and C4 diagrams.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill architect-arbazkhan971
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/architect
Command: npx skills add https://github.com/arbazkhan971/godmode --skill architect-arbazkhan971

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provide rigorous, actionable architecture decisions for systems that need clear structure, scaling, reliability, or maintainability improvements by evaluating trade-offs and producing formal artifacts that teams can implement and review.

Core Features & Use Cases

  • Pattern evaluation: Compare and score multiple architecture patterns (modular monolith, microservices, serverless, event-driven, CQRS, hexagonal) against system constraints and team factors.
  • Artifacts & diagrams: Produce Architecture Decision Records (ADRs), C4 diagrams (context and container minimum, with component/code details where needed), and bounded context maps.
  • Migration & validation: Recommend migration paths, coupling and dependency checks, quality attribute analysis, and commit-ready documentation for greenfield projects, rewrites, or scaling/migration efforts.

Quick Start

Run /godmode:architect and provide the system name, stage, team size, and key constraints to receive a comparison matrix, C4 diagrams, and an ADR.

Frequently Asked Questions about architect

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

FAQPage Schema
How do I evaluate microservices versus a modular monolith for system design?

System design pattern evaluation compares and scores microservices, modular monoliths, serverless, and event-driven architectures against your specific constraints and team factors. It generates a comparison matrix to guide your architecture decision.

How do I create architecture decision records and C4 diagrams for a new project?

To create architecture decision records and C4 diagrams, provide your system name, stage, team size, and key constraints. The process generates commit-ready ADRs, bounded context maps, and C4 context/container diagrams for your greenfield project.

What is the best way to plan a system architecture migration?

Architecture migration planning recommends migration paths by evaluating trade-offs between patterns like CQRS and hexagonal architecture. It includes coupling checks, dependency analysis, and quality attribute analysis to ensure a reliable system transition.

When do I need domain-driven design and bounded context maps?

You need domain-driven design and bounded context maps when assessing scaling or maintainability improvements. They help evaluate event-driven and hexagonal patterns, producing formal artifacts that teams can implement and review for complex systems.

Does this approach to system design work for serverless and event-driven architectures?

Yes, system design evaluation explicitly supports serverless and event-driven architectures. It compares them alongside monoliths, microservices, CQRS, and hexagonal patterns to evaluate trade-offs and produce quality attribute analysis for your target system.