Agent swarm
Skill Yesterday-AI/skills/plugins/personal-agent/skills/agent-swarm
Yesterday's PUBLIC plugin catalog for Claude Code and Cursor
npx -y skills add Yesterday-AI/skills --skill agent-swarmAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Orchestrate specialized coding agents in isolated worktrees for parallel development tasks.
SKILL.md
1.5 KB, as published. Nobody here has run it
Agent Swarm Orchestration 🐝
Orchestrate specialized coding agents in isolated worktrees. Based on Elvis Sun's architecture.
Concept
- Orchestrator (You): Holds business context, decisions, memory. Spawns agents.
- Workers (Agents): Hold codebase context only. Run in isolated
git worktrees. - Loop: Monitoring script checks PRs, CI, and agent health.
Usage
1. Spawn an Agent
# Creates a worktree and prepares the task context
./skills/agent-swarm/scripts/spawn-agent.sh <task-name> <branch-name> "<prompt>"
2. Monitor Progress
# Checks all active agents and reports status
./skills/agent-swarm/scripts/monitor-agents.sh
Structure
Each agent gets:
- Isolated Git Worktree:
../worktrees/<feature-branch> - Task Context: A dedicated prompt file.
- Session: A tracked session (TMux or OpenClaw Sub-Agent).
Rules 🛡️
- CONTEXT_SEPARATION: Orchestrator knows why (Business). Worker knows how (Code). Do not overload workers with business docs.
- DEFINITION_OF_DONE: PR created + CI passed + Self-Review done.
- FAIL_FAST: If an agent is stuck, kill it and respawn with better context (don't loop).
Adapted for OpenClaw by ManniTheRaccoon. 🦝