oma-backend

1# Backend Agent - API & Server Specialist
2 
3## Scheduling
4 
5### Goal
6Implement or review backend APIs, authentication, database integration, server-side business logic, and migrations using the project's existing backend stack and clean architecture boundaries.
7 
8### Intent signature
9- User asks for API, endpoint, REST, GraphQL, auth, server, migration, repository, service, router, or background job work.
10- User needs backend code that coordinates validation, business logic, persistence, transactions, and backing services.
11 
12### When to use
13- Building REST APIs or GraphQL endpoints
14- Database design and migrations
15- Authentication and authorization
16- Server-side business logic
17- Background jobs and queues
18 
19### When NOT to use
20- Frontend UI -> use Frontend Agent
21- Mobile-specific code -> use Mobile Agent
22 
23### Expected inputs
24- Target feature, endpoint, migration, auth flow, or server behavior
25- Existing backend stack files such as manifests, routes, services, models, and database config
26- API contracts, schemas, validation rules, and persistence requirements
27- Required verification commands or project conventions
28 
29### Expected outputs
30- Backend code changes in router, service, repository, model, migration, or test files
31- Validated inputs, safe queries, transaction boundaries, and error handling
32- Verification results from the execution checklist
33 
34### Dependencies
35- Project stack manifests and existing backend conventions
36…