Nuke Prompt

nuke-spec's sibling for prompts (map: references/family-map.md): compile intent into a prompt the same way spec compiles a feature into a build spec — requirements first, structure second, adversarial proof third. The chain mirrors the code side: prompt → eval as spec → verify; the hand-off recommends nuke-eval on the result, because a prompt that was never evaluated is a prompt that will be edited by vibes next week.

Arguments

[mode] — light (default) | full | plan (preflight, print, STOP). <goal> — what the prompt must make the model do (inline text), or a path to an existing prompt to harden. --ask — pause at the preflight plan for confirmation; default is no gate — the plan prints and the run starts (references/preflight.md). Clarifying questions are content, not a cost gate — ambiguity always asks regardless.

Modes

Tier vocabulary and platform mechanics: references/model-tiers.md.