What problem does it solve? Design decisions often get buried inside PRDs or scattered across conversations, leaving no durable source of truth for system boundaries and contracts. This Skill guides the creation of first-class architecture documents that capture system shape, constraints, and tradeoffs so downstream PRDs can reference them instead of re-explaining the design. ## Core Features & Use Cases - Structured Architecture Doc Workflow: Walks through scoping, reviewing existing docs, choosing a canonical path under docs/architecture/, and drafting section by section using a proven template. - Architecture vs PRD Separation: Enforces a clear distinction between design docs (boundaries, contracts, tradeoffs) and PRDs (product intent, scope, milestones), with guidance on when to use each. - Downstream Linking and Handoff: Identifies PRDs that should reference the new doc and offers next-step options to create a PRD or commit the doc directly to main. - Use Case: A team is redesigning a runtime adjudication boundary. Use this Skill to produce docs/architecture/support-runtime-adjudication.md capturing the chosen design, rejected alternatives, and migration plan, then hand off implementation to a PRD. ## Quick Start Ask the assistant to create an architecture doc for your proposed system design, describing the boundary or contract that is changing.
