transcendr/slopware-skills / plugins/coder-loop/skills/coder-loop
coder-loop
VerifiedRun 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.4 KB |
| agents/openai.yaml | config | 310 B |
| references/codex.md | markdown | 5.1 KB |
| references/companions.md | markdown | 7.9 KB |
| references/postmortem.md | markdown | 2.6 KB |
| references/review-kernel.md | markdown | 2.6 KB |
| references/role-contracts.md | markdown | 3.5 KB |
| references/workflows/tutorial.md | markdown | 5.5 KB |
references/role-contracts.md
View on GitHub# CODER Loop role contracts
Use these contracts as prompt material. Adapt the wording to the task, but do
not omit facts the role needs to perform or prove its work.
## Coordinator
Keep the parent orchestration-only. Own the outcome, decomposition, sequencing,
candidate boundary, integration decision, acceptance decision, and final
delivery. Route every source, test, generated-output, or configuration change
needed for composition to a bounded integration owner. Do not implement a task
family, repair a conflict, or review your own implementation.
Before every dispatch, include the current repository state, relevant user
changes, exact authority, and the evidence that will prove the family. Do not
require an acknowledgment. The worker's substantive result is the response.
## Implementation worker
```text
Implement one bounded task family in the CODER Loop.
Overall outcome: [requested result]
Your task family: [coherent owned change]
Candidate boundary: [files, generated outputs, configuration, tests]
Retained behavior: [behavior that must survive]
Acceptance claims: [claims this family must settle]
Dependencies: [completed prerequisites and current evidence]
Exclusions: [adjacent work that remains out of scope]
Authority: [local edits, tests, top-level task actions, commit, and external-write boundaries]
Repository state: [branch, head, user changes to preserve]
Implement and verify only this family. Preserve unrelated user changes. Return
the exact changed candidate, diff summary, commands and observations that prove
the acceptance claims, and any claim that remains open. Do not publish or
expand scope.
```
Keep related remediation with this worker when practical so the repair retains
implementation context. Send only admitted gaps and the evidence that made them
blocking.
## Independent reviewer
Start a fresh context that did not implement the candidate. Give it raw
artifacts and acceptance criteria, not the implementer's reasoning,
recommendation, or success claim.
```text
Review this CODER Loop candidate independently and read-only.
Decision: [candidate proposed for acceptance]
Complete candidate boundary: [every relevant source input]
Retained behavior: [approved behavior that must survive]
Acceptance claims: [claims required for acceptance]
Raw artifacts: [diff, files, tests, logs, screenshots, or other evidence]
Project priority policy: [authoritative policy, or none]
Authority: read-only; do not edit, commit, publish, or delegate.
Apply the CODER Loop review kernel. Admit an observation only when deleting it
leaves an acceptance claim unmet or unsupported. For each admitted gap,
identify the claim, belonging evidence, contract impact, and the smallest
sufficient repair direction. Separate acceptance-blocking gaps from
non-blocking observations. State that no blocking gap remains only when every
live acceptance claim has belonging evidence.
```
Do not ask the reviewer to implement a fix. Do not resume the implementer as
the reviewer. Do not contaminate a re-review with the previous reviewer's
conclusion; provide the changed candidate and still-live claims.
## Coordinator acceptance
After every family clears independent review, inspect the integrated candidate
and answer only these questions:
- Do the family candidates compose without conflict?
- Does each acceptance claim have current belonging evidence?
- Did any integration change invalidate earlier evidence?
- Does the final state remain inside scope and authority?
Accept or withhold. Do not create a second ceremonial review after those
questions are settled.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |