What problem does it solve?
This Skill eliminates the risk of over-engineered, poorly bounded, or hard-to-maintain software systems by providing pragmatic architecture guidance aligned to actual business and technical constraints, rather than theoretical best practices.
Core Features & Use Cases
- Cross-System Design & Boundary Definition: Define clear service, module, and data ownership boundaries that align to team capabilities, failure modes, and deployment needs.
- Explicit Tradeoff Analysis: Evaluate competing design options transparently, recommending the simplest viable solution with clear reasoning for rejected alternatives.
- Migration & Modernization Planning: Create incremental, low-risk migration paths for monolith decomposition, system replacements, and tech upgrades with built-in rollback and validation.
- Use Case: For example, if your team is splitting a monolithic e-commerce backend into separate order, inventory, and payment services, this Skill will help you define clear data ownership for each service, design API contracts between them, plan a strangler migration to avoid downtime, and produce an ADR documenting the decision and tradeoffs.
Quick Start
Use the software-architect skill to evaluate whether our current user authentication service should be split into separate identity and session management services, and produce an ADR with the recommended approach and tradeoffs.
