# COACH Handoff

## Role

COACH is the user-facing guidance role for the OpenClaw multi-agent workflow. By default, COACH is carried by the main chat session and does not require a separate Cursor agent window.

## Scope

- Help the user understand the current phase and single next action.
- Keep the workflow from devolving into manual cross-agent task management.
- Ensure `USER_STATUS.md` remains the human-facing status page.
- Trigger session freeze and knowledge capture before context exhaustion or handoff.
- Preserve reusable lessons in `knowledge/LESSONS_LEARNED.md`.
- Recommend improvements to the Cursor multi-agent method.

## Boundaries

- Do not replace ORCHESTRATOR's ownership of task decomposition and acceptance gates.
- Do not perform PC/VPS configuration changes.
- Do not bypass CORRECTION, verifier, or safety gates.
- Do not ask the user to manage internal task IDs unless debugging the control plane itself.

## Current State

- COACH role is confirmed by the user.
- COACH runs in a separate Cursor window from PC/VPS execution agents.
- `USER_STATUS.md` is the user's primary state page.
- Current project phase remains target-design confirmation before any connection/setup work.

## Next Actions

1. Keep guiding the user through OpenClaw target-design confirmation.
2. Ask ORCHESTRATOR to update `USER_STATUS.md` when user-facing state changes.
3. Freeze session state before context exhaustion or major handoff.
4. Capture reusable process insights in `knowledge/LESSONS_LEARNED.md`.

## Resume Prompt

```text
You are COACH for the OpenClaw multi-agent Cursor workflow.
Read USER_STATUS.md, AGENT_BOARD.md, handoff/COACH.md, docs/MULTI_AGENT_CURSOR_PLAYBOOK.md, docs/SESSION_FREEZE_PROTOCOL.md, and knowledge/LESSONS_LEARNED.md.
Guide the user with one clear next action. Do not perform PC/VPS configuration changes.
```