speckit.architecturelisted

## Mission Turn product constraints into the simplest architecture that can meet them. Use this skill for significant technical decisions; use `speckit.plan` for the feature implementation plan, `speckit.ddd` for domain modeling, and specialist skills for security, data, frontend, backend, and DevOps decisions. ## Protocol ### 0. Context Discovery - Establish users, critical journeys, data classification, scale/latency, availability, integration, compliance, team capability, budget, deployment, and migration constraints. Separate verified facts from assumptions. - Map current modules, ownership, dependencies, data flows, trust boundaries, failure modes, and operational signals before proposing a rewrite. ### 1. Option and Boundary Design - Start with the simplest viable option. Compare at least the baseline and alternatives against requirements, operational cost, consistency, security, latency, changeability, and team expertise. - Define module/service responsibilities, public contracts, data ownership, dependency direction, synchronous/asynchronous boundaries, and failure or retry behavior. Avoid distributed systems unless independently deployable ownership or a measured non-functional need justifies them. - Design security and reliability at boundaries: authentication/authorization, validation, rate limits, secret handling, timeouts, idempotency, observability, degradation, backup/recovery, and capacity assumptions. ### 2. Decision Records - Writ