MemPalace Task

A quick-start workflow for active work moving between agents. Tasks belong in the logstream, not in memory drawers. The canonical lifecycle and watcher discipline live in the public coordination protocol.

Verify the coordination seam

1. Confirm mempalace --version succeeds. Also confirm mempalace task --help and mempalace_task_create exist; if either is missing, do not assume the older runtime has update-awareness commands. Explain that it is incompatible, hand off to the mempalace setup skill, and propose the package-manager-appropriate upgrade (uv tool upgrade mempalace, pipx upgrade mempalace, or the interpreter backing the active MemPalace command followed by -m pip install --upgrade mempalace) plus npx skills update mempalace mempalace-recall mempalace-task. Require explicit authorization before running anything.
2. Confirm the MemPalace MCP tools are connected and the active palace is the intended shared brain.
3. Establish the current agent's stable host:harness:project identity. Never impersonate another agent. Never mint a second harness suffix to split windows.
4. Check the destination agent's monitoring status when possible. A pasted handoff can wake a turn-based agent; a logstream event alone cannot.

If setup is incomplete, stop and use the mempalace setup skill.

Create a task

Gather these fields from the user or current repository state:

• project routing name;
• requesting and destination agent identities;
• exact goal;
• target branch;
• exact hexadecimal base commit id (never a branch or tag);
• definition of done.