Add Locate → Plan → Execute workflow to §1

Why: Charles wants an explicit three-phase workflow alongside the
existing "Think Before Coding" checklist, not a replacement.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

CLAUDE.md

@@ -18,6 +18,12 @@ Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-s
 
 **Don't assume. Don't hide confusion. Surface tradeoffs.**
 
+**Workflow: Locate → Plan → Execute.** Never jump straight to edits.
+
+1. **Locate**: find the relevant files, functions, call sites, and tests. Quote or cite the existing code before proposing changes. If you can't locate it, say so — don't guess.
+2. **Plan**: state the intended change in one or two sentences. List assumptions and open questions. If uncertain, ask before writing code.
+3. **Execute**: make the minimal edit that matches the plan. Deviations require a new plan, not silent improvisation.
+
 Before implementing:
 - State your assumptions explicitly. If uncertain, ask.
 - If multiple interpretations exist, present them — don't pick silently.