software-solution-architecture
Installation
SKILL.md
Software Solution Architecture
Use this skill when the question starts from a business workflow, operating model, system landscape, or transition problem rather than from a single service or deployable boundary.
This skill chooses the solution shape first. It does not default to runtime patterns such as modular monolith vs microservices, CQRS, service mesh, or MCP/A2A until the business flow, participating systems, and transition shape are already clear.
Use ../software-architecture-design/SKILL.md after the solution shape is known and the next question is service decomposition, distributed consistency, platform engineering, or runtime topology.
Quick Reference
| Need | Default move | Read next |
|---|---|---|
| Design a target solution across multiple systems | Map business flow to systems, responsibilities, and constraints before choosing patterns | references/solution-workflow.md |
| Compare integration styles and boundaries | Choose API, event, batch, file, webhook, BFF, or anti-corruption boundaries from a decision matrix | references/integration-and-boundary-patterns.md |
| Map capabilities, owners, and systems of record | Capture business capability, owning team, boundary type, and source-of-truth decisions | assets/planning/capability-boundary-map.md |
| Plan a phased migration | Define current, interim, and target states with coexistence, cutover, and rollback rules | references/transition-architecture.md |
| Sequence delivery into safe waves | Capture migration wave entry, rollback, and retirement criteria | assets/planning/transition-wave-planner.md |
| Package the final recommendation | Summarize target state, options, transition, risks, and handoffs | assets/planning/solution-blueprint.md |