# Problem Grill

> Use when a product or feature idea needs pressure-testing against problem, user, pain, success, and timing.

- Skill: `rohitg00/problem-grill` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rohitg00/problem-grill`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rohitg00/problem-grill/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: rohitg00 (https://skillmd.com/u/rohitg00)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rohitg00/problem-grill

---


# problem-grill

Lifecycle stage: CHALLENGE

## Trigger

Use before accepting that a product or feature should exist.

## When not to use
Do not use when this trigger is absent; choose the command or skill that owns the requested state, artifact, and verification gate.

## Inputs

- User request or current artifact.
- Known constraints and context.
- Relevant evidence or source links, if available.
- Current Agent Brain state.

## Procedure

1. State the current state and target artifact.
2. Identify missing blockers and ask at most three blocking questions.
3. Separate facts, assumptions, hypotheses, and open questions.
4. Apply the anti-rationalization table below.
5. Produce the required artifact: **Problem Grill Report**.
6. Add evidence, risks, decision, and next state.

## Anti-Rationalization

| Shortcut | Rebuttal |
|---|---|
| "This is obvious." | Write the assumption and evidence. If you cannot, it is not obvious. |
| "We can do this later." | If the missing step changes the decision, do it now or state the risk. |
| "The user wants speed." | Reduce scope; do not skip the quality bar. |
| "This does not need verification." | Every important claim or behavior needs proof. |

## Verification

- Required artifact exists and is named.
- Facts, assumptions, and open questions are separated.
- Evidence or evidence gaps are explicit.
- Next state is stated.
- Stop conditions are honored.

## Output Artifact

Problem Grill Report

Use `templates/grill-report.md` for a concise, auditable artifact with evidence, blockers, and next action so another agent can resume.

## Failure Modes

- Producing advice instead of an artifact.
- Accepting user assumptions without challenge.
- Skipping evidence because the task feels simple.
- Recommending an agent when a simpler system is enough.
- Hiding risks or open questions.

## Example

Trigger: a product request over-assumes the problem or automation need. Action: challenge user, pain, frequency, alternatives, evidence, and safety before approving build work. Output artifact: `templates/grill-report.md` with blockers and next action. Verification: cite known facts, assumptions, missing evidence, and non-agent alternatives reviewed.

A request says, "Automate every repo maintenance task." The skill should challenge whether automation is needed, list manual or checklist alternatives, surface privacy and side-effect risks, and produce a problem grill report before approving any build plan.