# Coordinate REST API Delivery

Building a production REST API requires aligned requirements, implementation, testing, documentation, and deployment. This skill provides a two-week TDD workflow for coordinating specialized agents.

## Install

```bash
npx skillstore add dnyoussef/sop-api-development
```

## Metadata

- Status: approved
- Slug: dnyoussef-sop-api-development
- Skillstore revision: r1
- Version status: missing
- Tree hash: cc12e3cbb93b281ada3afea8c569f1c217e16bffe21fecda7423182ddb4313fa
- Author: DNYoussef
- GitHub username: DNYoussef
- License: MIT
- Repository: https://github.com/DNYoussef/ai-chrome-extension/tree/main/.claude/skills/sop-api-development
- Ref: c579efd02184f1128d6741d16e6c8d951d7d4208
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/dnyoussef-sop-api-development
- Manifest: https://skillstore.pages.dev/api/skills/dnyoussef-sop-api-development/manifest

## Capabilities

- Defines a 14-day REST API delivery plan from requirements through launch.
- Coordinates product, architecture, database, QA, backend, documentation, and DevOps responsibilities.
- Specifies deliverables for requirements, OpenAPI specs, schemas, test plans, CI, docs, and deployment.
- Applies a TDD cycle for endpoint tests, implementation, review, and refactoring.
- Covers E2E, performance, security, staging, production, monitoring, and knowledge transfer steps.
- Lists measurable success targets for coverage, latency, uptime, throughput, and documentation.

## Use Cases

- Plan a New API Build: Turn an API idea into phased requirements, architecture, database, testing, and DevOps workstreams.
- Coordinate Backend Delivery: Guide implementation teams through TDD endpoint development, review, documentation, and release readiness.
- Prepare Launch Operations: Create staging, production, monitoring, rollback, runbook, and support handoff steps before launch.

## Prompt Templates

### Start an API Plan

```
Use this REST API SOP to plan a new API for my product. Ask for missing requirements before assigning workstreams.
```

### Create Delivery Phases

```
Apply the two-week SOP to my API project. Produce phase goals, agent responsibilities, deliverables, and review checkpoints.
```

### Run TDD Endpoint Work

```
Use the SOP to coordinate TDD delivery for these endpoints. Include tests, implementation tasks, reviews, and documentation outputs.
```

### Prepare Production Release

```
Use the deployment and validation sections to prepare staging, production rollout, monitoring, rollback, and knowledge transfer plans.
```

## Limitations

- It is a workflow template, not a generated API implementation.
- It assumes compatible agent roles and tool access are already available.
- It does not validate real infrastructure, secrets, or production permissions.
- Timeline, targets, and stack choices need adjustment for each project.

## Best Practices

- Confirm requirements, data models, and authentication rules before implementation starts.
- Write tests before endpoint implementation and keep review outputs tied to each endpoint.
- Validate staging, rollback, monitoring, and documentation before production traffic moves.

## Anti Patterns

- Starting backend implementation before API contracts and database schema are reviewed.
- Treating generated tasks as production approval without human security and operations review.
- Using default timelines or performance targets without adapting them to project constraints.

## Security Audit

- Audited at: 2026-07-05T13:15:08.176\+00:00
- Summary: Static external-command findings are false positives from Markdown JavaScript examples and template string delimiters. The blocker findings are ordinary REST API terms such as endpoint IDs, delete operations, invalid input, and OpenAPI compliance. No evidence of prompt injection, malware intent, data exfiltration, or unauthorized reconnaissance was found.

## Stats

- Views: 257
- Downloads: 8
- Favorites: 0
- Popularity score: 0