| name | backend-rag-integration |
| description | Backend HTTP API, SQLite, Qdrant, integration contracts, schema and migration safety. |
| when_to_use | Server routes, DB schema, RAG retrieval wiring, breaking API changes, service boundaries. |
Backend, RAG, and integration
Role
Mike (Engineering Orchestrator) and Devon (Backend Architect Lead) use this skill for Python backend and data plane work (delegate vs own per task).
Load
- Active contracts/plans under
[PRODUCT_CODE_ROOT]/docs/plans/
- Gate evidence if near release:
[PRODUCT_CODE_ROOT]/gates/ as applicable
- Pack note: Prior deep playbooks are not shipped here; use current
org_engineering/agents/ specs + this skill.
Checklist
- Contracts — request/response shapes; version or migrate consumers explicitly
- SQLite — migrations safe; no silent data loss; transactional boundaries
- Qdrant — collection/index consistency with ingest path
- Auth and entitlements — align with current security model; escalate unknowns via
security-compliance-evidence
- Tests for new behavior — unit/integration per project norms
Stop conditions
- Breaking API without consumer update list → stop until documented + callers updated
- RAG or ingest changes → consider
data-and-ingest overlap
Cursor
Subagents may trace call paths; Mike owns cross-cutting contract truth at release boundaries.