agent-orchestration
starsforks
How to install agent-orchestration?
parcadei/continuous-claude-v3/agent-orchestration
$npx -y skills add parcadei/Continuous-Claude-v3 --skill agent-orchestrationAgent Orchestration Rules
SKILL.md
| 1 | # Agent Orchestration Rules |
| 2 | |
| 3 | When the user asks to implement something, use implementation agents to preserve main context. |
| 4 | |
| 5 | ## The Pattern |
| 6 | |
| 7 | **Wrong - burns context:** |
| 8 | ``` |
| 9 | Main: Read files → Understand → Make edits → Report |
| 10 | (2000+ tokens consumed in main context) |
| 11 | ``` |
| 12 | |
| 13 | **Right - preserves context:** |
| 14 | ``` |
| 15 | Main: Spawn agent("implement X per plan") |
| 16 | ↓ |
| 17 | Agent: Reads files → Understands → Edits → Tests |
| 18 | ↓ |
| 19 | Main: Gets summary (~200 tokens) |
| 20 | ``` |
| 21 | |
| 22 | ## When to Use Agents |
| 23 | |
| 24 | | Task Type | Use Agent? | Reason | |
| 25 | |-----------|------------|--------| |
| 26 | | Multi-file implementation | Yes | Agent handles complexity internally | |
| 27 | | Following a plan phase | Yes | Agent reads plan, implements | |
| 28 | | New feature with tests | Yes | Agent can run tests | |
| 29 | | Single-line fix | No | Faster to do directly | |
| 30 | | Quick config change | No | Overhead not worth it | |
| 31 | |
| 32 | ## Key Insight |
| 33 | |
| 34 | Agents read their own context. Don't read files in main chat just to understand what to pass to an agent - give them the task and they figure it out. |
| 35 | |
| 36 | ## Example Prompt |
| 37 | |
| 38 | ``` |
| 39 | Implement Phase 4: Outcome Marking Hook from the Artifact Index plan. |
| 40 | |
| 41 | **Plan location:** thoughts/shared/plans/2025-12-24-artifact-index.md (search for "Phase 4") |
| 42 | |
| 43 | **What to create:** |
| 44 | 1. TypeScript hook |
| 45 | 2. Shell wrapper |
| 46 | 3. Python script |
| 47 | 4. Register in settings.json |
| 48 | |
| 49 | When done, provide a summary of files created and any issues. |
| 50 | ``` |
| 51 | |
| 52 | ## Trigger Words |
| 53 | |
| 54 | When user says these, consider using an agent: |
| 55 | - "implement", "build", "create feature" |
| 56 | - "follow the plan", "do phase X" |
| 57 | - "use implementation agents" |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
