Loading...
Loading...
Coordinates skills, frameworks, and workflows throughout the project lifecycle using pattern-based sequencing, goal decomposition, phase-gate validation, and multi-agent orchestration. Use when starting multi-phase projects, sequencing frameworks, decomposing goals into capability plans, validating phase-gate readiness, coordinating subagents, or designing MCP-based tool orchestration.
npx skill4agent add oakoss/agent-skills orchestrationagent-patterns| Need | Action |
|---|---|
| Identify project type | Classify as Pattern A / B / C |
| Sequence frameworks | Follow pattern-specific phase order |
| Decompose a goal | Extract required effects, match capabilities |
| Validate readiness | Check phase-gate criteria before advancing |
| Find alternatives | Generate fallback capabilities per step |
| Score a plan | Evaluate cost, latency, risk, diversity |
| Coordinate agents | Select orchestration pattern for task type |
| Pass context | Use context distillation for subagents |
| Pattern | Characteristics | Timeline |
|---|---|---|
| A: Simple Feature | Existing system, well-understood, single-team | 1-5 days |
| B: New Product/System | From scratch, security/compliance matters | 4-12 weeks |
| C: AI-Native/Complex | AI agents, RAG, knowledge graphs, orchestration | 8-20 weeks |
| Gate | Entry Criteria |
|---|---|
| Design (Phase 2) | PRP complete, problem validated, success metrics, user stories |
| Development (3) | Architecture documented, data model designed, security threats mapped |
| Testing (Phase 4) | Features complete, unit tests over 80%, code review, SAST clean |
| Deployment (5) | All tests passing, UAT completed, security tested, coverage over 90% |
| Factor | Weight | Scores |
|---|---|---|
| Cost | 0.3 | free=1.0, low=0.8, medium=0.5, high=0.2 |
| Risk | 0.3 | safe=1.0, low=0.8, medium=0.5, high=0.2 |
| Latency | 0.2 | instant=1.0, fast=0.7, slow=0.3 |
| Diversity | 0.2 | min(unique_domains / 5, 1.0) |
| Pattern | Use Case |
|---|---|
| Hierarchical | Parent delegates to specialized subagents |
| Sequential | Chain of experts (architect -> dev -> review) |
| Parallel | Independent tasks running simultaneously |
| Handoff | One agent passes context to the next |
| MCP Primitive | Role in Orchestration |
|---|---|
| Resources | Discover available data (schemas, configs, docs) before work |
| Tools | Execute validated actions with typed arguments |
| Prompts | Reuse domain-specific instruction templates across agents |
| Sampling | Allow servers to request AI reasoning mid-execution |
| Mistake | Correct Pattern |
|---|---|
| Treating all projects as Pattern A (simple feature) | Classify first: Pattern A (simple), B (new product), C (AI-native) before selecting frameworks |
| Skipping phase gates to move faster | Enforce gate criteria before advancing; skipping causes compounding rework |
| Activating all available skills simultaneously | Limit to 1-3 skills per phase with clear deliverables and handoffs |
| No decision logging for capability choices | Log rationale, alternatives considered, scores, and rejection reasons at each step |
| Building HTN plans without validating preconditions | Check project state (files, dependencies, env vars) against each capability's requirements first |
| Delegating without a clear objective manifest | Every subagent needs an objective, constraints, max tokens, and available tools |
| Passing entire codebase to subagents | Use context distillation to pass only relevant symbols and facts |
ExploreTaskPlan