claude-delegate-local-mcp: Skill for Claude Code

Session execute

The plan was approved. session-plan stopped here on purpose; this is what it was stopping for.

If you cannot find the approved plan, stop and say so. Reconstructing it from the conversation produces something nobody approved, and the difference is invisible afterwards.

Read the hand-off notebook in the plans directory before the first edit. It says what this machine is set to that the repository does not, and it is the only place that knows.

1. What may run at once

Overlap what is genuinely independent — wall-clock is worth having — but the limits here are not about compute:

• Delegations and delegated agents overlap freely, whether they read or write.
• Never a suite while a fan-out is live. The server shares this machine.
• Every commit edits the top of CHANGELOG.md, so two items built in parallel conflict there even when nothing else they touch does.

A worktree lets a suite run while work continues, with PYTHONPATH set. conftest.py puts the worktree's src/ first, but a test that starts a subprocess never runs it and imports the main checkout through the editable install; PYTHONPATH=<worktree>/src makes both import the worktree. Ignored config files must be copied in or tests that need them skip — the notebook has this machine's paths.

What spends the window is what enters this conversation, and that is as true of writing a module as of reading one. Quote a suite's tail rather than pasting its whole run.

2. Closing out a commit

In order, every time:

1. Full suite, plus ruff and mypy. Targeted runs are the right tool while you iterate; the full suite is what closes a commit, because a targeted run cannot see the coupling a change creates. What has to be green is what lands: a branch is squash-merged, so that is its tip rather than every intermediate commit. ruff format is not a gate here; ruff check is, and so is mypy src, which CI's lint job runs too. It imports nothing, so it can run beside a suite; a second warm, a minute cold.
2. The CHANGELOG entry, written to CHANGELOG.md's own header — it states the heading shape, the subsections and what an entry has to carry, and restating that here is how the two would come to disagree. The heading's number is provisional at this point; §4 is where it gets checked.
3. The owning document, from python scripts/docs_gate.py --owner <path> and never from memory. Changing the code means updating its owner in the same commit.
4. python scripts/docs_gate.py --mode pre-commit, with the change staged. Confirm it is staged first — git diff --cached --name-only must print at least one path. With nothing staged the gate prints 0 file(s) changed and then PASS, having run no ownership check at all, and that pass is indistinguishable from a real one.
5. PLAN.md: flip the marker and change nothing else in that document. A ✅ body is frozen — no rewording, no line added or removed. A parent goes ✅ only once all its children are.
6. The hand-off notebook: delete before you add. Remove every line this commit just filed into CHANGELOG.md, DECISIONS.md, JOURNAL.md or PLAN.md, then add only what is still unfiled. The notebook holds what an upcoming session needs and nothing a tracked document already has, so it shrinks as work lands.