backend

Execute backend implementation tasks from plan.md and validate against API contracts.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/anhtrinh919/claude-code-sdd --skill backend-anhtrinh919
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: backend
Source: https://github.com/anhtrinh919/claude-code-sdd/tree/main/skills/backend
Command: npx skills add https://github.com/anhtrinh919/claude-code-sdd --skill backend-anhtrinh919

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Backend Implementation Skill orchestrates the backend phase of Spec-Driven Development (SDD) projects by reading requirements.md (contract), plan.md (task groups), and handover.md (frontend context). It implements the plan.md groups in order using the code-harness, then runs architectural review (Opus) and integration testing against every API contract defined in requirements.md. Trigger on: /backend, or when the backend step is reached in the build process.

Core Features & Use Cases

  • Orchestrates the backend phase by delegating tasks to the code-harness in the correct sequence.
  • Validates the backend contract against the frontend expectations via architectural review and end-to-end API integration tests.
  • Reads the latest specs directory (specs/YYYY-MM-DD-[feature]) to determine scope and acceptance criteria.

Quick Start

Point Claude Code at the latest specs/YYYY-MM-DD-[feature] directory and start the backend implementation phase.

Frequently Asked Questions about backend

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate backend implementation phases in spec-driven development?

Automate spec-driven backend implementation by reading requirements.md, plan.md, and handover.md to execute tasks sequentially using a code-harness. It validates results against API contracts and runs architectural reviews automatically.

How does integration testing work against API contracts defined in requirements?

Integration testing validates backend outputs against every API contract defined in requirements.md. After the code-harness executes plan.md tasks, the workflow runs end-to-end tests to ensure frontend and backend expectations align.

What happens if required spec files are missing for backend workflow automation?

If required inputs like requirements.md or plan.md are missing or misaligned, the backend workflow stops immediately and prompts for remediation. This prevents executing incomplete phases and ensures contract validation has the necessary context.

How do I start a backend build phase from a specs directory?

Point your environment at the latest specs/YYYY-MM-DD-[feature] directory to start the backend build phase. The workflow reads the directory to determine scope and acceptance criteria, then executes plan.md groups in order.

Can I use this for architectural review and end-to-end API validation?

Yes, this orchestrates backend architectural review and end-to-end API integration testing. After implementing plan tasks, it validates the backend contract against frontend expectations defined in handover.md.

When do I need spec-driven backend orchestration with a code-harness?

Use spec-driven backend orchestration when you need to automate sequential task execution from plan.md and validate results against API contracts. It ensures architectural review and integration testing happen automatically after implementation.