pavilio-grill

What problem does it solve? It prevents premature or vague implementation by stress-testing a raw idea or existing plan through a structured interview before any code is written, producing a complete, reviewable design contract. ## Core Features & Use Cases - Grill-forward interview: Asks one question per message with a recommended answer, challenges fuzzy terminology against the project glossary (CONTEXT.md), and cross-references the codebase instead of asking what code can answer. - OpenSpec change artifacts: Writes proposal.md, design.md (with mermaid diagrams), delta specs with WHEN/THEN scenarios, and tasks.md into an openspec/changes/<change-id>/ directory, committed to git. - Inline domain docs: Updates CONTEXT.md glossaries and offers ADRs (only when decisions are hard to reverse, surprising, and real trade-offs) as decisions crystallize. - Use Case: Before building a new billing feature, run the grill to resolve domain terms like Invoice vs Bill, present a design for approval, and end with a committed change dir ready for plan execution. ## Quick Start Invoke /pavilio-grill with your feature idea or draft plan and answer the interview questions until the design is approved and the change artifacts are written.