grill-code
Installation
SKILL.md
Activation Contract
Use this wrapper when the user wants the grill-me flow presented through the active runtime's native question UX when that mechanism is explicitly available in the current session.
Hard Rules
- Load and follow
grill-me; this wrapper only changes question presentation. - Use a runtime's native question UX only when that mechanism is explicitly available in the current runtime/session.
- Native question branch: use the explicitly available mechanism that preserves the delegated question semantics; for opencode, the named example is the
questiontool when available. - Never invent or assume a tool, prompt primitive, or UI capability that is not explicitly available.
- Preserve
grill-mesemantics: ask one question at a time, keep open-ended questions open-ended, and stop/wait after each answer. - When the native mechanism presents selectable options, put the delegated
grill-merecommendation first/recommended; if the runtime already provides a built-in custom/freeform answer field, rely on that native field instead of adding a separate selectable custom/chat option; in opencode, rely on the built-inType your own answerpath. - If the native mechanism only supports bounded choices and has no custom/freeform answer field, do not force open-ended grilling questions into options; ask in normal chat instead.
- If no suitable native mechanism is explicitly available, ask in normal chat.
- Ask one question at a time, then stop and wait for the user's answer.
- Keep all other behavior aligned with
grill-meand any delegated skills it uses.