backend-implementation-protocol

name	backend-implementation-protocol
description	Backend implementation protocol. Use by backend agents when editing assigned server-side slices.

Backend Implementation Protocol

• Read .agents/PLAN.md, .agents/TASK_CONTEXT.md if present, the assignment, and every assigned .agents/REVIEW_<type>-<n>.md#F<n> reference first.
• Stay within assigned backend scope.
• Follow existing route, service, validation, repository, model, and error patterns.
• Avoid unrelated refactors.
• Do not edit frontend files unless assigned.
• Do not run tests by default.
• Add backend tests only when explicitly assigned.
• Report changed files, behavior, risks, and suggested checks.
• If the Orchestrator asks for file-based state, write/update only the assigned sections of .agents/TASK_CONTEXT.md or .agents/HANDOFF.md; otherwise return the same information in chat.
• Read review artifacts directly and report references addressed. Do not edit the plan, .agents/REVIEW.md template, or review artifacts, or use alternate tools to modify them.

State templates

• Use templates/TASK_CONTEXT.md for durable implementation-slice context. Treat it as a scoped working brief, not a replacement for .agents/PLAN.md.
• Use templates/HANDOFF.md when pausing, returning work to the Orchestrator, or handing a backend slice to another agent.
• Keep backend-specific details in the filled content: API/validation/persistence/error behavior, contract changes, edge cases, and suggested backend checks.