architect

Create ADRs and architectural guidance for design decisions.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/asalhamed/dev-agents --skill architect-asalhamed
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/asalhamed/dev-agents/tree/main/architect
Command: npx skills add https://github.com/asalhamed/dev-agents --skill architect-asalhamed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design systems, make architectural decisions, and produce ADRs (Architecture Decision Records).

Core Features & Use Cases

  • Provide structured ADRs to capture and communicate architectural decisions across bounded contexts.
  • Facilitate FP-friendly, DDD-aligned architecture modeling and decisions.
  • Drive design reviews and avoid scope creep by documenting trade-offs and constraints.

Quick Start

Identify architectural concerns early, model domains with bounded contexts, and produce ADRs that guide implementation.

Frequently Asked Questions about architect

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

FAQPage Schema
What is an Architecture Decision Record and when do I need one?

An Architecture Decision Record (ADR) is a structured document that captures and communicates architectural decisions. You need ADRs during feature design, system redesigns, or when addressing cross-cutting concerns to document trade-offs and avoid scope creep.

How do I create ADRs for systems using domain-driven design?

Create ADRs by modeling domains with bounded contexts and documenting FP-friendly architectural patterns. This process aligns domain-driven design decisions, captures constraints, and drives design reviews to streamline implementation guidance across bounded contexts.

What's the best way to document architectural trade-offs during a system redesign?

The best way to document architectural trade-offs is producing structured ADRs. This approach captures design decisions, drives design reviews, and clearly communicates constraints and trade-offs across bounded contexts during system redesigns.

Can I use functional programming patterns with domain-driven design architecture?

Yes, you can use functional programming (FP) patterns with domain-driven design. This skill facilitates FP-friendly, DDD-aligned architecture modeling to produce ADRs that guide implementation while maintaining resilient architectural boundaries.

Why does documenting cross-cutting concerns require architectural guidance?

Documenting cross-cutting concerns requires architectural guidance because these issues span multiple bounded contexts. Producing ADRs ensures clear decision documentation, aligns domain-driven design, and prevents scope creep when addressing these shared system constraints.