pmos-architecture-designer

What problem does it solve?

It prevents expensive, unclear, or implicit architecture choices by forcing architecture prerequisites and boundary decisions to be made before implementation begins.

Core Features & Use Cases

• Architecture decision scoping: Clarifies what is being decided, what is costly to change later, and which dependencies are external or cross-module.
• Boundary and ownership design: Makes responsibility ownership, data ownership, and API/event/contract seams explicit, including platform vs subproject placement.
• ADR-ready tradeoff and readiness: Compares alternatives, records tradeoffs (complexity, operational cost, migration cost, testability, rollback difficulty), and produces an architecture-ready conclusion before builder execution.

Quick Start

Use this skill when you are about to start coding and need to define boundaries, integration seams, and the irreversible technical choices in a way that an implementation handoff can proceed.