What problem does it solve? After brainstorming confirms requirements, teams often jump into implementation without a coherent multi-stage design, leading to inconsistent terminology, missing architecture decisions, and transitional compatibility hacks. This Skill enforces a structured design phase that confronts every stage's responsibilities, interfaces, and data flows before any planning or coding begins. ## Core Features & Use Cases - Stage-by-stage design confrontation: Reads the brainstorming index and iterates through every stage, confirming terminology, responsibilities, interfaces, data flow, error handling, and test strategy one question at a time. - Living documentation: Incrementally writes per-stage design files under docs/grill/, updates CONTEXT.md glossaries, and creates ADRs only for hard-to-reverse decisions with real trade-offs. - Final-state-first discipline: Explicitly forbids transitional compatibility mechanisms (adapters, dual reads/writes, feature flags) unless the final requirement demands them, while still requiring data safety and release-operation assessment. - Use Case: After brainstorming a multi-stage migration of an ordering system, use this Skill to produce confirmed design documents for each stage, an updated domain glossary, and ADRs before handing everything to a writing-plans workflow. ## Quick Start Use the grill-with-docs skill to design all stages from the brainstorming index at docs/brainstorming/2024-01-15-user-auth.md before planning implementation.
