メニュー
Relentlessly interrogate a plan or design one question at a time until the goal, risks, and trade-offs are clear.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Two-axis review of a diff — Standards (does it follow the repo's conventions and avoid code smells?) and Spec (does it implement what the ticket/spec asked?). Runs the axes as parallel sub-agents. Use to review a branch, PR, or work-in-progress.
Implement one ready ticket or spec interactively in the foreground — the attended alternative to the AFK /nightmanager night shift. TDD where seams allow, then code review, then commit.
Investigate a question against high-trust primary sources and capture the findings as a Markdown note in the repo. Dispatches Nightmanager's librarian tool so you keep working while it reads.
Test-driven development reference — what a good test is, where tests go, the anti-patterns, and the rules of the red → green loop. Reference material for /implement and the night shift, not a workflow of its own.
Turn the current conversation into a draft local spec in specs/ using this repository's spec template and Nightmanager conventions. Synthesis, not an interview.
Break a spec, plan, or conversation into vertically-sliced Nightmanager tickets — local TODOs.md entries, each declaring what it delivers and what blocks it.
| name | grill-me |
| description | Relentlessly interrogate a plan or design one question at a time until the goal, risks, and trade-offs are clear. |
Interview the user relentlessly about every aspect of this plan or design until you both reach a shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one at a time. For each question, offer your recommended answer.
Ask exactly one question, then wait for the answer before asking the next. Asking several at once is bewildering and gets shallow answers. Do not batch, and do not move on until the current question is settled.
This skill sharpens the plan; it does not build it. Do not produce specs, TODOs.md entries, documentation, or workflow guidance, and do not start implementing or call /implement, until the user confirms you have reached a shared understanding.
When the plan feels clear, stop and say so, then ask the user to confirm. On confirmation, the natural next step is to-spec (write a draft spec) — not implementation. Nightmanager never implements straight from a grilling session.
