design-grilllisted

# Design Grill Use this skill to force shared understanding before implementation. The output is a cleaned-up decision summary, not code. Inspired by gstack `office-hours` and Matt Pocock's `grill-me`, `grilling`, `grill-with-docs`, and `domain-modeling` skills. This is a rewrite for this catalog's workflow. ## Hard Gate Do not implement, scaffold, edit production code, run migrations, or perform mutating implementation commands while grilling. This skill produces decisions and documentation only. If the user asks to implement during the session, stop the grill cleanly: finalize `DESIGN-GRILL.md`, report the accepted decisions, and wait for a separate implementation request. ## Start With Repo Truth Before asking anything the repository can answer: 1. Inspect relevant docs, plans, existing `DESIGN-GRILL.md`, `CONTEXT.md`, `CONTEXT-MAP.md`, and ADRs if present. 2. Search the codebase for the named feature, API, workflow, command, page, schema, or error. 3. State assumptions explicitly and name conflicts instead of averaging them. Ask only for product intent, trade-offs, missing constraints, or preferences that are not discoverable from the repo. Use the same language as the user for questions, recommendations, and the final summary. Keep canonical technical terms such as ADR, PRD, API, and `CONTEXT.md` when they are clearer than translation. ## Grilling Loop Ask one question at a time. Every question must include your recommended answer and why. For each answer: