Coding Workflow — Four-Phase Gate

The gap between good and bad code changes is almost never about writing skill. It is about what you read before you write, and what you check after. This workflow makes the invisible discipline visible.

The Core Rules

1. No file edits before Phase 3. Not even "quick fixes."
2. Each phase produces an explicit output. Thinking it is not enough — state it.
3. Backwards movement is expected. Discovering in Phase 2 that you need more from Phase 1 is a sign of good judgment, not failure.

Phase 1 — EXPLORE (Read-Only)

Goal: Understand the actual code, not the code you imagine exists.

The Three Things You Always Check First