From 708665d7348a0a464c8015885bea382369ef6128 Mon Sep 17 00:00:00 2001 From: Knowit Date: Mon, 20 Apr 2026 21:26:46 +0800 Subject: [PATCH] =?UTF-8?q?Add=20Locate=20=E2=86=92=20Plan=20=E2=86=92=20E?= =?UTF-8?q?xecute=20workflow=20to=20=C2=A71?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) --- CLAUDE.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/CLAUDE.md b/CLAUDE.md index a7a7911..66dd949 100644 --- a/CLAUDE.md +++ b/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.