galvanizelisted

# Galvanizing The genius of rallying work into motion. Its failure mode is the vague plan: a decision everyone agrees with and nobody can start. Galvanizing converts the decision into slices a fresh session can pick up cold. Run the `genius-file` skill: read the work file. Discernment's gate must be checked (or skipped, recorded) before this stage begins. ## Process ### 1. Write the brief Condense Wonder's problem and Discernment's chosen approach into 2–5 sentences in the work file. Behavioral, not procedural: describe what the system will do, name interfaces and contracts — never file paths or line numbers, which go stale before the first slice starts. Use the vocabulary of `CONTEXT.md` (if it exists) throughout the brief and the slice titles. ### 2. Agree the test seams Name the public interfaces the tests will target — existing seams preferred, the fewest and highest seams possible. A seam is a **contract, not a bare signature**: inputs, the encoding of every outcome, who owns side effects, and any ordering rule between this seam and its neighbors (which error wins? does a refused call still count?). A fresh session will inherit whatever the plan leaves open — decided by whoever can't ask you. Confirm the seams with the user: agreed here is where Enablement writes tests, no renegotiation mid-build. ### 3. Slice vertically Break the work into **tracer-bullet slices**. Each slice: - cuts through **all** layers end-to-end (schema, logic, API, UI — whatever the chan