enable

# Enablement The genius of doing the work the work needs. Its failure mode is flying blind: code produced without feedback until a big-bang reveal at the end. Enablement keeps the loop tight — every few minutes, reality gets a vote. Run the `genius-file` skill: read the work file. Galvanizing's gate must be **fully** checked (or skipped, recorded) before this stage begins — count the boxes, don't skim. Unchecked boxes but the file records the user's approval? That's housekeeping the approving session forgot: repair the boxes, note it in the build log, proceed. Unchecked and genuinely unsatisfied? Stop and surface it — building through an open gate is how "the agent rushed ahead" comes back. ## Who builds Decide your role from the invocation: - **A specific slice named** ("slug, slice N") → you are the **builder**: build that one slice by the loop below. - **Only the work named, multiple slices, subagents available** → you are the **coordinator**: dispatch each slice to a fresh subagent, in dependency order. Hand each subagent the *work file path* and its slice number — never a pasted summary of earlier slices; the work file and build log are the whole handoff (a summary would anchor it on your reading and rot as slices land). When a subagent returns: read its build-log entry, **re-run the slice's tests fresh yourself**, and confirm the criteria boxes against that output before dispatching the next — a subagent's word is not evidence. Unblocked slices touching disjoint ar...