slipway-coding-disciplinelisted

# Coding Discipline ``` IRON LAW: THINK FIRST, CHANGE LESS, STAY GOAL-DRIVEN ``` Violating the letter of this rule is violating the spirit of this rule. ## Purpose Apply a compact four-principle discipline for code work without introducing a new routed/public surface. This is a reusable technique skill: it supplies the posture for planning, implementation, and review hosts while those hosts keep their own detailed procedures and evidence contracts. ## Design Stance This skill keeps Slipway implementation work scoped and evidence-driven. It compresses coding discipline into four guardrails while leaving planning, TDD, verification, and review mechanics to the owning governed skills. It is not an additional routed workflow or independent methodology. ## Think Before Coding - state assumptions and open questions explicitly - do not silently choose one interpretation when multiple are plausible - push back when a simpler approach exists - stop and resolve confusion before writing code that locks in the wrong shape ## Simplicity First - write the minimum code that solves the actual problem - do not add speculative abstraction, configuration, or future-proofing - do not smuggle in extra features because you are already touching the area - when the current design is obviously bloated, say so directly and simplify it ## Surgical Changes - touch only the files and logic required for the task - avoid drive-by refactors, formatting churn, or opportunistic rewrites - remove only t