skills.rest
rajyeole6
rajyeole6COMMUNITY
Explore all skills by this author →
GitHub

agency-software-architect

Guide domain-driven design and document architectural decisions with ADRs.

Updated Jul 23, 2026
Search Tags:#architecture#software engineering#scalability#system design#adr#ddd
One-click install
npx skills add https://github.com/rajyeole6/AI-RECRUITER --skill agency-software-architect-rajyeole6
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-software-architect
Source: https://github.com/rajyeole6/AI-RECRUITER/tree/main/.agents/skills/engineering-software-architect
Command: npx skills add https://github.com/rajyeole6/AI-RECRUITER --skill agency-software-architect-rajyeole6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the complexity of designing software systems by providing a structured framework for domain modeling, architectural decision-making, and trade-off analysis, preventing over-engineering and technical debt.

Core Features & Use Cases

  • Domain-Driven Design (DDD): Guides the identification of bounded contexts, aggregates, and domain events to ensure the software aligns with business logic.
  • Architectural Decision Records (ADR): Provides a standardized template to document the context, rationale, and consequences of technical choices.
  • Trade-off Analysis: Evaluates architectural patterns like microservices, modular monoliths, or event-driven designs based on specific project constraints and scalability needs.

Quick Start

Use the agency-software-architect skill to evaluate the trade-offs between a modular monolith and microservices for a new e-commerce platform.

Frequently Asked Questions about agency-software-architect

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

FAQPage Schema
How do I document architectural decisions to prevent technical debt?▼

To document architectural decisions and prevent technical debt, use Architectural Decision Records (ADR) to capture the context, rationale, and consequences of technical choices in a standardized format.

What is domain-driven design and how does it guide system architecture?▼

Domain-driven design (DDD) is a modeling approach that identifies bounded contexts, aggregates, and domain events to ensure your software architecture aligns directly with underlying business logic.

How do I evaluate trade-offs between microservices and a modular monolith?▼

Evaluating trade-offs between microservices and a modular monolith requires analyzing specific project constraints and scalability needs to determine the most maintainable architectural pattern for your system.

When should I use event-driven design in software system design?▼

You should use event-driven design in software system design when your project constraints require high scalability and decoupled communication, determined through a structured trade-off analysis of architectural patterns.

Does this software architecture guidance apply to existing system reviews?▼

Yes, this software architecture guidance applies to the design phase of new software development projects, architectural reviews of existing systems, and ongoing technical decision-making processes.

Related Skills

Explore More Software Engineering Skills→
FoundationForgeFoundationForge

system-design

Identifies architectural needs and generates a documented system design plan.

Official
Advanced
Imad-OuteImad-Oute
2

mh-cto-sdlc-system-decomp

Decompose systems into services and document boundary decisions with ADRs.

Community
Advanced
softmgsoftmg

Pair Programming

Coordinate role-based pair programming sessions with automated testing and verification.

Official
Advanced
allaydesaiallaydesai
2

bmad-agent-architect

Guide distributed system and cloud infrastructure architecture design decisions.

Community
Advanced