backend-orchestrator
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.
Best use case
backend-orchestrator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
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.
Teams using backend-orchestrator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/backend-orchestrator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How backend-orchestrator Compares
| Feature / Agent | backend-orchestrator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
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.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Backend Orchestrator Skill
## Role
Acts as CTO-Backend, managing all API, database, and service tasks.
## Responsibilities
1. **API Management**
- Design REST endpoints
- Manage API versioning
- Ensure consistent responses
- Coordinate authentication
2. **Database Operations**
- Schema design and migrations
- Query optimization
- Index management
- Data integrity
3. **Service Coordination**
- Business logic implementation
- Service layer patterns
- Third-party integrations
- Background job management
4. **Context Maintenance**
```
ai-state/active/backend/
├── endpoints.json # API registry
├── models.json # Data models
├── services.json # Service definitions
└── tasks/ # Active backend tasks
```
## Skill Coordination
### Available Backend Skills
- `api-development-skill` - Creates/updates API endpoints
- `database-skill` - Schema changes, migrations
- `service-integration-skill` - External service integration
- `auth-skill` - Authentication/authorization
- `testing-skill` - API and service testing
### Context Package to Skills
```yaml
context:
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"]
```
## Task Processing Flow
1. **Receive Task**
- Parse requirements
- Check dependencies
- Load current state
2. **Prepare Context**
- Current API structure
- Database schema
- Service dependencies
3. **Assign to Skill**
- Choose appropriate skill
- Package context
- Set success criteria
4. **Monitor Execution**
- Track progress
- Run tests
- Validate output
5. **Validate Results**
- API tests pass
- Database integrity
- Performance benchmarks
- Security checks
## Backend-Specific Standards
### API Checklist
- [ ] RESTful design
- [ ] Proper status codes
- [ ] Consistent naming
- [ ] Versioning implemented
- [ ] Documentation updated
- [ ] Rate limiting configured
### Database Checklist
- [ ] Normalized schema
- [ ] Indexes optimized
- [ ] Migrations tested
- [ ] Rollback plan
- [ ] Backup verified
- [ ] Performance tested
### Security Checklist
- [ ] Authentication required
- [ ] Authorization checked
- [ ] Input validated
- [ ] SQL injection prevented
- [ ] Sensitive data encrypted
- [ ] Audit logging enabled
## Integration Points
### With Frontend Orchestrator
- API contract agreement
- Request/response formats
- Error standardization
- CORS configuration
### With Data Orchestrator
- Data pipeline coordination
- ETL process management
- Data quality assurance
### With Human-Docs
Updates `backend-developer.md` with:
- New endpoints added
- Schema changes
- Service modifications
- Integration updates
## Event Communication
### Listening For
```json
{
"event": "frontend.api.request",
"endpoint": "/api/new-feature",
"requirements": ["pagination", "filtering"]
}
```
### Broadcasting
```json
{
"event": "backend.api.ready",
"endpoint": "/api/new-feature",
"documentation": "swagger.json",
"tests": "passed",
"performance": "50ms avg response"
}
```
## Test Requirements
### Every Backend Task Must Include
1. **Unit Tests** - Service logic
2. **Integration Tests** - Database operations
3. **API Tests** - Endpoint functionality
4. **Load Tests** - Performance under load
5. **Security Tests** - Auth and validation
6. **Contract Tests** - API contracts maintained
## Success Metrics
- API response time < 200ms
- Test coverage > 80%
- Zero security vulnerabilities
- Database query time < 50ms
- Error rate < 0.1%
## Common Patterns
### Service Pattern
```python
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
```
### Database Pattern
```python
class DatabaseOrchestrator:
def manage_schema(self, task):
# 1. Design schema changes
# 2. Create migration
# 3. Test rollback
# 4. Optimize indexes
# 5. Update documentation
```
## Anti-Patterns to Avoid
❌ Direct database access from controllers
❌ Business logic in API routes
❌ Hardcoded configuration
❌ Missing error handling
❌ No input validation
❌ Synchronous long-running operationsRelated Skills
wp-performance-backend
WordPress backend performance optimization — profiling, queries, object cache, autoload, cron, and remote HTTP. Always-active rules when investigating slowness issues.
woocommerce-backend-dev
Add or modify WooCommerce backend PHP code following project conventions. Use when creating new classes, methods, hooks, or modifying existing backend code. **MUST be invoked before writing any PHP unit tests.**
master-orchestrator
全自动总指挥:串联热点抓取、内容生成与爆款验证的全流程技能。
bmad-orchestrator
Orchestrates BMAD workflows for structured AI-driven development. Routes work across Analysis, Planning, Solutioning, and Implementation phases.
backend-testing
Write comprehensive backend tests including unit tests, integration tests, and API tests. Use when testing REST APIs, database operations, authentication flows, or business logic. Handles Jest, Pytest, Mocha, testing strategies, mocking, and test coverage.
tdd-orchestrator
Master TDD orchestrator specializing in red-green-refactor discipline, multi-agent workflow coordination, and comprehensive test-driven development practices. Enforces TDD best practices across teams with AI-assisted testing and modern frameworks. Use PROACTIVELY for TDD implementation and governance.
nodejs-backend-patterns
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.
dotnet-backend
Build ASP.NET Core 8+ backend services with EF Core, auth, background jobs, and production API patterns.
cc-skill-backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
backend-development-feature-development
Orchestrate end-to-end backend feature development from requirements to deployment. Use when coordinating multi-phase feature delivery across teams and services.
when-building-backend-api-orchestrate-api-development
Use when building a production-ready REST API from requirements through deployment. Orchestrates 8-12 specialist agents across 5 phases using Test-Driven Development methodology. Covers planning, architecture, TDD implementation, comprehensive testing, documentation, and blue-green deployment over a 2-week timeline with emphasis on quality and reliability.