From temper
Adversarial Q&A loop that stress-tests plans and designs by extracting claims, generating challenge questions, and presenting one at a time. Use before finalizing architecture or implementation plans.
How this skill is triggered — by the user, by Claude, or both
Slash command
/temper:grill-meThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Interview the user relentlessly about a plan or design until reaching shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one.
Interview the user relentlessly about a plan or design until reaching shared understanding. Walk down each branch of the decision tree, resolving dependencies between decisions one-by-one.
This is NOT the walkthrough. The walkthrough explains the plan. Grill Me challenges it.
| Property | Walkthrough | Grill Me |
|---|---|---|
| Purpose | Explain the plan to the user | Challenge the plan's assumptions |
| Direction | Temper → User (teaching) | Temper ↔ User (adversarial) |
| Questions | "Does this make sense?" | "What happens if X fails?" |
| Outcome | User understands plan | User discovers weaknesses |
| Mode | Sequential section presentation | One hard question at a time |
Read the plan/design document. Extract:
For each extracted item, generate challenge questions targeting:
| Target | Question Pattern |
|---|---|
| Unstated assumptions | "What happens if {assumption} is false?" |
| Missing error paths | "What does {component} do when {dependency} fails?" |
| Alternatives not considered | "Why {this approach} instead of {alternative}?" |
| Scalability limits | "What happens at 10x/100x current {metric}?" |
| Dependency risks | "If {dependency} changes/breaks, what's the impact?" |
| Edge cases | "What about {edge case}?" |
| Hidden complexity | "What's the hardest part of implementing {this}?" |
| Success criteria gaps | "How would you verify {claim} actually works?" |
| Cross-cutting concerns | "How does this interact with {existing system}?" |
| Rollback | "If this fails in production, how do you roll back?" |
CRITICAL: Never ask multiple questions. One question, wait for response.
AskUserQuestion:
question: "{challenge question}"
options:
- label: "Answer"
description: "Provide your answer or reasoning."
- label: "Update plan"
description: "I want to revise the plan based on this question."
- label: "Skip"
description: "Skip this question, move to next."
- label: "Done grilling"
description: "End the session and return to the gate."
multiSelect: false
After each answer:
Continue until:
After the loop ends:
GRILL ME — Summary
Questions asked: {N}
Weaknesses found: {N}
Plan updates made: {N}
Weaknesses:
1. {description} — {how it was addressed}
2. {description} — {still open}
Plan updated: Yes/No
Returning to {stage} gate...
This skill is invoked from the Plan and Design stage gates in the /temper unified command. When the user selects "Grill Me" at a gate, the orchestrator invokes this skill with the current plan.md or design.md as input.
After the grill session ends, the user returns to the original stage gate (Plan or Design). If the plan was updated during grilling, the gate shows the updated summary.
npx claudepluginhub galando/temper --plugin temperConducts relentless Socratic interviews to stress-test plans, designs, or ideas by walking every decision branch and resolving one-by-one. Triggers only on explicit 'grill me' or 'me grille'.
Interviews you relentlessly about a plan or design using Socratic questioning. Uncovers hidden assumptions, edge cases, and feasibility gaps before implementation.
Socratic interviewer that stress-tests plans, designs, and ideas by surfacing hidden assumptions and unresolved dependencies until shared understanding is reached.