Orchestrator
Wave-based parallel task execution with sub-agents
Install
$ agentstack add skill-mshadmanrahman-pm-pilot-orchestrator ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-mshadmanrahman-pm-pilot-orchestrator) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Orchestrator
Decompose complex work into independent waves of parallel sub-agent tasks.
When to Use
- Tasks with 3+ independent sub-tasks
- Research across multiple sources
- Bulk operations (triage, analysis, review)
- Any work where parallelism saves time
Procedure
- Decompose Work
- Break task into atomic, independent units
- Group into waves (units within a wave have zero dependencies)
- Order waves by dependency: wave 2 depends on wave 1 results
- Plan Waves
`` Wave 1 (parallel): [task-a, task-b, task-c] Wave 2 (parallel, depends on wave 1): [task-d, task-e] Wave 3 (sequential): [merge results] ``
- Launch Sub-Agents
- One Task agent per wave item
- Each agent gets: clear objective, input data, output format
- Each agent writes results to
.claude/manifests/{task-id}.md
- Collect Results
- Wait for all agents in a wave to complete
- Read manifests using
manifest-readerskill - Check for failures or partial results
- Merge and Synthesize
- Combine results from all waves
- Resolve conflicts or inconsistencies
- Produce unified output
Wave Design Rules
- Max 5 agents per wave (resource constraint)
- Each agent should complete in under 2 minutes
- If an agent fails, note failure and continue (don't block the wave)
- Always have a merge step as the final wave
Manifest Format
Each sub-agent writes:
---
task: {task-id}
status: complete | failed | partial
agent: {agent-description}
---
## Findings
{results}
## Errors
{any errors encountered}Output Format
Orchestration: {task name}
Waves: {count}
Results: {success count}/{total count} tasks completed
Summary: {merged findings}
Failures: {list or "none"}Rules
- Never launch wave 2 before wave 1 completes
- Always check manifests before proceeding
- Failed agents should not block successful ones
- Keep each agent's scope small and focused
- Clean up manifest files after final merge
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: mshadmanrahman
- Source: mshadmanrahman/pm-pilot
- License: MIT
- Homepage: https://github.com/mshadmanrahman/pm-pilot#readme
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.