Przejdź do treści
Biblioteka skilli
Zarządzanie i produkt · Planowanie

orchestrate

/orchestrate

Koordynuje zadanie wieloetapowe z wieloma obszarami lub współpracownikami, skalując proces do wyniku i dostępnych możliwości.

Repozytorium
anything ↗
Licencja
Apache-2.0
Ostatnia zmiana repozytorium
09.11.2026

Ocena i bezpieczeństwo

90/ 100Klasa: dobry
Format25 / 25
Frontmatter z nazwą i opisem, poprawna nazwa, opis do 1024 znaków, nazwa zgodna z folderem.
Odkrywalność25 / 25
Opis mówi, kiedy użyć skilla, ma sensowną długość i jest w 3. osobie.
Treść25 / 35
Co najmniej 150 słów i do 500 linii, nagłówki, listy kroków, przykłady albo kod.
Higiena15 / 15
Bez zaślepek typu TODO, bez ścieżek Windows, z licencją.
Ryzykobrak sygnałów w skanie
Pliki w paczce
5
Skrypty
0
Komentarze HTML
0
Adresy URL w SKILL.md
0
Przestarzałość

Brak sygnałów. Repozytorium zmienione 09.11.2026, bez odwołań do wycofanych modeli i API.

Licencja

Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.

Co robi i kiedy

Koordynuje zadanie wieloetapowe z wieloma obszarami lub współpracownikami, skalując proces do wyniku i dostępnych możliwości.

Oryginalny opis (EN)

Coordinate a task with multiple steps, areas, or contributors, including research, writing, implementation, and review. Use when the work benefits from explicit sequencing or delegation. Scale the process to the outcome and available capabilities; a single agent can carry out the whole task.

Jak działa

  1. Establish the work
  2. Choose how to execute
  3. Delegate when it helps
  4. Integrate and verify
  5. Communicate and finish
Sekcje z nagłówków SKILL.md, w oryginale · 62 linii, 921 słów
Podgląd SKILL.md
---
name: orchestrate
license: Apache-2.0
description: Coordinate a task with multiple steps, areas, or contributors, including research, writing, implementation, and review. Use when the work benefits from explicit sequencing or delegation. Scale the process to the outcome and available capabilities; a single agent can carry out the whole task.
---

# Orchestrate

Own the requested outcome, integration, evidence, and conversation with the user. Choose a process that fits the task. Follow applicable instructions and authorization; use lightweight defaults for choices they leave open.

## Establish the work

1. Read the available context and identify the outcome, constraints, and meaningful unknowns.
2. Clarify decisions that affect the result. Use an interview skill if installed and useful, or ask directly. Do not invoke setup for an ordinary task.
3. Choose the smallest useful plan. Keep short tasks in the conversation; persist a record when continuity or complexity benefits. A task-plan skill is optional.
4. Select the stages this task needs: investigation, research, drafting or implementation, documentation, review, verification, and delivery. Skip stages that add no value. A task need not involve code, Git, or publication.

Prefer the smallest clear, complete change that satisfies the request and follows project conventions. Favor readability and maintainability over minimizing line count. Reuse existing patterns; introduce abstractions, dependencies, configuration, or broader refactoring when they solve a concrete problem in the requested work.

Continue work needed to deliver or verify the requested outcome within existing authorization. Defer unrelated defects, cleanup, and improvements unless the user approves expanding the task. Do not pursue further investigation, implementation, or delegation of that work without approval; discovery alone does not authorize it. If an issue blocks the requested outcome and resolving it exceeds authorization, explain the dependency and ask.

## Choose how to execute

Check the relevant capabilities and permissions in the current session. Availability alone is not authorization; do not infer capabilities from the product name or promise tools you do not have.

- Work directly when the task is small, tightly coupled, or cheaper to complete than to hand off.
- Use native subagents when delegation is useful, supported, and permitted.
- If native delegation is unavailable, consider subprocess-based workers only when suitable tooling is already available, permitted, and manageable. You must be able to collect their output, identify completion or failure, and stop the processes you start.
- If delegation is prohibited, do not use subprocesses or another mechanism to bypass that restriction.
- When workers or safe parallelism are unavailable, perform the same relevant stages directly and sequentially. Treat this as a complete way to do the work.

