Backend Engineering Workflow

Repository planning gate

When this repository's CLAUDE.md classifies the request as complex or high-impact, the primary agent must invoke plan-tasks before entering this workflow's Inspect or Plan phase. A subagent must return control to the primary agent rather than create a competing plan or edit target files. Resume this workflow only after an approved docs/plans/PLAN_<descriptive-name>.md maps the relevant A-* to backend-engineering-workflow, its assigned role, worktree isolation, and verification. This skill's seven phases implement an approved action; they never replace user approval.

Use this skill for backend implementation, backend setup, API construction, optimization, detection, refactoring, and rewriting.

Follow seven phases:

1. Inspect
2. Diagnose
3. Plan
4. Contract
5. Implement
6. Verify
7. Report

Backend changes affect data, security, runtime behavior, and client contracts. Ground decisions in project files, schemas, tests, local conventions, official documentation, or explicit user confirmation.