agy lead

Task orchestration with AGY. You are the lead in the current harness. With an argument, work on that task; otherwise apply this guidance to the active task. Extend it across the session only when the user asks.

Working with AGY

1. Frame the assignment. Orient just enough to state the outcome and completion criteria. Discovery itself can be delegated when the right next step is unclear. Supply relevant background and existing authorizations without expanding their scope. Copy the user's constraints and prohibitions into the brief word for word, in a section of their own; your framing goes around them, never in place of them. Leave out instructions addressed to you about orchestration, such as which skill to use or what to delegate: the worker does its assignment itself. State which decisions are settled and which are left to the worker, and check the facts a settled decision rests on, such as the project's current version, before writing it down. When the task has a deadline, launch with a --timeout that leaves you time to assess and deliver, state the deadline in the brief, and ask for the best result available by then. AGY sees its brief and its conversation, not the host's intervening discussion.
2. Default to delegating substantive work. Use AGY to advance the task while you own user communication, cross-task decisions, acceptance, integration, and delivery. Delegation saves your context and quota, not total time or tokens. Handle work directly when it is small or existing context makes handoff and review more expensive. Shape the handoff to the work: noisy exploration whose conclusion is cheap to check hands off cleanly; a tightly coupled change stays in one assignment that includes its investigation and verification, and the worker reports the design choices it made. Make routine orchestration choices within the user's existing authorization. Stay within the requested scope and stage: discussing a proposal does not authorize implementing it.
3. Choose persona and worker scope by outcome. Default to staffer; choose a specialist when the user requests it or its guidance materially improves the assignment (researcher for a source-backed survey, reviewer for independent critique, implementer for a scoped code change with verification). Reserve ask for installation smoke tests or explicit testing; do not route ordinary work to it. Keep related context together and choose worker count by useful independent outcomes. Implementation normally includes necessary verification in the same assignment; avoid splitting one change into implement, test, and review handoffs. Before parallel assignments that share interfaces, naming, or approach, settle those decisions and include them in each affected brief. Workers that edit files in parallel need separate git worktrees, each launched from its own worktree, because job state and continuation are per worktree; otherwise run editing assignments one at a time and parallelize only reads.
4. Wait by default. After dispatch, wait for the result through jobs. Parallel host work should be an already-identified independent task worth handling directly. Idle time is not a reason to open another investigation into the same problem; avoid duplicating delegated work or delivering conclusions that depend on unavailable worker results.
5. Require an assessable result. Specify the artifacts and evidence needed for acceptance. For example: research findings with sources and uncertainties; actual implementation changes with verification results, consequential choices, and remaining issues; or review findings with locations, triggering conditions, evidence, and impact, plus coverage limits even when no issues are found. Adapt these requirements to the task. The worker may analyze and recommend; you retain final judgment.
6. Assess, then decide the next step. Read every result against completion criteria and check for conflicting assumptions or interfaces across workers. Read the worker's status line and any conflicts it reports between its brief and what it observed first; a conflict may overturn a settled decision. Inspect relevant diffs and verification for edits; make targeted checks of consequential claims as needed without repeating the whole investigation. Check interface and public API choices, choices that depart from the brief, and figures the worker reports as verified. Acceptance should cost a fraction of doing the work yourself. Fix a small defect you already understand directly; turn substantive gaps into focused follow-ups, continuing the existing conversation when its context helps and supplying new user decisions. Use a fresh conversation for an independent opinion or different context. Take over when another handoff is unlikely to help. Integrate the results, disclose material omissions, and complete the requested delivery when the task is satisfied. Add review rounds only when they resolve meaningful uncertainty.

Dispatch and follow through

Read ../jobs/SKILL.md for result collection, cancellation, continuation, and recovery. This skill lives at <plugin-root>/skills/lead/SKILL.md. Write the brief to a temporary file and call the shared companion:

node "<skill-dir>/../../companion/agy-companion.mjs" staffer --prompt-file "<brief-path>"

For a specialist, replace staffer with research, review, or implement. When requesting code review, use the review-brief guidance in ../reviewer/references/code-review.md. Modes retain their existing model and permission defaults; honor user overrides. Run unsandboxed as described in ../jobs/references/troubleshooting.md (escalated execution in Codex).

Keep each returned job ID with its assignment and collect the result through jobs. Use continue --job <id> for follow-ups; the companion refuses it while that job is still running. Let useful running work finish when feedback can wait; for an immediate change, follow jobs' cancel, confirm termination, then continue sequence. Account for partial work after interruption and follow the existing timeout recovery rules.

In this workflow you compose briefs and synthesize results. The persona skills' thin-shell and verbatim-delivery instructions apply to direct persona invocations. Preserve exact quotes, figures, errors, and evidence references when integrating results. The lead skill uses existing companion modes; it adds no scheduler.