agent-architect

Define system boundaries, contracts, and ADR-style architectural decisions.

Updated Jan 29, 2026
One-click install
npx skills add https://github.com/fabiomilennials1234-a11y/v8milennialsb2bv2 --skill agent-architect-fabiomilennials1234-a11y
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-architect
Source: https://github.com/fabiomilennials1234-a11y/v8milennialsb2bv2/tree/main/.claude/skills/agent-architect
Command: npx skills add https://github.com/fabiomilennials1234-a11y/v8milennialsb2bv2 --skill agent-architect-fabiomilennials1234-a11y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Principal engineer agent — system design, architectural decisions, trade-offs, domain modeling. Thinks in systems and boundaries, not features. Invoked by Conductor for architectural decisions.

Core Features & Use Cases

  • Define system boundaries, modules, and service contracts to clarify responsibilities.
  • Evaluate trade-offs across reliability, scalability, and maintainability using 3-horizon thinking.
  • Produce ADR-style decisions and architectural guidance to align stakeholders.

Quick Start

Propose a high-level system architecture with boundaries, contracts, and trade-offs for the given domain.

Frequently Asked Questions about agent-architect

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

FAQPage Schema
How do I define system boundaries and service contracts for domain-driven design?

Define system boundaries by identifying and articulating components, modules, and contracts to clarify responsibilities, enabling scalable architectural decisions across domain-driven design patterns.

What is the best way to evaluate architecture trade-offs for multi-tenancy and caching?

Evaluate architecture trade-offs using tri-horizon thinking across reliability, scalability, and maintainability to assess multi-tenancy, caching, and data flow options for safe, auditable changes.

How do I document architectural decisions to align stakeholders on system design?

Document architectural decisions by producing ADR-style decisions and architectural guidance that enforce rigorous decisioning, tri-horizon evaluation, and documentation for safe, auditable architecture changes.

Can I use tri-horizon evaluation for event-driven architecture and domain modeling?

Yes, tri-horizon evaluation applies across event-driven patterns, domain modeling, and domain-driven design to articulate system boundaries, evaluate trade-offs, and ensure scalable architectural decisions.

When should I not use a high-level system architecture approach for domain boundaries?

Avoid high-level system architecture approaches when features require immediate tactical fixes rather than rigorous ADR-style decisioning, tri-horizon evaluation, and formal boundary and contract definitions.

How do I propose a high-level system architecture with clear boundaries and contracts?

Propose a high-level system architecture by identifying system boundaries, components, and contracts, then evaluating trade-offs across reliability, scalability, and maintainability for the given domain.