domain-decomposition-api-design-advisor

Domain Decomposition API Design Advisor

Source mapping: Tier 3 specialized skill derived from Kotlin_Spring_Developer_Pipeline.md (SK-25).

Mission

Convert vague product intent into explicit technical boundaries and contracts that can survive implementation and change. Optimize for clear ownership, explicit invariants, and low coupling rather than premature microservice enthusiasm.

Inputs To Gather

• Business goals, user journeys, and success criteria.
• Known constraints: SLA, throughput, latency, audit, privacy, compliance, data retention.
• Existing system boundaries, shared data, and integration points.
• Failure and retry expectations, especially around money, inventory, identity, and messaging.
• Team topology and deployment constraints when they influence boundary choices.

Decomposition Workflow

1. Break the feature into use cases and state transitions.
2. Identify the core nouns, aggregates, and decision points.
3. Identify where consistency must be strong and where eventual consistency is acceptable.
4. Separate commands from queries when that improves clarity, not by default.
5. Identify external actors and dependencies.