01
Interrogate a vague proposal
Identify the goal, users, scope, constraints, success measures, dependencies, risks, ownership, and assumptions that need answers.
requirements interrogation
CategoryBusiness & Productivity
Codex Grill Me Skill
Codex Grill Me Skill turns a vague idea into a decision-ready plan by asking focused questions, challenging unclear answers, tracing dependencies, and exposing assumptions before implementation begins. Download the skill for product ideas, architecture, workflows, specifications, and decisions that are still too loose to build safely.
RequirementsDecision treesPlan reviewAssumption testing
01
02
03
04
05
06
07
08
09
02
03
04
05
06
07
08
09
task: complete requirements interrogation task
inspect:
- requirements and context
- existing standards
- failure and edge cases
verify: outputs + checks + handoffWhy a specialist workflow matters
Starting implementation too early makes hidden decisions look like technical details and pushes expensive clarification into the middle of the work.
A good grilling session is not a long questionnaire. It follows the answer, opens one important decision branch at a time, and stops when the plan contains enough evidence to act.
This skill helps Codex inspect available context first, ask precise questions, recommend a default when useful, challenge contradictions, and maintain a visible record of decisions and unresolved risks.
What the downloadable skills can do
What Codex Grill Me Skill can help accomplish
02
Follow decision dependencies
Ask one consequential question at a time, use each answer to choose the next branch, and avoid questions already resolved by available context.
03
Challenge weak reasoning
Point out contradictions, unsupported claims, missing failure behavior, premature solutions, and tradeoffs being treated as free.
04
Produce an actionable brief
Summarize decisions, rationale, requirements, exclusions, open questions, acceptance checks, and the next useful step.
A repeatable working process
How the requirements interrogation workflow moves from request to verified result
The steps keep context, implementation, and verification visible so the result can be reviewed and repeated.
workflow.statusREADY
Context → Plan → Work → Verify
01
Inspect before asking
Read the supplied plan, repository, notes, constraints, and prior decisions so the interview does not waste the user's time.
02
Find the highest-impact uncertainty
Choose the question whose answer changes the most downstream decisions and explain why it matters.
03
Press until the branch is clear
Ask follow-ups when an answer is vague, test edge cases and consequences, and record the decision before moving on.
04
Close with a decision record
Return a concise plan with agreed requirements, rationale, risks, exclusions, unresolved questions, and readiness status.
Useful across real projects
Where Codex Grill Me Skill fit
The workflow adjusts to the project, audience, tools, and risk while preserving the same quality standard.
Product planning
Clarify users, jobs, scope, business rules, permissions, states, metrics, rollout, support, and failure behavior.
Architecture decisions
Examine load, data, trust boundaries, integrations, operations, migration, cost, recovery, and alternative designs.
Workflow design
Define triggers, actors, inputs, handoffs, exceptions, approvals, outputs, ownership, and measurements.
Specifications
Turn a loose request into behaviors, constraints, interfaces, edge cases, testable outcomes, and non-goals.
Common requests
Tasks these skill can handle
Start with one defined outcome and provide the source material, constraints, and checks that matter.
01Interrogate a product idea
02Review an architecture plan
03Clarify feature requirements
04Challenge a proposed workflow
05Find hidden assumptions
06Define acceptance criteria
07Prepare a decision record
08Decide whether a plan is ready to build
Who benefits most
Who Is This For?
These skill is designed for people who need dependable requirements interrogation work with a visible process.
Founders and product managers
Pressure-test ideas and turn incomplete intent into a plan a team can evaluate.
Engineers and architects
Expose missing technical decisions, operational risks, and unstated constraints before implementation.
Designers and researchers
Clarify users, scenarios, evidence, states, accessibility needs, and learning goals.
Teams preparing handoffs
Create a shared decision record that reduces interpretation between planning and execution.
Good to know:
The skill can challenge and organize a plan, but it cannot supply business authority, user evidence, legal judgment, or stakeholder decisions that have not been provided.
Set up the workflow
Installation Guide
Install the complete skill folder and add the project-specific context before beginning.
Download and extract the Grill Me skill
Keep SKILL.md with interview rules, decision tracking, challenge patterns, stopping conditions, and output format.
Choose personal or project scope
Use project scope when the interview should inspect repository context, or personal scope for reusable planning sessions.
Provide the starting material
Add the idea, plan, notes, constraints, known decisions, research, technical context, and intended audience.
Choose the interview depth
State whether you want a short critical pass or a full decision-tree interview before receiving the final brief.
Before you download
Frequently Asked Questions
Practical answers about capabilities, limits, setup, and review.
Will the skill ask many questions at once?+
No. It prioritizes one consequential branch at a time so each answer can shape the next question.
Does Grill Me write the implementation?+
Its primary job is clarification. Implementation should begin only after the resulting plan is sufficiently complete and you explicitly request it.
Can it inspect a repository first?+
Yes. When repository context is available, it should check what is already decided before asking questions.
Will it disagree with me?+
It will challenge contradictions, vague claims, missing evidence, and unpriced tradeoffs while keeping the discussion focused on the decision.
When does the interview stop?+
It stops when critical branches are resolved, remaining uncertainty is visible, acceptance checks exist, and the next step is clear.
Make the work repeatable
Give Codex a questioning workflow that replaces silent assumptions with explicit decisions before expensive work begins.
Clear context. Purposeful work. Relevant checks. A result others can understand.