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.