Stats
Actions
Tags
From session-orchestrator
Stress-tests a plan, design, or PRD by interrogating decisions one at a time, grounding each question in the codebase to surface contradictions and assumptions before implementation.
How this command is triggered — by the user, by Claude, or both
Slash command
/session-orchestrator:grill [file-path-or-topic]The summary Claude sees in its command listing — used to decide when to auto-load this command
# Grill Invokes the `grill` skill (`skills/grill/SKILL.md`). Relentlessly interrogates a plan/design/PRD one decision at a time, grounds every question in the codebase, and surfaces contradictions before implementation. Optionally writes `docs/specs/YYYY-MM-DD-<slug>-grill.md`. ## Argument Validation The optional argument is either a file path to grill (a PRD, spec, `STATE.md`) or a topic/slug. If absent, the skill grills the plan already present in the current conversation; if there is none, it asks the user to state it first. Examples: - `/grill` — grills the plan in the current conve...
Invokes the grill skill (skills/grill/SKILL.md). Relentlessly interrogates a plan/design/PRD one decision at a time, grounds every question in the codebase, and surfaces contradictions before implementation. Optionally writes docs/specs/YYYY-MM-DD-<slug>-grill.md.
The optional argument is either a file path to grill (a PRD, spec, STATE.md) or a topic/slug. If absent, the skill grills the plan already present in the current conversation; if there is none, it asks the user to state it first.
Examples:
/grill — grills the plan in the current conversation context/grill docs/prd/2026-06-09-export.md — grills a specific PRD file/grill "partial order cancellation" — grills the named idea, slug pre-setCONTEXT.md, steering docs, ADRs, relevant source), state the target back.AskUserQuestion, applying the Five Tactics (glossary conflict, sharpen fuzzy language, code contradiction, edge-case scenario, assumption audit); read the repo before asking./plan feature, summary only, hand off without a file, or done.Unlike /brainstorm, grill imposes no implementation gate — it is a composable thinking tool. It writes no code and never commits; the only write it performs is the optional summary file in Phase 4. What happens after the grill is the user's call.
| Situation | Use |
|---|---|
| A settled-feeling plan needs stress-testing before build | /grill |
| The design is still ambiguous and needs narrowing | /brainstorm |
| Scope is clear, need a formal PRD + issues | /plan feature |
| Adversarial pass before formalizing | /grill → /plan feature |
skills/grill/SKILL.md — full skill specificationskills/brainstorm/SKILL.md — cooperative sibling for ambiguous designsskills/plan/SKILL.md — primary hand-off target.claude/rules/ask-via-tool.md — AUQ usage convention (AUQ-001..005)npx claudepluginhub kanevry/session-orchestrator --plugin session-orchestrator/grill-meInterrogates the user about a plan or idea, asking one question per turn, exploring decision tree until convergence. Produces a list of decisions ready for /to-prd.
/grillStress-tests a feature spec or plan by walking its decision tree, challenging assumptions, surfacing gaps, and proposing fixes. Supports --auto and --deep flags.
/reviewRuns expert review on a plan, specification, or implementation approach, using provided arguments as review context.
/planOrchestrates full design planning — requirements discovery, gap analysis, and implementation planning — producing a machine-readable artifact for /implement.
/pre-impl-reviewRuns a combined design, architecture, and risk review before implementation. Loads product artifacts and produces a structured review with risk register. Skippable for small no-UI features.
/validateValidates plans, roadmaps, or proposals as ruthless CTO mentor, producing 8-section report with verdict, strengths, flaws, blindspots, and next steps.