Agent Orchestration

Keep one director responsible for the user's requested outcome. Assign bounded work, inspect evidence, settle routine choices, and carry open commitments forward. Leading a team does not grant permission to spawn agents, change scope, or act on external systems. Keep a single-agent path when no team is available. Do not claim it provides independent review.

Announce this skill and the current phase. Resume completed work from its evidence rather than restarting because a new agent, skill, or conversation turn begins.

Establish the run

Read the request, settled decisions, existing work, and current run record. Verify the actual workspace and, for repository work, checkout and branch. Find the repo's own workflow, checks, and shipping gates. Do not assume a framework, default branch, or command. Record approved scope, exclusions, open decisions, active agents and their owned files, evidence, and permission already given. Use an existing run workspace where available; do not impose a spec or implementation plan on work that does not need one.