grill-me
Pressure-test an existing plan or design artifact until it is coherent enough for the next workflow step or plainly blocked. Use when the user wants to be grilled on a plan, design doc, PRD, ADR, rollout plan, migration runbook, rolling-wave project shape, or slice contract; when they say "grill me"; or when Codex should interrogate a source-of-truth artifact, inspect code and adjacent docs before asking, auto-answer evidence-backed questions, ask only about conflicts or low-confidence recommendations, edit the original file in place, preserve the artifact's existing format, and keep conclusions, blockers, readiness, and deferred work synchronized in the document.
rijkvanzanten · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add rijkvanzanten/rolling-wave-engineering --skill grill-me技能说明
name: grill-me description: Pressure-test an existing plan or design artifact until it is coherent enough for the next workflow step or plainly blocked. Use when the user wants to be grilled on a plan, design doc, PRD, ADR, rollout plan, migration runbook, rolling-wave project shape, or slice contract; when they say "grill me"; or when Codex should interrogate a source-of-truth artifact, inspect code and adjacent docs before asking, auto-answer evidence-backed questions, ask only about conflicts or low-confidence recommendations, edit the original file in place, preserve the artifact's existing format, and keep conclusions, blockers, readiness, and deferred work synchronized in the document.
Grill Me
Pressure-test one source-of-truth artifact until it is coherent enough to proceed or plainly blocked. Edit the artifact directly. Do not keep critical state only in chat.
Required Workflow
- Select one source-of-truth file.
- Use the file the user names.
- If the user does not name a file and there is exactly one credible candidate, state that selection and proceed.
- If multiple plausible files exist, force explicit selection before editing.
- Prefer repairing the existing artifact. Create a new artifact only when no usable source exists or the format is unsafe to edit directly.
- Inspect before asking.
- Read the artifact first.
- Read relevant code, docs, tests, configs, or adjacent plans aggressively whenever they can answer a question from evidence instead of user memory.
- Resolve anything you can from disk before asking the user.
- Classify the artifact scope before grilling:
project-shape:docs/rolling-wave/{project}/project.mdor an artifact with finish line, success criteria, scope, and roadmap.slice-contract:docs/rolling-wave/{project}/slices/NNN-slug.mdor an artifact with original slice contract, acceptance criteria, and implementation notes.other-plan: any other source-of-truth plan.
- Keep the interrogation depth matched to that scope.
Project-Shape Scope
When grilling a rolling-wave project.md or other project-shape artifact, focus on global shape:
- finish line
- success criteria
- scope and non-goals
- constraints and assumptions
- roadmap order
- slice granularity
- dependency flow between slices
- whether broad slices should split into separate review decisions or become child rolling-wave projects
- cross-slice risks, decisions, and open questions
Do not grill deep future slices for behavior, file choices, implementation approach, exact tests, edge cases, or detailed acceptance criteria unless that detail changes the global finish line, scope, roadmap order, dependency structure, or reviewability of the slice map. Future slice details belong to prepare-next-slice when that slice becomes current.
For project-shape artifacts, a slice is good enough when it is a concrete implementation step fitting one bounded human review decision. Multiple independently useful, executable, or revertible chunks may stay together when one intent or transformation recipe, risk class, and verification strategy cover them. Mechanical batches may cross domains. Split separate approval decisions, unrelated mental models, distinct risk classes, or materially different verification strategies. It does not need a full slice contract yet.
For project-shape artifacts, stop once the global finish line, scope, roadmap order, and next slice are clear enough for prepare-next-slice. Do not keep grilling just because future slices still have implementation uncertainty.
Slice-Contract Scope
When grilling a slice contract, grill slice-level behavior, verification intent, expected intermediate state, minimum implementation, execution fit, risks, and scope boundaries until the slice is ready to implement.
Prepare-Review Mode
Use this bounded mode only when prepare-next-slice explicitly requests prepare-review.
- Apply the preparation readiness bar, not the full generic grill checklist.
- Read the slice, parent project, direct dependencies, and supplied neutral evidence index first.
- Check behavior and scope, dependency order, user-facing or irreversible decisions, review coherence, safe deferrals, and one credible failure mode.
- Validate representative high-risk claims. Do not recreate exhaustive consumer, import, generated-registration, or dependency inventories unless implementation requires an exact finite list.
- Use a soft budget of about three minutes and twelve repository queries. Batch searches. When the budget is exhausted, return the highest-leverage
question,blocked, orredirectinstead of continuing broad exploration. - Return
redirectonly when a prerequisite or replacement slice is required for an honest contract. Draft that slice, update material roadmap/dependency state, keep itpending, and include a neutral evidence index. - Stop as soon as required branches are resolved or safely deferred. Optional polish and final completeness proof do not block readiness.
- Preserve the artifact's native format while making it usable as a source of truth.
- Do not rewrite the artifact into this skill's preferred template.
- Keep the document's existing section names, ordering, style, and level of formality unless that structure is actively hiding contradictions or unresolved decisions.
- Add missing tracking information where it naturally belongs in the current format: readiness, blockers, open questions, assumptions, dependencies, deferred work, or explicit out-of-scope items.
- If the artifact already has equivalents for those concepts, update those existing sections instead of creating new standardized sections.
- Add a new section only when there is no reasonable place for the information and the missing state would otherwise live only in chat.
- Reorganize only the smallest necessary part when the current structure hides dependencies, duplicates one decision across sections, or makes the plan impossible to veri