grilllisted

## Activation Contract Use when the user wants a relentless interview for a plan, design, code approach, docs-backed exploration, or SDD planning set. Select exactly one mode: | Trigger shape | Mode | Behavior | | --- | --- | --- | | `grill me`, `grill code`, `entrevistame` | `plain` | Run `grilling` with native question UX. | | `grill with docs`, `grill docs open` | `docs` | Run `grilling` plus `domain-modeling` with native question UX. | | `grill me sdd`, `entrevistame sdd`, SDD planning interview | `sdd` | Interview, then draft OpenSpec `proposal.md`, specs, `design.md`, and `tasks.md`. | ## Hard Rules - Every user-facing question MUST go through the `native-question-ux` skill. Use its fallback if the runtime has no native question tool. - Follow the `grilling` skill in every mode: one question at a time, attach a recommendation, stop and wait, and explore the codebase instead of asking when possible. - Preserve open-ended interview semantics; do not turn the flow into generic code review. - `docs` mode also follows `domain-modeling` to capture terms, decisions, and context as they emerge. - Interview/summaries/gates use the user's language; artifacts default to English unless the user explicitly requests Spanish artifacts. - `sdd` mode is plan-only: read-only codebase access; no code edits, builds, installs, tests, commits, or state-changing commands. The only side effect is writing approved planning `.md` files. - In `sdd` mode, subskills return approved drafts only