Menú
Use when a product or feature idea needs pressure-testing against problem, user, pain, success, and timing.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Agent Brain /brain-brief: after intake, research, and grill have enough signal.
Agent Brain /brain-build: an implementation plan has a selected task and validation method.
Agent Brain /brain-design: a product brief needs ux or interaction design before planning.
Agent Brain /brain-eval: changing Agent Brain behavior or checking quality.
Agent Brain /brain-grill: the idea, brief, design, or plan has unresolved assumptions.
Agent Brain /brain-learn: after repeated success/failure, a tricky fix, or a shipped workflow.
| name | problem-grill |
| description | Use when a product or feature idea needs pressure-testing against problem, user, pain, success, and timing. |
Lifecycle stage: CHALLENGE
Use before accepting that a product or feature should exist.
Do not use when this trigger is absent; choose the command or skill that owns the requested state, artifact, and verification gate.
| 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. |
Problem Grill Report
Use templates/grill-report.md for a concise, auditable artifact with evidence, blockers, and next action so another agent can resume.
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.