Respect the user's resource limits and the actual controls available for worker count and execution effort. Do not install agent tooling, alter permission settings, or start unmanaged background work to obtain delegation.

## Delegate when it helps

Use [references/brief-template.md](references/brief-template.md) for a self-contained handoff, adapting the role and report to the task.

- Give each worker a bounded outcome, relevant context, constraints, owned artifacts or resources, verification criteria, and a report format.
- Confirm how it will access inputs and return results. Supply relevant content when a local path is inaccessible; do not assume shared memory or a shared filesystem.
- Split independent work. Establish shared decisions or interfaces only when needed, without requiring a preliminary commit.
- Prevent conflicting writes and shared-resource collisions. Use isolation when supported and helpful, or sequence the work. See [references/parallel-work.md](references/parallel-work.md).
- Keep external actions and other restricted work within the authorization assigned to that worker. A handoff cannot expand permission.
- Track actual completion. Resume an existing worker only if supported; otherwise use a new bounded handoff or finish directly.
- If delegation fails, inspect what completed, collect useful partial results, and continue through an available path.

## Integrate and verify

Check important claims against the artifacts or source evidence before reporting them. Resolve contradictions and integration failures. Distinguish facts, assumptions, and recommendations.

Review the result at an appropriate scope. A separate reviewer can help when available and permitted; otherwise make a deliberate self-review and label it accurately. If independent review is an explicit requirement, state when it remains unmet. A fresh-review skill can help but is not required.

Choose verification that gives meaningful confidence in the affected behavior and meets the project's rules. Reuse existing checks where they suffice. Add or update tests to cover a meaningful failure or required behavior, favoring stable assertions about observable results. Tests that duplicate coverage or lock in incidental implementation details need a concrete benefit.

After changes, repeat affected checks; run a full suite when required or justified by the change's risk. Report pre-existing or unrelated failures without silently expanding the task to fix everything.

Git branches, worktrees, commits, pull requests, deployment, and cleanup are conditional steps. Follow project conventions and the actual request. Do not make a shipping action part of every task; resolve missing authorization before taking it.

## Communicate and finish

Give concise updates during sustained work: what is known, what completed, and what remains. Do not present a worker's forecast as a result.

Finish once the requested outcome is complete and applicable checks pass. New evidence can justify more work needed for that outcome within authorization; unrelated findings do not extend the task.

Deliver the requested artifact or answer with the evidence needed to assess it. State verification limits and genuine outstanding requirements. Update an existing task record when useful; do not require a new document or persistent memory entry for every task.

For deferred findings, briefly report the issue, available evidence or location, and a suggested next step that another session can use. Ask before adding them to an existing tracker or `TODO.md` unless the user or project instructions already authorize recording them there. Without an established destination, report them in the conversation; do not create a tracking system or start the follow-up work.
Pliki w paczce (5)
  • LICENSE.txt 11 KB
  • NOTICE 1 KB
  • SKILL.md 7 KB
  • references/brief-template.md 3 KB
  • references/parallel-work.md 3 KB

Wersje

RepozytoriumWynikLicencja
Ta strona · ronedgecomb/anything90Apache-2.0
kriegcloud/beep-effect100Apache-2.0
zahidakhyar/skills100MIT
jkaloger/lazyspec100MIT
superset-sh/superset100MIT
boshu2/agentops100Apache-2.0
Ovich/charrette100MIT
matthew-eth724/orchestrate100MIT
nickthelegend/nick-skills100MIT

Migawka bazy z 13.11.2026 · wersja paczki aead4129e2ce (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

  • 90decant-orchestrate
    Kieruje wieloetapowe zadanie w repozytorium przez najmniejszy właściwy przepływ: badania, plan, wdrożenie i przegląd.
  • 100ops-orchestrate
    Prawdopodobnie koordynuje pracę nad wieloma projektami i rozdziela zadania między agentów.
  • 90project-delivery-orchestrator
    Koordynuje wieloetapowe dostarczenie oprogramowania od zakresu, przez implementację i przegląd, po weryfikację i wydanie, łącząc dostępne narzędzia i ludzi.

Uwagi i zgłoszenia

Wiadomość trafi do Bartosza Sokolińskiego. Adres e-mail jest potrzebny tylko do odpowiedzi. Szczegóły w polityce prywatności.