Loading...
Loading...
Found 11 Skills
Decompose complex tasks, design dependency graphs, and coordinate multi-agent work with proper task descriptions and workload balancing. Use this skill when breaking down work for agent teams, managing task dependencies, or monitoring team progress.
Coordinates multi-session, delegated, or long-running work with persistent state, recovery checks, and explicit status transitions. Use when a task spans multiple turns, multiple agents, background jobs, or scheduled loops, or when interrupted work must be resumed reliably.
Use this skill for project management: planning, progress tracking, task coordination, timeline/milestone management, risk assessment, resource allocation, and execution guidance. Examples: <example>User organizing complex development: "Starting feature with frontend, backend, infrastructure changes. Need project plan." → Creates plan with task breakdown, timeline, coordination strategy.</example> <example>User facing delays: "Project behind schedule, unsure how to prioritize tasks." → Analyzes situation, provides recovery plan with prioritized actions.</example>
Provides a prompt template and best practices for building Claude Code agent teams. Covers team composition, teammate spawn prompts, task breakdown, file ownership, communication protocols, and delegate mode. Use when creating an agent team, spawning teammates, parallelizing work across multiple Claude Code instances, or deciding whether an agent team is the right approach.
Multi-agent swarm coordination for complex tasks. Uses hierarchical topology with specialized agents to break down and execute complex work across multiple files and modules. Use when: 3+ files need changes, new feature implementation, cross-module refactoring, API changes with tests, security-related changes, performance optimization across codebase, database schema changes. Skip when: single file edits, simple bug fixes (1-2 lines), documentation updates, configuration changes, quick exploration.
With 'Dao' as the overall controller, consolidate capabilities such as planning, game design, game visual design, general design, review, implementation, summary, and repository maintenance into a unified entry, and call internal modules as needed.
Coordinate team task execution on OpenAnt. Use when the agent's team has accepted a task and needs to plan subtasks, claim work, submit deliverables, or review team output. Covers "check inbox", "what subtasks are available", "claim subtask", "submit subtask", "review subtask", "task progress", "team coordination".
Orchestrate multiple code-writing agents in parallel when the work contains 3 or more genuinely independent build tasks. Use for execution lanes with disjoint write scope, clear task boundaries, and no dependency edges that would force sequencing.
Multi-agent collaboration plugin that spawns N parallel subagents competing on the same task via git worktree isolation. Agents work independently, results are evaluated by metric or LLM judge, and the best branch is merged. Use when: user wants multiple approaches tried in parallel — code optimization, content variation, research exploration, or any task that benefits from parallel competition. Requires: a git repo.
Coordinate complex work using a phase-gated, multi-agent engineering loop (audit → design → implement → review → validate → deliver). Use when you need to split a task into subsystems, run dual independent audits, reconcile findings into a confirmed issue list, delegate fixes in clusters, enforce dual-review PASS gates, and drive an end-to-end delivery. Prefer discovering and invoking other specialized skills when they can execute part of the work faster or more reliably.
Agent skill for swarm - invoke with $agent-swarm