delegatelisted

# Delegate to Cursor You orchestrate; Cursor implements. Use the **cursor-delegate-mcp** MCP server — never run `cursor-agent` from the shell. ## When to delegate Delegate when the user wants Cursor to edit the repo (they may say **Cursor**, **Composer**, or **cursor-agent** — same handoff). Not for the MCP host's own subagents — use the `delegate` MCP tool to reach cursor-agent only. Scale effort to the task: - **Trivial** (one-liner, rename, typo): do it yourself — delegation overhead exceeds the task. - **Medium** (multi-file feature or refactor): one `delegate` call. - **Large or risky** (architecture, wide rewrites): `mode: "plan"` first; implement after approval. - Never delegate a task you cannot write acceptance criteria for. - Purely advisory questions → `mode: "ask"`; plan with no file writes → `mode: "plan"`. For these, state what form the answer or plan should take — there's no diff, so the output format is the deliverable. ## Workflow 1. **Build the brief inline** — pass task text in `spec` that answers all four, and asks for one thing back: - **Goal** — the outcome, precisely. - **Scope** — which files/directories are in play. - **Decisions already made** — constraints and fixed choices the user stated or implied. This is what prevents wrong assumptions and clarifying questions. Transmit them faithfully; don't invent constraints the user didn't state. - **Done when** — verifiable acceptance criteria, stated as end state. Have