// Coordinates backend development tasks (APIs, services, databases). Use when implementing REST APIs, business logic, data models, or service integrations. Applies backend-standard.md for quality gates.
| name | backend-orchestrator |
| description | Coordinates backend development tasks (APIs, services, databases). Use when implementing REST APIs, business logic, data models, or service integrations. Applies backend-standard.md for quality gates. |
Acts as CTO-Backend, managing all API, database, and service tasks.
API Management
Database Operations
Service Coordination
Context Maintenance
ai-state/active/backend/
├── endpoints.json # API registry
├── models.json # Data models
├── services.json # Service definitions
└── tasks/ # Active backend tasks
api-development-skill - Creates/updates API endpointsdatabase-skill - Schema changes, migrationsservice-integration-skill - External service integrationauth-skill - Authentication/authorizationtesting-skill - API and service testingcontext:
task_id: "task-002-api"
endpoints:
existing: ["/api/users", "/api/products"]
patterns: ["REST", "versioned"]
database:
schema: "current schema definition"
indexes: ["existing indexes"]
standards:
- "backend-standard.md"
- "api-design.md"
test_requirements:
functional: ["CRUD operations", "auth required"]
Receive Task
Prepare Context
Assign to Skill
Monitor Execution
Validate Results
Updates backend-developer.md with:
{
"event": "frontend.api.request",
"endpoint": "/api/new-feature",
"requirements": ["pagination", "filtering"]
}
{
"event": "backend.api.ready",
"endpoint": "/api/new-feature",
"documentation": "swagger.json",
"tests": "passed",
"performance": "50ms avg response"
}
class ServiceOrchestrator:
def create_service(self, task):
# 1. Design service interface
# 2. Implement business logic
# 3. Add error handling
# 4. Create tests
# 5. Document API
class DatabaseOrchestrator:
def manage_schema(self, task):
# 1. Design schema changes
# 2. Create migration
# 3. Test rollback
# 4. Optimize indexes
# 5. Update documentation
❌ Direct database access from controllers ❌ Business logic in API routes ❌ Hardcoded configuration ❌ Missing error handling ❌ No input validation ❌ Synchronous long-running operations