agent-orchestration▌
parcadei/continuous-claude-v3 · updated Apr 8, 2026
When the user asks to implement something, use implementation agents to preserve main context.
Agent Orchestration Rules
When the user asks to implement something, use implementation agents to preserve main context.
The Pattern
Wrong - burns context:
Main: Read files → Understand → Make edits → Report
(2000+ tokens consumed in main context)
Right - preserves context:
Main: Spawn agent("implement X per plan")
↓
Agent: Reads files → Understands → Edits → Tests
↓
Main: Gets summary (~200 tokens)
When to Use Agents
| Task Type | Use Agent? | Reason |
|---|---|---|
| Multi-file implementation | Yes | Agent handles complexity internally |
| Following a plan phase | Yes | Agent reads plan, implements |
| New feature with tests | Yes | Agent can run tests |
| Single-line fix | No | Faster to do directly |
| Quick config change | No | Overhead not worth it |
Key Insight
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.
Example Prompt
Implement Phase 4: Outcome Marking Hook from the Artifact Index plan.
**Plan location:** thoughts/shared/plans/2025-12-24-artifact-index.md (search for "Phase 4")
**What to create:**
1. TypeScript hook
2. Shell wrapper
3. Python script
4. Register in settings.json
When done, provide a summary of files created and any issues.
Trigger Words
When user says these, consider using an agent:
- "implement", "build", "create feature"
- "follow the plan", "do phase X"
- "use implementation agents"
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★53 reviews- ★★★★★Valentina Martin· Dec 28, 2024
agent-orchestration has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Chen Sanchez· Dec 28, 2024
Keeps context tight: agent-orchestration is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Aditi Smith· Dec 28, 2024
Useful defaults in agent-orchestration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Valentina Chen· Dec 24, 2024
Registry listing for agent-orchestration matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Aarav Bansal· Nov 19, 2024
Useful defaults in agent-orchestration — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Kabir Taylor· Nov 19, 2024
We added agent-orchestration from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Maya Ndlovu· Nov 19, 2024
agent-orchestration has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Ira Sethi· Oct 10, 2024
I recommend agent-orchestration for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Kabir Martin· Oct 10, 2024
agent-orchestration fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Aarav Perez· Oct 10, 2024
Solid pick for teams standardizing on skills: agent-orchestration is focused, and the summary matches what you get after install.
showing 1-10 of 53