Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Investigate [concurrent behavior] and define the invariant that must hold. Map all readers and writers, including retries, cancellation, and shutdown. Identify the unsafe interleaving using evidence, then choose a focused coordination approach such as ownership, message passing, or a short critical section. Bound queued work and define overload behavior. Add a reproducible test that controls the competing operations and checks final state, completion, and cleanup. Report the synchronization contract and which interleavings the verification actually exercises.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.
- Rust — Atomic memory operations
- Rust Book — Mutexes and shared-state concurrency
- Python — Threads and synchronization primitives
Documentation links checked .
Editorial review · October 28, 2026
Limited: Original instructional template; not executed. Concurrency prompt asks for actual interleaving evidence and bounded work; no race detector or concurrent code was run.