orchestration

Orchestrates multi-agent development workflows with task classification, checkpoints, and delegation.

Updated Jun 14, 2026
One-click install
npx skills add https://github.com/ironkid90-s/lucky5-v7 --skill orchestration-ironkid90-s
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestration
Source: https://github.com/ironkid90-s/lucky5-v7/tree/main/.ptah/skills/orchestration
Command: npx skills add https://github.com/ironkid90-s/lucky5-v7 --skill orchestration-ironkid90-s

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating complex software engineering work across planning, implementation, and QA phases is error-prone when done ad hoc. This Skill provides a structured orchestration layer that classifies any engineering request into one of 8 task types (FEATURE, BUGFIX, REFACTORING, DOCUMENTATION, RESEARCH, DEVOPS, SAAS_INIT, CREATIVE) and drives it through an optimized multi-agent workflow with user validation checkpoints. ## Core Features & Use Cases - Task Classification & Strategy Selection: Detects task type via keyword matrix and complexity scoring, then selects Full, Partial, or Minimal workflow depth with confidence-based decision rules. - 14 Specialist Agents: Coordinates project-manager, software-architect, team-leader, developers, testers, reviewers, researchers, and creative agents through defined invocation patterns and parallel execution where safe. - User Validation Checkpoints: Enforces approval gates after requirements and architecture deliverables, plus QA selection, so nothing ships without explicit sign-off. - 3-Tier CLI Delegation: Optionally lets sub-agents spawn CLI agents (gemini, codex, copilot, ptah-cli) as junior helpers for grunt work like file analysis and test scaffolding, with session resume on timeout. - Use Case: A user reports a memory leak. The skill classifies it as BUGFIX, invokes a researcher to find the root cause, a team-leader to decompose and verify the fix, and a senior-tester to write regression tests, all tracked in a task folder. ## Quick Start Ask the assistant to orchestrate a new task, for example: run /orchestrate followed by a description such as "add WebSocket support for real-time updates" and approve the proposed strategy.

Frequently Asked Questions about orchestration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a new orchestrated development task?▼

Run /orchestrate followed by a task description to start a new task, or /orchestrate TASK_2025_XXX to continue an existing one. The orchestrator classifies the request into one of 8 task types and announces the planned agent sequence before proceeding.

What task types does the orchestration workflow support?▼

It supports 8 task types: FEATURE, BUGFIX, REFACTORING, DOCUMENTATION, RESEARCH, DEVOPS, SAAS_INIT, and CREATIVE. Each type maps to an optimized workflow, such as PM to Architect to Team-Leader to QA for features, or Researcher to Team-Leader to QA for bugfixes.

How does CLI agent delegation work with sub-agents?▼

Sub-agents can spawn CLI agents like gemini, codex, copilot, or ptah-cli as junior helpers via ptah_agent_spawn for focused sub-tasks such as file analysis or test scaffolding. A maximum of 3 CLI agents run concurrently, and sub-agents retain full quality ownership of the output.

What happens when a CLI agent times out or fails?▼

Resume the agent instead of re-spawning by retrieving its CLI Session ID from ptah_agent_status and passing it as resume_session_id to ptah_agent_spawn. The resumed agent loads its previous session context and continues where it left off. Codex does not support resume.

When are user validation checkpoints required?▼

Approval checkpoints are required after the project-manager produces task-description.md and after the architect produces implementation-plan.md. A QA choice checkpoint also follows development completion, letting you pick tester, style, logic, visual, reviewers, all, or skip.

Can the orchestrator write code directly instead of delegating?▼

No. The orchestrator's role is strictly coordination: it delegates all implementation to specialist agents like backend-developer and frontend-developer via the Task tool. When in doubt about a task, the default behavior is to delegate rather than implement directly.