Grill — the alignment gate
Before any work starts: draft an approach, attack it, then ask you.
This is the cheapest correction in the whole loop. A plan is a paragraph; the work is an afternoon. Finding the missing file, the unhandled case or the absent test while it is still a paragraph costs a few seconds of model time. Finding it after the work is done costs the work.
What it does
- Asks what you want planned. Nothing runs until you have said.
- Drafts an approach — concrete: which files, in what order, and the one test that would prove it worked.
- Grills the draft. A second pass whose only job is to find what the plan fails to name. It did not write the plan and does not defend it.
- Checks the grill itself. A critique that objects in general terms is not usable — it cannot be acted on and cannot be argued with. This check runs on a fresh context that has seen neither the plan-writer nor the critic, and blocks if the grill did not quote what it was attacking.
- Asks you before anything proceeds.
Why the grill is a separate step
Every serious result on AI self-review says the same thing: a model reviewing its own work is far too easy on itself. The critique has to come from a call that did not produce the thing being criticised, or it is agreement in a different font.
That holds here by construction. Each step in a Vodou graph is a stateless one-shot call — the grill receives the plan's text, not the plan-writer's conversation. It has the artifact and no attachment to it.
Using it
Say any trigger phrase, or run it from its Skill Console tab. Answer the first question with what you want planned — a feature, a migration, a decision, a piece of writing. It is not specific to code.
To skip the gate on work you have already thought through, just do the work. The point of this skill is the moments when you have not.