Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Investigate why [record] fails to synchronize. Reproduction and current evidence: [steps, local state, sanitized errors, and connectivity changes].
Trace the record's stable identifier, local version, pending operation, submission, server result, acknowledgement, and reconciliation. Separate connectivity failure from authentication, validation, conflict, or missing durable work. Check whether the operation completed remotely even if its response was lost.
Test the most useful diagnostic before applying a correction. Verify the original scenario plus an app restart and repeated delivery. Report how the fix preserves user data and avoids duplicate effects, with concrete checks and remaining environment constraints.Make this prompt yours
Replace bracketed fields with your goal, current behavior, and relevant evidence. Keep requirements that affect the task. Check the result against the acceptance criteria you supplied.
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Documentation links checked .
Editorial review · October 28, 2026
Supported: Original, unexecuted failure-review template. The documented conflict/repository boundaries support its checks; proposed repair behavior still needs application-specific evidence.