Nuke Implement

The missing rung between nuke-code and the spec pipeline. Family positioning: code is how the session implements with its own hands · implement is how it delegates implementation to subagents · fix executes an existing spec · verify repairs work someone else already did. Use it when the task is clear enough to state but you want cheap workers typing while the session orchestrates — the cheap-implementer profile as a one-command skill, no spec required.

Core principle, unchanged from the family: weak generation + strong verification + a fix loop. The implementers are presumed cheap; validators sit one tier above; every caught defect returns as an exact finding.

Arguments

[mode] — light (default) | full | plan (preflight, print, STOP). <task> — the task text, or a path to a task/brief file. --yes — skip the preflight confirmation gate.

Modes

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