What problem does it solve? Teams often jump from requirements straight into coding, which causes frontend and backend to drift apart with mismatched endpoints and shapes. This Skill turns business requirements into a validated architecture document, a single-source-of-truth API contract, and a dependency-ordered ROADMAP before any code is written. ## Core Features & Use Cases - Architecture Document: Produces a stack-grounded, tech-agnostic architecture with Mermaid diagrams, component slugs, and boundaries, validated by the architecture-validator agent. - API Contract: Generates an OpenAPI contract (or GraphQL SDL / proto equivalent) plus a readable companion, with bidirectional traceability between boundary capabilities and operations. - ROADMAP Generation: Creates a milestone/epic roadmap where frontend epics declare the operationIds they consume and backend epics declare the ones they implement, enforcing dependency order. - Use Case: After finishing requirements discovery for a web app, invoke this Skill to produce architecture.md, api-contract.openapi.yaml, and ROADMAP.md, each gated by validator approval before the build phase begins. ## Quick Start Ask the assistant to design the architecture and generate the roadmap from the existing business requirements document.