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/review-kernel.md
View on GitHub# CODER Loop review kernel
Use this kernel after a bounded worker produces a candidate and before the
coordinator accepts that task family.
```text
decision ← candidate accepted now + retained behavior now
gap ← an acceptance claim not settled by belonging evidence
while gap exists:
cause ← smallest cause whose deletion leaves gap unexplained ∨ unresolved
change ← smallest change whose deletion leaves decision unmet ∨ unproven
reconsider only claims affected by cause or change
halt ; accept or withhold
```
## Meanings
**Decision**: The exact candidate proposed for acceptance plus the behavior its
approved contract retains.
**Candidate**: Every source input that can affect the accepted result,
including new or untracked files when they belong to the change.
**Retained behavior**: An outcome still required by the approved contract. A
specified user-visible form remains a visual claim; functional or structural
evidence alone does not settle it.
**Acceptance claim**: A statement necessary to accept the decision.
**Belonging evidence**: A current observation about this candidate and retained
behavior that can settle an acceptance claim.
**Gap**: A live acceptance claim without belonging evidence.
**Cause**: An explanation admitted only when deleting it would leave the gap
unexplained or unresolved.
**Change**: A correction admitted only when deleting it would leave the
decision unmet or unproven.
**Smallest**: Sufficient for the live claim, not the most exhaustive
explanation or broadest change.
**Withhold**: Refuse acceptance because a live claim remains unsettled. Do not
treat withholding as permission to broaden investigation or remediation.
## Admit findings
Classify observations through the contract:
```text
observation → deletion test → contract impact → project priority
if deleting the observation leaves the contract met and supported:
not a finding
if deleting the observation leaves the contract unmet or unsupported:
finding
priority ← severity of the remaining contract gap
```
Treat a finding as acceptance-blocking when its gap prevents the decision from
being accepted. Map it to P0, P1, or another severity only when the project has
an authoritative priority scheme. Never inherit severity from the reviewer.
## Recheck after repair
Give the changed candidate to a fresh reviewer. Recheck every claim the repair
could affect and preserve evidence for unrelated claims when it still belongs.
Do not rerun the entire review merely to display rigor.
Halt when every live claim has belonging evidence. Withhold when one does not.
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 |