backend-change-builder

What problem does it solve?

It prevents production incidents caused by incorrect backend behavior, including broken authorization, non-idempotent retries, partial writes, and opaque failures.

Core Features & Use Cases

It guides you to design and implement backend changes with explicit validation at trust boundaries, server-side authentication/authorization (including object-level IDOR prevention), clear transaction boundaries, robust idempotency for retriable mutations, and structured error/observability patterns. Use it when you are modifying endpoint handlers, service methods, authentication/authorization logic, permission checks, transactional data mutations, or background/async jobs that must remain correct under concurrency and retries. It is also suited for agent-assisted backend fixes where you need evidence, a same-pattern scan, and a reuse-and-placement rationale before accepting changes.

Quick Start

Use backend-change-builder to produce a backend implementation and review plan for updating an endpoint that mutates data with correct validation, authorization, transactions, idempotency, error handling, observability, and concurrency safeguards.