Grill Me

Grill Me

Must read: ../pack-shared/standards.md — Read /taste and /architecture doctrines this turn before recommending answers. Do not skip.

Execution context: ../pack-shared/execution-context.md · Ask style: ../pack-shared/asking.md · Plain language: ../pack-shared/plain-language.md

/grill-me discovers product, behavioral, taste, and architecture decisions without automatic logs or hidden artifacts. Keep locked decisions and applicable Active Rules visible in the execution context. Save a durable record only when the user requests it and approves its destination.

Read: doctrine.md.

Process

1. Establish or refresh a compact in-chat execution context from the ask and rediscovered repository, ticket, PR, or diff facts. If a parent already supplied an outcome, current slice, non-goals, lane, and ticket/PR, reuse that brief. Re-announce only facts or user decisions that changed or were missing.

2. Batch every unsettled topic from the doctrine's behavior sweep. Include plan count and file lane so the first batch is complete.

3. Apply /taste and /architecture before recommending answers:

   When	Include in the batch
   Always	/taste Cite keys (taste:keep-it-simple and Named principles)
   Always	/architecture Cite keys: who owns this job, public entry, reuse versus a new one-job helper, folders, write path, who may act on that write, and whether to move old code. For a typo or pure rename, recommend “keep the existing structure.”

4. Send a Questions-only batch for every real open decision (no Locked heading in that message). Wait for the reply.

5. Put answers, Active Rules, corrections, and revised lanes directly in the execution context. If a correction exposes a new material unknown, send a new Questions-only batch.

6. When material Questions are settled, announce Locked in (tell me if this is wrong) for non-goals, split, and shared understanding in a separate announce-only message. Do not issue plans until that Locked closure stands and every relevant Active Rule has an enforcement and verification owner.

Do not create automatic files for language, choices, rules, or progress. If the user wants a durable artifact, ask for or honor an approved destination under the shared optional-persistence rule.

If a parent already owns the next step

Hand the inline context back to /task for planning. Do not stop to wait for the user to pick a next skill.

If this is a user one-off

Stop after shared understanding unless the user explicitly asks for the next step. /task receives the inline context; /write-ticket may receive the relevant memo and decisions.

• Structure needed → /architecture, then /task.
• Ready to build → /task.

Anti-patterns

• Giving workers a hidden path instead of the parent context
• Writing plans before Locked closure
• Treating a user decision as recoverable from code alone
• Creating automatic artifacts to hold language, choices, rules, or progress