What problem does it solve? Specifications written weeks apart drift silently: two specs model the same entity differently, state vocabularies diverge, and nobody owns shared fields. This Skill interviews the technical architect to capture immovable constraints, a shared domain model with per-field ownership, interface contracts, and an authority model before experience design begins. ## Core Features & Use Cases - Constraint capture: Records existing systems, regulatory obligations, platform commitments, team reality, and non-negotiables, each with what it forces. - Shared domain model derivation: Runs three passes over specs (declared entities, undeclared nouns, contested fields) to assign field ownership and flag entities no feature could own as missing specifications. - Authority and contract modeling: Documents disclosure classes per authority type and cross-feature handoffs naming the triggering state. - Living document management: Amends .specify/memory/architecture.md in place on re-runs, preserving stage-5 sections, ratification footers, and prior checklist evaluations. - Use Case: After the first few feature specs exist, run this to produce a versioned architecture baseline that later specs anchor to, then re-run it whenever a new spec introduces an entity, state, or authority. ## Quick Start Ask the assistant to run the architecture-foundations interview against the existing specs to draft the shared domain model and constraints document.
