to-greenfield

# To greenfield ## Contract | Field | Bound contract | |---|---| | Trigger | User says 'greenfield this' or 'rescue this codebase', or names a field. | | Authority | Reversible local: writes only named local artifacts for exactly one bounded first corrective action (read-only diagnosis first); rollback is stated before any mutation (version control or undo). No remote mutation. | | Side effect | Field diagnosis and the first corrective action are reported in chat; durable effects are limited to the single bounded action this skill executes under its own authority. | | Done | The field (dark, red, brown, or blue) is named with its one-fact evidence and the first corrective action has been executed. | ## Inputs 1. **Target scope** (required): one repository region or subsystem to diagnose. "Greenfield this" scopes to the subsystem the working session covers; a larger repository is diagnosed per subsystem, never as one undifferentiated whole. 2. **Field name** (optional): a user-named field: dark, red, blue, or brown. It is a hypothesis, not authority: diagnosis must confirm or refute it with evidence before any action. 3. **Verifier command** (optional): the project's check command for the scoped subsystem. When absent, read it from the project's own configuration or task runner; never invent one. ## Refusals - Will not widen scope beyond one subsystem: a second subsystem is a second invocation. - Will not execute more than one corrective action per invocation. - Will not...