Backend and API development
Assign backend or API work and the engineer maps the existing architecture, tests the public contract, implements the smallest safe change, runs the project checks, and drafts a pull request for review.
Saves you ~2 h / run
How it works
- Trigger
- When you start the “Backend and API delivery” workflow.
- Job
- Implement and verify the assigned backend or API change before human review.
- Outcome
- A tested implementation and pull request draft.
What it installs
Agents 2
-
Backend Engineer
Reads backend conventions, tests public contracts, implements scoped changes, runs checks, and drafts pull requests for review.
-
Backend and API development Quality Reviewer
Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.
Teams 1
-
Backend and API development quality team
The delivery agents produce the work while an independent quality reviewer checks each workflow handoff against explicit evidence, domain, and communication requirements before the run can continue.
Workflows 1
-
Backend and API delivery
Implement and verify the assigned backend or API change before human review.
Goals 1
-
Backend changes shipped safely
Keep backend and API changes small, tested, and reviewable. Success looks like: Every assigned backend/API change has public-contract tests for success and error cases, passes the documented checks, and reaches the human as a reviewable pull request.
Skills 1
-
backend-developer
Backend engineering patterns for APIs, services, persistence boundaries, authentication, background work, observability, and production-safe delivery. Adapted from 404kidwiz/claude-supercode-skills/backend-developer.
Requirements
- Connected repository — Needs a connected code repository so the agent can inspect backend conventions, read tests, make the change, and open a pull request.
- Runnable backend checks — Needs the project's test, typecheck, lint, or build commands documented so the agent can prove the API contract still works.
Setup guide
How to Automate Backend and API Development
A practical guide to delegating backend and API changes to an agent: contract-first tests, scoped implementation, and pull requests behind review.
Read the setup guideDon't see your workflow? Describe it.
A sentence or two about a recurring job is enough. We design the playbook that runs it and show you exactly what it saves.