← ClaudeAtlas

workflow-grilllisted

Grill-me interrogation mode: relentlessly walk the decision tree one question at a time, interrogate requirements, self-answer from the codebase, exit on shared understanding or proceed — hands a Resolved-decisions block to the command's artifact step. Activated by /capture /design /implement /architect /extend /debug. Not a from-scratch design flow; produces no design doc.
lugassawan/swe-workbench · ★ 2 · AI & Automation · score 71
Install: claude install-skill lugassawan/swe-workbench
# workflow-grill — Relentless Interrogation Mode ## What this mode is `workflow-grill` runs in the **orchestrator** (main conversation thread), inside a command's clarify step, **before** any subagent is delegated to. It is not a standalone workflow — it is a mode gate activated by the interrogation prelude in the six interactive commands. It produces one output: a `## Resolved decisions` block that the command threads into its normal artifact/delegation step (the same way a ticket-context summary is prepended). Because `AskUserQuestion` is a main-thread tool, this entire loop must stay in the orchestrator. Never embed it in a shared subagent — it would leak the mode gate into flows that don't use it (e.g. `product-manager` is shared with `/report-issue`; `senior-engineer` is consulted by `/implement`). ## Procedure ### Step 1 — Build the decision tree From `$ARGUMENTS` and any prepended ticket-context summary, enumerate the decisions that must be resolved before the artifact step can produce a correct result. A decision belongs on the tree if: - getting it wrong would require rework of the artifact, **or** - it implies a constraint the subagent needs to know (scope, persona, tech stack, tone, reversibility). Order decisions by dependency: decisions whose answers unblock others come first. Two-way-door decisions (easily reversed, low blast radius) go last and may be deferred. ### Step 2 — Walk the tree, one decision at a time For each decision in dependency order: