engineering-engineering-software-architect

Designs software architectures using domain-driven design, trade-off analysis, and architectural decision records.

2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/30eggis/walwal-harness --skill engineering-engineering-software-architect-30eggis
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: engineering-engineering-software-architect
Source: https://github.com/30eggis/walwal-harness/tree/main/HR-Resource/engineering-engineering-software-architect
Command: npx skills add https://github.com/30eggis/walwal-harness --skill engineering-engineering-software-architect-30eggis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams struggle to make consistent, well-reasoned architectural decisions that balance scalability, maintainability, and business domain alignment, often resulting in systems that are hard to evolve or justify. ## Core Features & Use Cases - Domain-Driven Design: Identifies bounded contexts, aggregates, and domain events through event storming to align architecture with business domains. - Architecture Pattern Selection: Compares modular monoliths, microservices, event-driven, and CQRS patterns with explicit use-when and avoid-when guidance. - Architectural Decision Records: Produces ADRs capturing context, decision, and consequences so the reasoning behind choices is preserved. - Use Case: A CTO worker is assigned a mission to design a new order-processing platform; this Skill maps the domain contexts, evaluates microservices versus a modular monolith, and documents the final choice as an ADR. ## Quick Start Assign this worker a mission to design the system architecture for a new service and record the output as an ADR in the mission documents folder.

Frequently Asked Questions about engineering-engineering-software-architect

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

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

Choose a modular monolith when the team is small and domain boundaries are unclear; choose microservices when domains are well-defined and teams need autonomy. The Skill provides a comparison table covering event-driven and CQRS options as well.

How to write an architectural decision record?▼

An ADR captures the decision title, status, motivating context, the chosen change, and its consequences. The Skill includes a markdown ADR template that records why a decision was made, not just what was decided.

What is domain-driven design in software architecture?▼

Domain-driven design aligns architecture with business domains through bounded contexts, aggregates, and domain events. The Skill uses event storming for domain discovery and context mapping for upstream and downstream relationships.

When should I avoid event-driven architecture?▼

Avoid event-driven architecture when strong consistency is required across workflows. It fits loosely coupled, asynchronous processes, but synchronous transactional domains are better served by other patterns.

How does this worker receive assignments in the harness?▼

It operates as a hireable HR-Resource worker, not a CXX executive. A CXX assigns a mission through /hiring and /resource-manager wiring, and output is recorded in .harness/documents/{mission_name}/workers/{name}.md.