rebuild-promptlisted

# Rebuild Prompt Turn a rough prompt into a polished one with the right `/skill` invocations embedded per task. Deliver the finished prompt, then stop — the user pastes it back into this same conversation and runs it. Rationale for every rule below lives in README.md § Design notes. Mechanics, exact strings, and templates live in `reference/routing-guide.md`. Do not restate either here — if you're about to explain *why*, it belongs in one of those two files, not a third copy in this one. ## Pipeline ### 0. Grill the premise Run `grilling` on the raw prompt before decomposing anything. If `grilling` is not installed, grill inline instead: ask what the user is actually trying to achieve, what changes if it works, what they've already ruled out, and which assumption would be most expensive to have wrong. Skip only for one mechanical task with an obvious capability, and say in one line that it was skipped and why. When grilling turns up zero real signal — no target, symptom, or file named at all, not even a hint — do not default to a broad speculative search across the whole scope as if a real target were known. Narrow the first task to diagnosis only, and mark the missing target as the `[?]` gap itself rather than picking a plausible-looking one and committing full effort to chasing it. Carry the answer to the last question forward to step 3 — it's what decides which task, if any, escalates past the default effort level. ### 1. Decompose, then classify If the raw prompt