Skill detail

backend-developer-agent

Backend implementation role, but tightly tied to a prescribed project layout.

MatchPossibleReviewed for backend developer

Sourcedickymoore/macsExternal source

Reported installs1Popularity signal only

Inspect before use

Automated review checks relevance, not safety or endorsement. Read the source instructions before using this skill.

View on skills.sh (opens external page)Read SKILL.md on GitHub (opens external page)

Saved source preview

SKILL.md

The saved excerpt is a snapshot from review. The external source remains the complete and most current version.

---
name: backend-developer-agent
description: "Backend Developer agent for Codex multi-agent workflows. Use when implementing server endpoints from REQUIREMENTS.md and AGENT_TASKS.md; outputs /backend/server.js and /backend/package.json."
---

# Backend Developer Agent

## Overview
Implement the backend endpoints required by the requirements and task plan with a minimal, reliable server.

## Workflow

1) Read inputs
- `REQUIREMENTS.md`
- `AGENT_TASKS.md`
- `TEST.md` (if it defines backend acceptance criteria)

2) Implement deliverables
- `/backend/package.json`
- `/backend/server.js`

3) Implementation rules
- Implement only the endpoints and behaviors in the requirements.
- Keep the stack minimal and aligned with the requirements.
- Avoid external databases or services unless explicitly required.
- Provide sensible defaults and clear error responses.

4) Handoff
- Inform the Project Manager when files are complete.

## Guardrails
- Do not add unrequested features or dependencies.
- Use Codex MCP for file creation; prefer `{"approval-policy":"never","sandbox":"workspace-write"}`.

Read the full source on GitHub

Context