/swe-wm-update

Single source of truth for WM updates. Uses swe-wm MCP tools for targeted section updates — never overwrites daemon-managed fields.

Every WF_* transition MUST use this skill instead of manual updates.

⚠️ CRITICAL: Use MCP Tools, NOT write_memory

NEVER use write_memory or edit_memory to update WM files. These overwrite the entire file and risk clobbering daemon-managed fields.

ALWAYS use swe-wm MCP tools:

Tool	Purpose
`swe_wm_read`	Read WM state + content
`swe_wm_update_section`	Update a specific section (agent-owned only)
`swe_wm_update_status`	Update `[STATUS]:` tag

Daemon-managed fields (updated automatically by Python hooks — DO NOT touch):

**Current State**: — updated on WF_* reads
**Previous State**: — updated automatically
### Transitions — appended automatically
**Edit Count Since Checkpoint**: — incremented on file edits
**Last Updated**: — timestamped automatically

Step 1: Read Current WM

mcp__swe-wm__swe_wm_read(session_id="{session_id}")

Note the current state and section contents for your update decisions.

Step 2: Gather Data Using Step-Specific Checklist

Find the checklist matching your --from argument below. Complete ALL items.

WF_START

Feature(s) identified from INDEX_FEATURES
Task description captured
Update Current Task section with task + context
Update Feature(s) section
Update Progress with initial items

WF_CLASSIFY

Features identified from INDEX_FEATURES
FEATURE_[KEY] loaded for each feature
Supporting memories loaded (DOM_, SYS_, REF_, ARCH_, INDEX_*)
Requirements validated against domain memories (or "none detected")
Task type classified (simple / medium / large / operational)
Update Affected Features with Primary / Secondary
Update Files with key file paths from feature memories
Update Progress with classification and feature loading steps completed

WF_RESEARCH

Research findings summarized
Symbols / patterns discovered noted
Update Files with files examined
Update Progress with research outcomes
Update Notes with findings

WF_CONTINUE

Previous state verified from WM
Resume point identified
Progress carried forward from previous session
Update Files with files from previous work

WF_ARCH_REVIEW

Design documented with explicit file paths
Update Files with files to modify/create
Layer compliance verified (pass / fail per criterion)
Swarm assessment completed (needed / not needed)
User approval status noted
Update Progress with review results
Update Notes with design decisions

WF_SWARM_ORCHESTRATE

Swarm configuration documented
Agent assignments noted
Topology selected
Update Progress with orchestration steps
Update Notes with swarm config

WF_EXECUTE

Current subtask status
Update Files with files modified / created with descriptions
Tests written / run status
Blockers noted (if any)
Update Progress with implementation steps

WF_CHECKPOINT

All work since last checkpoint summarized
Update Files with files modified with change descriptions
Current phase / subtask status
Update Progress comprehensively

WF_VERIFY

CLAUDE_OBLIGATIONS compliance verified
Architecture compliance verified
Test coverage verified
All progress items marked complete or noted
Update Files — complete list of every file touched in session
Update status to VERIFY_COMPLETE or COMPLETED

WF_DONE

Update status to COMPLETED
Update Context with summary of all work done
Update Notes with memories updated during session
Follow-up items documented (if any)
All Progress items checked off

WF_CLARIFY

Clarification question and user response noted
Task description updated if scope changed
Update Progress with clarification outcome

Step 3: Write Updates Using MCP Tools

Use targeted section updates. One call per section that changed.

# Update task status
mcp__swe-wm__swe_wm_update_status(session_id="{session_id}", status="IN_PROGRESS")

# Update specific sections (replace mode)
mcp__swe-wm__swe_wm_update_section(
  session_id="{session_id}",
  section="Progress",
  content="- [x] Step 1 done\n- [ ] Step 2 pending"
)

# Append to a section (e.g., adding a new file entry)
mcp__swe-wm__swe_wm_update_section(
  session_id="{session_id}",
  section="Notes",
  content="- New finding: ...",
  append=true
)

Agent-owned sections (safe to update):

Current Task, Progress, Files, Notes, Requirements, Implementation Notes, Previous Task, Task Context, Affected Features, Context, Feature(s)

Protected sections (tool will reject these):

Workflow Context, Transitions

Step 4: Validate

After writing, optionally re-read to confirm:

mcp__swe-wm__swe_wm_read(session_id="{session_id}")

Verify:

Session ID is correct
Feature Key(s) is NOT empty or "(to be determined)"
Task description is NOT empty
Progress has actual items
Files lists actual files (if any were touched)
Status reflects reality

Step 5: Confirm & Resume

Output: 📋 Updated Working Memory: WM_{session_id}

⚠️ CRITICAL: DO NOT STOP HERE. This skill is a utility — you MUST continue.

Exit

IMMEDIATELY resume the workflow step you were on before invoking this skill. This is a utility skill — no state change occurs. Your calling step's instructions told you to invoke /swe-wm-update as a sub-step, NOT as a stopping point.

After outputting the confirmation line above:

Do NOT wait for user input
Do NOT end your response
Continue with the next action from the calling WF step_*

If you were invoked from a WF_* step's "MANDATORY NEXT STEP" table, proceed to the transition listed there. If you were invoked mid-step, continue where you left off in that step's instructions.

swe-wm-update