Detalle del Skill

backend-developer-agent

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

CoincidenciaPosibleRevisado para desarrolladores backend

Fuentedickymoore/macsFuente externa

Instalaciones reportadas1Solo señal de popularidad

Revisar antes de usar

La revisión automática comprueba relevancia, no seguridad ni respaldo. Lee las instrucciones de la fuente antes de usar este Skill.

Ver en skills.sh (abre una página externa)Leer SKILL.md en GitHub (abre una página externa)

Vista previa guardada

SKILL.md

Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.

---
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"}`.

Leer la fuente completa en GitHub

Contexto