codev: Skill for Claude Code

/arch-save — save state, clear, and come back as yourself

Long sessions accumulate stale context. This is the deliberate cure: you choose the moment, you choose what survives, and a fresh session resumes from what you wrote.

$ARGUMENTS carries the architect name, a next task for the session that comes back, or both:

/arch-save                                  save, clear, re-init, then wait
/arch-save file and spawn that issue        … and start on that first, unprompted
/arch-save main file and spawn that issue   explicit name, then the next task

The next task is how an owner who already knows what the refreshed session should do first says so once, at the moment they direct the refresh, instead of watching for the re-init to land and typing it again.

When NOT to run this

On the owner's direction, or when the owner runs it themselves. Do not invoke this autonomously mid-task on your own judgement — the irreversible step is a human decision, relocated from "press /clear" to "invoke /arch-save", not removed. If the owner tells you to run it, run it; if you think it is time, suggest it and wait.

Only at a resumable boundary — a gate approval, a PR merge, a completed investigation, the end of a long tool-heavy stretch. Never mid-task. Nothing here can check that; the state file must describe a point a fresh session can resume from, not a half-finished action. A mid-task snapshot resumes into confusion.

The procedure

Do these in order. The order is the feature — step 3 must precede step 4, because the context that knows what to write is the one about to be destroyed.

1. Resolve your name, then split off the next task

Always run afx whoami first, whatever $ARGUMENTS holds — the split below cannot tell a name from a task until it knows your name. The name rules are unchanged:

• type: architect → the reported name is yours.
• type: builder → STOP. This terminal is a builder. Report the mismatch.
• Non-zero exit → you have no name yet. A single-token $ARGUMENTS that validates as a name is still accepted as one; anything else → STOP and ask which architect you are. Do not guess, and do not default to main — writing another architect's state file is the exact failure /arch-init exists to prevent (#1094).