← ClaudeAtlas

coder-looplisted

Run the Codex Optimized Development, Evaluation, and Remediation (CODER) Loop with an orchestration-only coordinator, non-overlapping task-family owners, fresh independent reviewers, evidence-scoped remediation, and final coordinator acceptance. Discover and compose optional MSW, Timebox, MSL, and Codex Voice Optimizer companions as the Slopware Dev Stack without making them dependencies. Use in Codex when the user invokes the CODER Loop, asks to divide a complex change into bounded implementation families with independent reviewers, requests multi-agent implementation without overlapping ownership, requires review and repair until every blocking gap is independently rechecked, asks for the CODER tutorial or Slopware Dev Stack, or wants CODER to install or use its companions. Do not trigger for an ordinary single-agent change, a review-only request, or a non-Codex host.
transcendr/slopware-skills · ★ 35 · Code & Development · score 72
Install: claude install-skill transcendr/slopware-skills
# CODER Loop CODER stands for Codex Optimized Development, Evaluation, and Remediation. The loop uses bounded task-family review to give complex implementation clear ownership, independent evaluation, and evidence-scoped repair. It is also the development engine of the Slopware Dev Stack: CVO can control it, MSW keeps it necessary, Timebox makes an authorized run converge, and MSL makes the user-facing result clear. Every layer remains optional and independently installable. Turn a complex implementation into a small set of coherent ownership lanes, then make every candidate earn acceptance in a fresh context. Keep the parent as coordinator and final decision owner. Let workers implement, reviewers review, and only admitted acceptance gaps create repair work. ## Activate the CODER Loop Read [references/companions.md](references/companions.md) once on activation. Discover the active Slopware companion catalog, apply the available composition rules, and present the stack once without delaying work. When the user asks to learn CODER or see the Slopware Dev Stack, read [references/workflows/tutorial.md](references/workflows/tutorial.md) and teach before taking any live action. The teaching-only tutorial does not require repository, project, task, or collaboration capabilities. For bare activation without an implementation outcome, explain in one sentence that CODER uses bounded workers, fresh evaluation, and targeted remediation, then offer the tutorial, a real outcome, or