Tk Grill

Decision Grilling

Start only through an explicit /tk-grill, $tk-grill, or host skill selection. Do not invoke automatically when the user asks for a quick opinion, ordinary brainstorming, repository explanation, or implementation planning.

Boundary

Own the interview from a rough idea, decision, or plan through confirmed shared understanding. Keep all state in the current conversation.

Do not create or modify source, tests, config, Git state, tickets, Seed, SDD, domain artifacts, scratch files, ledgers, or task graphs. Do not invoke another skill or begin implementation automatically. After synthesis, offer only relevant optional routes:

• tk-prep when the result has become an implementation request or ticket;
• tk-domain when the user wants repository-native vocabulary or a durable decision;
• stop when no further action is needed.

Decision tree and frontier

Map the subject as a decision tree. A branch may become answerable only after its prerequisites are settled. The current frontier is every unresolved decision that can be answered now without guessing at another unresolved answer.

Work in rounds:

1. Separate established facts, unresolved assumptions, and user-owned decisions.
2. Resolve safely researchable facts from the conversation, supplied files, repository, connected tools, or bounded public sources. Do not ask the user for a fact that available evidence can answer.
3. Ask the whole current frontier in one round. Group only independent questions; never impose a fixed question count or round size.
4. Defer a question when its answer depends on an unresolved prerequisite. An unresolved research fact blocks only its dependent branch, not the rest of the frontier.
5. After the user answers, update the tree, identify contradictions or newly exposed assumptions, recompute the frontier, and continue.

Do not turn fact-finding into unbounded research. Investigate only facts that can materially change the current decision tree.

Question contract

Goals, priorities, trade-off preferences, scope, meaning, tone, and accepted risk belong to the user. Never silently choose one. When a useful recommendation is possible, include the recommendation and its reason instead of presenting neutral options and delegating all judgment.

Keep each round scannable in the user's language:

❓ **Q1 · <short title>**: <question and relevant choices>

➡️ <recommended answer and why>

---

❓ **Q2 · <short title>**: <independent frontier question>

➡️ <recommended answer and why>

Do not ask downstream questions merely to appear thorough. Relentless means leaving no silent decision branch, not maximizing question volume.

Completion

When the frontier appears empty:

1. Check the whole tree for an unvisited branch, hidden assumption, contradiction, or intentionally open risk.
2. Summarize the current understanding briefly and ask the user to confirm that it is shared and complete.
3. Do not act on the result before confirmation. If the user corrects it, update the tree and continue from the new frontier.
4. After confirmation, return a compact synthesis of the purpose or conclusion, key decisions and reasons, intentionally open assumptions or risks, and optional next routes. Do not create an artifact unless a separately selected owner later does so.

Source

Adapted the decision-tree, prerequisite-aware frontier, whole-frontier rounds, fact-versus-decision ownership, recommendations, and shared-understanding gate from mattpocock/skills skills/productivity/grilling at commit 6654f6b60cd9d5be8b54c6fafe44346dabeb3b76.

TigerKit removes mandatory subagent runtime assumptions, wrappers such as grill-me and grill-with-docs, automatic implementation transition, and persistent state. The original copyright and MIT notice are in repository NOTICE.md.