project-orchestrator-ops
Project management and multi-agent orchestration for autonomous software development. Use when coordinating development teams, breaking down requirements into tasks, tracking progress across agents, managing scope and timelines, or running end-to-end project builds. Triggers on queries like "build me a website", "create an app", "manage this project", "coordinate the team", "what's the project status", or any request requiring multi-agent coordination.
When & Why to Use This Skill
This Claude skill acts as a sophisticated project orchestrator designed for autonomous software development. it streamlines the entire development lifecycle by transforming high-level requirements into actionable task matrices, coordinating specialized AI agents (such as frontend, backend, and DevOps), and managing complex dependencies. By automating task decomposition, progress tracking, and quality assurance, it enables the seamless delivery of full-stack applications with minimal human intervention.
Use Cases
- Autonomous Full-Stack Development: Orchestrate multiple specialized agents to build complex web or mobile applications from a single requirement brief, handling everything from database schema design to UI implementation.
- Multi-Agent Team Coordination: Act as a digital project manager to assign tasks to specialized sub-agents, monitor their real-time progress, and resolve technical blockers across different phases of the project.
- Automated Project Governance: Maintain rigorous project documentation, including decision logs, status reports, and task breakdowns, ensuring transparency and architectural consistency throughout the build process.
- End-to-End DevOps Integration: Coordinate the handoff between development agents and infrastructure agents to automate CI/CD setup, cloud provisioning, and production deployments.
| name | project-orchestrator-ops |
|---|---|
| description | Project management and multi-agent orchestration for autonomous software development. Use when coordinating development teams, breaking down requirements into tasks, tracking progress across agents, managing scope and timelines, or running end-to-end project builds. Triggers on queries like "build me a website", "create an app", "manage this project", "coordinate the team", "what's the project status", or any request requiring multi-agent coordination. |
Project Orchestrator Operations
Coordinate autonomous software development across specialized agents without human intervention.
Core Workflow
1. Intake & Scoping
On new project request:
- Parse requirements into: features, tech stack, integrations, constraints
- Identify ambiguities → resolve from context or flag for user (batch questions)
- Create project brief with: objectives, success criteria, deliverables, timeline estimate
2. Task Decomposition
Break project into agent-assignable tasks:
PROJECT
├── Phase 1: Foundation
│ ├── [backend-dev] Database schema design
│ ├── [backend-dev] API scaffolding
│ ├── [frontend-dev] Project setup & routing
│ └── [supabase-admin] Database provisioning
├── Phase 2: Core Features
│ ├── [backend-dev] Auth implementation
│ ├── [frontend-dev] Auth UI
│ ├── [frontend-dev] Core screens
│ └── [backend-dev] Business logic APIs
├── Phase 3: Integration
│ ├── [frontend-dev] API integration
│ ├── [api-admin] External service setup
│ └── [testing-ops] Integration tests
├── Phase 4: Polish
│ ├── [frontend-dev] UI refinement
│ ├── [docs-admin] Documentation
│ └── [codebase-admin] Cleanup audit
└── Phase 5: Deploy
├── [github-admin] CI/CD setup
├── [deployment-ops] Production deployment
└── [monitoring-ops] Health monitoring
3. Agent Assignment Matrix
| Task Type | Primary Agent | Backup |
|---|---|---|
| Database/Schema | supabase-admin | backend-dev |
| API Routes | backend-dev | - |
| Business Logic | backend-dev | - |
| UI Components | frontend-dev | - |
| Styling | frontend-dev | - |
| Auth | backend-dev + frontend-dev | - |
| External APIs | api-admin | backend-dev |
| CI/CD | github-admin | deployment-ops |
| Deployment | deployment-ops | github-admin |
| Testing | testing-ops | - |
| Documentation | docs-admin | - |
| Cleanup | codebase-admin | - |
4. Execution Protocol
For each phase:
- Dispatch tasks to agents with: context, inputs, expected outputs, dependencies
- Monitor completion (check file system for deliverables)
- Validate outputs meet acceptance criteria
- Resolve blockers or escalate
- Proceed to next phase when all tasks complete
5. Handoff Format
When dispatching to agent:
## Task Assignment
**Agent:** [agent-name]
**Project:** [project-name]
**Phase:** [N] of [total]
### Objective
[Clear statement of what to build]
### Inputs
- [Files, schemas, specs available]
### Expected Outputs
- [Specific deliverables with paths]
### Acceptance Criteria
- [ ] [Testable criterion 1]
- [ ] [Testable criterion 2]
### Dependencies
- Requires: [prior task outputs]
- Blocks: [subsequent tasks]
### Context
[Relevant project decisions, constraints, patterns to follow]
6. Progress Tracking
Maintain status in project directory:
project/
├── .orchestrator/
│ ├── PROJECT_BRIEF.md
│ ├── TASK_BREAKDOWN.md
│ ├── STATUS.md # Current state
│ ├── DECISIONS.md # Key decisions made
│ └── BLOCKERS.md # Issues requiring resolution
Status format:
## Project Status
**Phase:** 2 of 5 (Core Features)
**Progress:** 60%
**Blockers:** None
### Completed
- [x] Database schema (supabase-admin)
- [x] API scaffolding (backend-dev)
- [x] Project setup (frontend-dev)
### In Progress
- [ ] Auth implementation (backend-dev) - 80%
- [ ] Core screens (frontend-dev) - 50%
### Pending
- [ ] API integration
- [ ] External services
Decision Authority
Autonomous Decisions (No escalation)
- Tech stack choices within project constraints
- File/folder organization
- Code patterns and conventions
- Library selection for common needs
- Error handling approaches
Escalate to User
- Scope changes beyond original requirements
- External service costs or commitments
- Ambiguous business logic
- Security-sensitive decisions
- Timeline extensions >20%
Quality Gates
Before phase transition:
- All tasks marked complete
- Deliverables exist at expected paths
- Build passes without errors
- Tests pass (if applicable)
- No critical TODOs remaining
Before final delivery:
- All phases complete
- Documentation complete (docs-admin)
- Codebase audit passed (codebase-admin)
- Deployment successful (deployment-ops)
- Health check passing (monitoring-ops)
Blocker Resolution
- Missing dependency → Check if prior task complete, re-run if needed
- Ambiguous requirement → Infer from context, document decision
- Technical constraint → Adjust approach, document trade-off
- Agent failure → Retry with more context, escalate if repeated
- External service issue → Use mock/stub, flag for later resolution
Project Templates
Web Application
Phases: Setup → Auth → Core → Polish → Deploy Agents: frontend-dev, backend-dev, supabase-admin, github-admin, deployment-ops
Mobile Application
Phases: Setup → Auth → Screens → API → Deploy Agents: frontend-dev (React Native), backend-dev, supabase-admin, deployment-ops
API/Backend Service
Phases: Schema → Routes → Logic → Tests → Deploy Agents: backend-dev, supabase-admin, testing-ops, deployment-ops
Marketing Site
Phases: Design → Build → Content → Deploy Agents: frontend-dev, docs-admin, deployment-ops