Default output: return only the result, blockers, and required evidence. Omit preambles, process narration, repeated context, confidence scores, and follow-up offers. Use at most five bullets unless a required artifact or schema needs more.

Orchestrate

Status: planned. The spawn/wait/handoff driver (scripts/cli.ts) and role references (references/dispatcher.md, references/planner.md) are not in this repository yet. Until they land, use the agents-sdk-dev skill (harness=cursor) with cloud Agent.create({ cloud: { repos } }) for multi-agent work, or the local pattern in agents/research-runner/cursor/runner.ts.

An explicit /ai-eng/orchestrate <goal> will fan out a large task across parallel Cursor cloud agents. Workers don't talk to each other; they talk up through structured handoffs. The intended design: a script owns the spawn/wait loop, the planner writes plan.json, the script executes it, and the planner reads handoffs to decide what comes next.

Required reading: the agents-sdk-dev skill (skills/agents-sdk-dev/SKILL.md in this repo, specify harness=cursor). Spawning, auth, and the error taxonomy live there.

Setup (when implemented)

• CURSOR_API_KEY must be a personal/user key. Create it from Cursor Dashboard > Integrations, then read agents-sdk-dev (harness=cursor) auth guidance.
• SLACK_BOT_TOKEN is optional for Slack visibility in the upstream design.

Workaround today