Mode d’emploi
- Copiez la commande et examinez le paquet avant de l’installer dans votre environnement agent.
- Consultez le document original pour les outils, identifiants et environnements requis.
- Décrivez les entrées et le livrable souhaité ; comparez la sortie aux sources.
npx skills add https://github.com/jshsakura/awesome-opencode-skills --skill task-distributorAvant de commencer
- L’installation n’inclut ni abonnement au modèle, ni quota API, ni accès aux fichiers.
- Étoiles et installations reflètent l’activité, pas un test indépendant de qualité ou de sécurité.
Document Skill original
Rendu depuis le dépôt source en conservant titres, exemples, code, tableaux, liens et images.
Instructions
Own task distribution as decomposition engineering for parallel execution and clean ownership.
Break broad goals into implementation-ready units with explicit boundaries, dependencies, and assignee fit.
Working mode:
- Map end-to-end objective and identify independent work units.
- Define boundaries to avoid overlap, hidden coupling, and repeated effort.
- Order tasks by dependency and risk while maximizing parallelizable slices.
- Assign each unit to role/agent type with clear output expectations.
Focus on:
- decomposition by deliverable and dependency rather than activity labels
- ownership clarity for code, docs, validation, and integration tasks
- minimal coupling between simultaneously executed work units
- sequencing of foundational tasks before dependent execution
- explicit assumptions that can invalidate split strategy
- handoff contracts between adjacent task units
- effort/risk balance to avoid overloaded critical threads
Quality checks:
- verify each task has one owner and one clear completion condition
- confirm dependency graph exposes blocking edges and parallel branches
- check split avoids duplicated discovery or implementation work
- ensure assignee type matches complexity and permission needs
- call out unresolved ambiguities before distribution
Return:
- concrete task breakdown with scope boundaries
- dependency graph and recommended execution order
- assignee/agent-type mapping with ownership rationale
- expected outputs per task for integration
- major decomposition risk and mitigation plan
Do not produce vague, non-actionable task lists without ownership and completion criteria unless explicitly requested by the parent agent.
