skills.rest
pitabwire
pitabwireCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

software-architecture

Analyze and document software architecture decisions using ADRs.

Updated Feb 26, 2026
Search Tags:#design#architecture#validation#microservices#adr#event-driven
One-click install
npx skills add https://github.com/pitabwire/skills --skill software-architecture-pitabwire
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: software-architecture
Source: https://github.com/pitabwire/skills/tree/main/software-architecture
Command: npx skills add https://github.com/pitabwire/skills --skill software-architecture-pitabwire

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Master software architecture decisions with structured analysis, ADRs, and design reviews to guide scalable systems.

Core Features & Use Cases

  • Review architecture patterns (microservices, event-driven, DDD)
  • Document ADRs and architectural decisions with trade-off analysis
  • Assess scalability, resilience, and pattern compliance across projects

Quick Start

Describe and capture the proposed architecture in an ADR-ready format for immediate review.

Frequently Asked Questions about software-architecture

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

FAQPage Schema
How do I document software architecture decisions for microservices?▼

Document software architecture decisions using Architecture Decision Records to codify trade-offs. This captures context, evaluates maintainability and performance, and ensures decisions remain traceable across microservices projects.

What is the best way to analyze event-driven architecture trade-offs?▼

Analyzing event-driven architecture trade-offs involves applying structured design reviews to assess scalability and resilience. This ensures your event-driven patterns align with requirements and are evaluated for security and performance.

How do I write an ADR for domain-driven design?▼

Writing an ADR for domain-driven design involves documenting architectural decisions with explicit trade-off analysis. This validates that DDD patterns meet requirements and evaluates their impact on system maintainability.

When do I need to validate architecture patterns for scalability?▼

Validate architecture patterns for scalability when adopting complex designs like microservices or event-driven systems. This assesses pattern compliance, ensuring your architecture supports growth while maintaining resilience and performance.

Can I assess pattern compliance across existing software projects?▼

Yes, you can assess pattern compliance across existing projects by applying architectural design reviews. This evaluates whether current implementations align with intended patterns and checks for maintainability and security gaps.

Related Skills

Explore More Software Engineering Skills→
ucirelloucirello
2

stpa-step1-define-purpose

Define STPA analysis purpose by identifying losses, hazards, and constraints.

Community
Intermediate
susantosantosusantosanto

superpowers-writing-plans

Translate approved specs into structured implementation plans with tasks and architecture.

Community
Intermediate
kivo360kivo360
1

moai-lang-typescript

Scaffold full-stack Next.js and TypeScript projects with type-safe API routes.

Community
Advanced
artosetrovartosetrov

guardian

Review SwiftUI code for Hexbound design system compliance and architecture rules.

Community
Advanced