[BUG] Claude ignores explicit 'do this later/in new session' instructions and implements immediately

Description

Claude ignores explicit user instructions about when to perform actions. When told to "document now, implement in a new session", Claude does both immediately.

Reproduction Steps

1. User identifies a problem that needs fixing
2. User says: "Update Spec 0115 to document the fix. I want to implement it in a new session with fresh context."
3. Expected: Claude updates only the spec documentation (01-requirements.md, 02-plan.md)
4. Actual: Claude updates the spec AND immediately implements the fix in the actual skill files

Actual Behavior

User said (paraphrased):

"Spec 0115 anpassen und hinzufügen, dass wir das als neue Phasen lösen müssen. Ich möchte das in einer neuen Session machen."

Claude's response:

1. ✅ Updated 01-requirements.md with Delta section
2. ✅ Added Phase 8 to 02-plan.md
3. ❌ Immediately edited ~/.claude/skills/spec-executor/SKILL.md
4. ❌ Immediately edited ~/.claude/skills/spec-executor/references/prompt-templates.md

When user complained, Claude apologized but the damage (unwanted edits) was done.

Expected Behavior

When user explicitly says:

• "in a new session"
• "später machen" (do it later)
• "nur dokumentieren" (only document)
• "nicht implementieren" (don't implement)

Claude should:

1. Complete ONLY the explicitly requested action (documentation)
2. STOP before any implementation
3. Optionally confirm: "I've documented the changes. Ready to stop here, or should I continue with implementation?"

Environment

• Claude Code version: Latest (Jan 2025)
• Model: Opus 4.5
• Platform: Linux/WSL2
• CLAUDE.md: Extensively configured with rules (including "User Intent" priority)

Additional Context

The user has a comprehensive CLAUDE.md with explicit rules like:

• "USER INTENT has priority"
• Decision protocols with confidence levels
• Git-lock rules requiring explicit permission

Despite these rules, Claude entered "execution mode" and ignored the temporal boundary ("in new session").

Suggested Fix

A system-level awareness of temporal boundaries in user requests:

• "later", "tomorrow", "new session", "next time" → STOP after current task
• "only X, not Y" → Do X, explicitly skip Y
• When in doubt: ASK before proceeding to next logical step

Workaround

User currently has no effective workaround. Adding more CLAUDE.md rules doesn't help if Claude ignores them during "execution mode."

Potential workarounds that DON'T solve the root cause:

• defaultMode: "askBeforeEdits" - Too aggressive, asks for EVERY edit
• Plan Mode - Helps but must be manually activated each session