agency-software-architect

Designs software architectures using domain-driven design, pattern selection, and architecture decision records.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system --skill agency-software-architect-ai-staffing-solution-consultants-llc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-software-architect
Source: https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system/tree/main/.agents/skills/engineering-software-architect
Command: npx skills add https://github.com/AI-Staffing-Solution-Consultants-LLC/core-engineering-system --skill agency-software-architect-ai-staffing-solution-consultants-llc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It helps teams make sound software architecture decisions by applying domain-driven design, architectural pattern selection, and structured trade-off analysis instead of defaulting to over-engineered or under-designed systems. ## Core Features & Use Cases - Domain Modeling: Identify bounded contexts, aggregates, domain events, and anti-corruption layers through event storming and context mapping. - Architecture Pattern Selection: Compare layered, hexagonal, onion, modular monolith, microservices, event-driven, and CQRS patterns with explicit use-when and avoid-when guidance. - Architecture Decision Records: Capture context, decision, and consequences in a standard ADR template so the reasoning behind choices is preserved. - Use Case: When splitting a growing monolith, use this Skill to map bounded contexts, evaluate modular monolith versus microservices trade-offs, and document the decision as an ADR. ## Quick Start Ask the architect to evaluate whether your current system should adopt hexagonal architecture and produce an ADR documenting the trade-offs.

Frequently Asked Questions about agency-software-architect

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

FAQPage Schema
How do I choose between a modular monolith and microservices?▼

Choose a modular monolith when the team is small and domain boundaries are still unclear. Choose microservices when domains are well-defined and teams need independent deployment and scaling autonomy.

When should I use domain-driven design for a project?▼

Use DDD when business rules, invariants, and organizational boundaries are more complex than the technical plumbing. Avoid it for simple CRUD or reporting systems where a layered design is easier to maintain.

What is the difference between hexagonal and onion architecture?▼

Hexagonal architecture isolates core use cases from UI, databases, and external APIs through ports and adapters. Onion architecture places the domain model at the center with strict inward dependency rules across concentric layers.

How do I write an architecture decision record?▼

An ADR captures the status, context motivating the decision, the decision itself, and its consequences. The goal is documenting why a choice was made, not just what was decided, so future teams understand the trade-offs.

When should I avoid event-driven architecture?▼

Avoid event-driven architecture when the system requires strong consistency across operations. It fits loosely coupled, asynchronous workflows but complicates transactional guarantees and debugging across services.