software-architecture

Guide software teams through architectural decisions with structured tradeoff analysis.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/edhahn/agent-skills --skill software-architecture-edhahn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: software-architecture
Source: https://github.com/edhahn/agent-skills/tree/main/software-architecture
Command: npx skills add https://github.com/edhahn/agent-skills --skill software-architecture-edhahn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Software architecture and engineering partner for design, code quality, and technical decision-making. Use this skill whenever the user is working on software projects and needs help with: system design or architecture decisions, evaluating technology choices or tradeoffs, code review or refactoring, writing technical specs/ADRs/RFCs, API design, database schema design, infrastructure planning, observability strategy, security architecture, or any discussion about how to structure, build, or evolve a software system. Also trigger when the user says things like "how should I architect this", "what's the right pattern for", "review this code", "I'm choosing between X and Y", "help me write a tech spec", "is this the right approach", or asks about scaling, performance, reliability, or maintainability of a system. Even general coding questions benefit from this skill when the problem involves meaningful design decisions.

Core Features & Use Cases

  • Provide structured architecture guidance and tradeoff analysis for software projects.
  • Assist with system design, technology evaluation, ADRs/RFCs, API design, and infrastructure decisions.
  • Align recommendations with existing patterns, constraints, and team capabilities across multi-project ecosystems.

Quick Start

Describe your project goals and constraints, and ask me to propose a scalable, maintainable software-architecture approach.

Frequently Asked Questions about software-architecture

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

FAQPage Schema
How do I evaluate technology choices and tradeoffs for system design?

Evaluate technology choices by providing structured architecture analysis, explicit tradeoffs, and recommended patterns that align with your existing infrastructure and team capabilities.

What's the best way to write an ADR or technical spec for a new software architecture?

Write an ADR or technical spec by enforcing operating-context awareness, explicit tradeoffs, and adherence to core principles while documenting recommended patterns and infrastructure decisions.

How do I structure API design and database schema decisions across multiple projects?

Structure API design and database schema decisions by aligning recommendations with existing patterns, constraints, and team capabilities across multi-project environments.

Can this help with code review and refactoring for architectural improvements?

Code review and refactoring are supported by providing structured analysis of design decisions, ensuring maintainability, and recommending patterns that fit your operating context.

What's included in infrastructure planning and observability strategy guidance?

Infrastructure planning and observability strategy guidance covers system design, technology evaluation, security architecture, and scaling decisions structured around explicit tradeoffs and core principles.

When do I need formal architecture documentation instead of general coding guidance?

Formal architecture documentation is needed when problems involve meaningful design decisions about scaling, performance, reliability, or maintainability rather than straightforward implementation tasks.