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/postmortem.md
View on GitHub# Review a completed CODER Loop
Use this companion reference after the CODER Loop reaches acceptance or a
genuine terminal block. The implementation and review loop owns the candidate
decision. This postmortem calibrates future routing and does not reopen
acceptance by ceremony.
## Gather belonging evidence
Use evidence already produced by the completed loop:
- the task-family contracts and original mechanical or reasoning-required
classifications;
- the actual model and reasoning assignments;
- the accepted candidate or exact terminal block;
- independent review findings and belonging evidence;
- repairs, targeted re-review, and the final acceptance decision;
- scope, authority, evidence, platform, or authoritative time constraints that
limited the result;
- comparable prior routing records already authorized by the project.
If an authoritative local-only `CODER_LEDGER.md` already exists, it may supply
the comparable records. Do not require or create that ledger. The completed
task evidence is sufficient for assessing the current loop, and persistence is
allowed only when the user or project has already authorized its destination.
## Assess every task family
For each completed family, determine:
1. Whether its original classification described the uncertainty actually
encountered.
2. Whether the assigned model and reasoning effort reached final acceptance
with complete evidence.
3. Whether independent review or remediation revealed reasoning that the
original assignment could not supply.
4. Whether scope, evidence, authority, platform capability, or an authoritative
time boundary explains the outcome better than model capability.
Do not label a model insufficient merely because the task was blocked outside
its authority or proof surface. Do not treat a lower-cost assignment as
successful unless its candidate reached final acceptance with all required
evidence.
## Form future routing
A postmortem may recommend at most one controlled mapping change. Admit that
recommendation only when comparable records repeatedly show:
- complete acceptance evidence;
- stable task scope and classification;
- no reasoning-required remediation; and
- the same lower assignment reaching final acceptance, when a lower assignment
is proposed.
One successful task never changes a default. A recommendation changes only the
next comparable assignment and retains the same independent-review standard.
It does not alter the completed decision, reduce proof, or expand authority.
If the evidence does not support a mapping change, report that no routing
change is warranted. Do not manufacture a recommendation to make the
postmortem appear productive.
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: 469k | 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: 321k | 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: 321k | 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: 321k | Updated | Claude CodeCodex | Verified | Install |