What problem does it solve? Before any code is written, parallel feature implementations tend to invent divergent patterns — different models of the same entity, different error conventions, different answers to failure cases. This Skill converts the user-facing guarantees from an experience baseline into binding system guarantees, so every feature built afterwards follows the same architecture. ## Core Features & Use Cases - Structured architect interview: Walks through seven sections — foundations re-check, stack and boundaries, cross-cutting mechanisms, non-functional budgets, build order, fitness functions, and deliberate deferrals — each recording the divergence it prevents. - Guarantee conversion: Translates experience-baseline promises (e.g., offline capture loses nothing) into concrete system mechanisms, budgets with hedges and sources, and checkable fitness functions. - Gate and ratification workflow: Writes a completeness/checkability/coherence checklist, enforces marker rules ([NEEDS DECISION], [NEEDS LOOKUP], etc.), and manages Draft/Ratified status with a decision register. - Use Case: After product specs, technical constraints, and an experience baseline exist for a project, run this Skill to finalize the architecture document at .specify/memory/architecture.md before the build starts. ## Quick Start Ask the assistant to run the architecture-baseline skill to finalize the project's architecture now that the specifications, constraints, and experience baseline are complete.
