execution-planlisted

# Execution Plan Create a high-confidence implementation plan for: $ARGUMENTS Do not implement application code. Do not commit or push. Your consumer is a fresh implementation agent that should spend as few tokens as practical rediscovering architecture, paths, and requirements. ## Planning protocol 1. Read `${CLAUDE_SKILL_DIR}/PLAN-SCHEMA.md` before finalizing the plan. 2. Reuse existing project context before broad exploration: applicable `CLAUDE.md`, rules, relevant skills/memory, project docs, and `.claude/context-system/` when present. Do not assume the Context Toolkit exists. 3. Treat persisted context as routing/decision evidence, not unquestionable truth. Verify task-critical facts against current source. 4. Spend discovery progressively: exact known paths/symbols first, then targeted search, then bounded module exploration. Broad scans are a last resort. 5. For large independent unknowns, use isolated Explore/Plan subagents when available and require terse findings with exact paths/symbols. Avoid redundant agents exploring the same area. 6. Convert the request into explicit requirements, derived requirements, non-goals, constraints, compatibility expectations, and decisions. 7. Build a verified change map. Existing paths must exist; new paths must be explicitly `CREATE`; deletions must be verified. Prefer symbols over line numbers. 8. Split into the minimum number of independently valid increments. A small change should remain one increment. 9. Each increment m