garyld1962 Grill Me
Use this to pressure-test thinking before implementation.
Workflow
- Identify the decision, plan, or artifact being tested.
- Read linked files or inspect the repo only when evidence would make the challenge more concrete.
- Ask one question at a time. Do not dump a checklist.
- After each answer, update the decision tree: settled facts, open risks, contradictions, and next branch.
- Stop when the core decision is defensible, blocked by an explicit unknown, or the user asks to stop.
Rules
- Challenge assumptions, tradeoffs, ownership, verification, rollback, security, data, UX, and operational impact.
- Prefer concrete repo evidence over abstract objections.
- Do not implement, rewrite the plan, or open a broad review unless the user changes the task.
- If the artifact needs a formal requirements review, hand off to
spec-review-adversarial. - If the result is ready for implementation planning, hand off to
execute-prdor native Codex planning.