lead
/lead
Koordynuje trwające zadanie z AGY, podczas gdy bieżący agent zachowuje kluczowe decyzje, przegląd i dostarczenie wyniku.
- Autor
- keli-wen ↗
- Repozytorium
- agy-staff ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 24.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 24.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Koordynuje trwające zadanie z AGY, podczas gdy bieżący agent zachowuje kluczowe decyzje, przegląd i dostarczenie wyniku.
Argumenty
/lead [task]
Oryginalny opis (EN)
Orchestrate an ongoing task with AGY while the current agent owns key decisions, review, and delivery. Use when the user invokes /agy:lead or asks you to coordinate a task using AGY.
Jak działa
- Working with AGY
- Dispatch and follow through
Podgląd SKILL.md
--- name: lead description: Orchestrate an ongoing task with AGY while the current agent owns key decisions, review, and delivery. Use when the user invokes /agy:lead or asks you to coordinate a task using AGY. argument-hint: '[task]' --- # 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; unknown interfaces or implementation choices need not be settled before discovery starts. Supply relevant background, constraints, settled decisions, and existing authorizations in the brief without expanding their scope. 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. Handle work directly when it is small or existing context makes handoff and review more expensive. 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. Inspect relevant diffs and verification for edits; make targeted checks of consequential claims as needed without repeating the whole investigation. 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. Handle short, specific checks directly; 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: ```bash 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. Prefer `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.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · keli-wen/agy-staff | 100 | MIT |
| rmyndharis/mandor | 90 | MIT |
| tamdogood/builder-essential-skills | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 295776a4827b (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100agy-lead
Koordynuje trwające zadanie z pomocą AGY, przy czym bieżący agent odpowiada za kluczowe decyzje, przegląd i dostarczenie wyniku. - 100agy-lead
Orkiestruje bieżące zadanie z AGY, a bieżący agent zachowuje kluczowe decyzje, przegląd i dostawę. - 100agy-delegate
Deleguje zadania kodowania do CLI Antigravity (agy) wyłącznie na wyraźną prośbę, przy czym orkiestrator zachowuje odpowiedzialność za przegląd i wdrożenie zmian. - 100agy-delegate
Deleguje zadania kodowania do CLI Antigravity (agy) wyłącznie na wyraźną prośbę, przy czym orkiestrator zachowuje odpowiedzialność za przegląd i wdrożenie zmian. - 100agy-native
Uruchamia zleconą pracę w bezgłowym AGY (Antigravity, Gemini) i zbiera wynik, wyłącznie gdy poproszono o AGY, Antigravity lub Gemini wprost. - 100agy
Kieruje zadanie do CLI agy Google Antigravity, wielomodelowego następcy gemini-cli (Gemini 3.x, Claude 4.6, GPT-OSS), gdy użytkownik wymienia agy, antigravity lub gemini.