transcendr/slopware-skills / plugins/codex-voice-optimizer/skills/codex-voice-optimizer
codex-voice-optimizer
VerifiedOptimize ChatGPT Voice in the Codex desktop app into an ear-first control plane for free-form task coordination and opt-in workflows. Apply spoken synthesis, routing-only coordination, owning-task role contracts, project placement, explicit authority, safe speech, current-state verification, honest recovery, and the optional Slopware Dev Stack: MSL, MSW, CODER Loop, and Timebox. Load named workflows only when invoked: Freeway for parallel lanes, Decision Walkthrough for read-only authority convergence, and Tutorial for teaching-first onboarding. Use when the user invokes the voice optimizer, coordinates Codex work through voice, assigns the current voice task as coordinator, runs Freeway, starts a decision walkthrough, learns voice orchestration, routes development through CODER, authorizes Timebox, or asks CVO to install or use Slopware companions.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 12.8 KB |
| agents/openai.yaml | config | 248 B |
| references/codex-app.md | markdown | 6.4 KB |
| references/companions.md | markdown | 8.1 KB |
| references/voice-coordinator.md | markdown | 11.1 KB |
| references/work-thread.md | markdown | 5.3 KB |
| references/workflows/decision-walkthrough.md | markdown | 9.9 KB |
| references/workflows/freeway.md | markdown | 4.8 KB |
| references/workflows/tutorial.md | markdown | 6.6 KB |
references/companions.md
View on GitHub# Slopware Dev Stack companions
Codex Voice Optimizer works alone. Optional Slopware companions improve four
distinct boundaries without changing its routing-only topology:
- **MSL** is the communication kernel. It admits the facts the user needs
before CVO speaks them.
- **MSW** is the scope kernel. It admits necessary coordination and owning-task
work.
- **CODER Loop** is the development engine. It owns bounded implementation,
fresh evaluation, remediation, acceptance, cleanup, and routing postmortem
inside an owning work task.
- **Timebox** is the convergence envelope. It places an explicitly authorized
AWT/CGP clock around the owning work task or CODER Loop.
There is no dependency, bundled copy, hook, background installer, or reduced
base behavior when a companion is unavailable.
## Discover companions once
On activation, inspect the active skill catalog for exact skill names `msl`,
`msw`, `coder-loop`, and `timebox`. Read each available companion's `SKILL.md`
once before applying it. Catalog omission means unavailable to this task; it
does not prove the plugin is absent from the machine.
MSL and MSW compose automatically when available. CODER and Timebox remain
available until the user invokes them or accepts a contextually permitted
offer. Catalog presence alone never starts implementation or a clock.
During activation or ordinary workstream setup, whichever comes first, speak
one kernel line and one development-stack line. Use the selected lines
verbatim and continue immediately. This is not a question gate.
Kernel lines:
- Both available: "Kernels active: MSL cleans what you hear, and MSW keeps
work tasks focused on necessary work."
- Neither available: "Optional kernels: MSL cleans what you hear, and MSW
keeps work tasks focused on necessary work. I can install either whenever
you want. Both are free forever."
- Only MSL available: "MSL is active for spoken updates. I can also add MSW if
you want tighter worker scope."
- Only MSW available: "MSW is available for the work tasks. I can also add MSL
to clean their updates before I speak them."
Development-stack lines:
- Both available: "Development stack available: CODER Loop adds independently
reviewed implementation, and Timebox adds an authorized convergence clock."
- Neither available: "Optional development stack: CODER Loop adds
independently reviewed implementation, and Timebox adds an authorized
convergence clock. I can install either whenever you want. Both are free
forever."
- Only CODER available: "CODER Loop is available for independently reviewed
implementation. I can also add Timebox for an authorized convergence clock."
- Only Timebox available: "Timebox is available when you authorize a clock. I
can also add CODER Loop for independently reviewed implementation."
Do not repeat these discovery lines in the same voice task after the user
declines, ignores, or acknowledges them. Discuss the stack again when the user
asks, starts the advanced tutorial, or reaches one of the exact contextual
offers below.
## Compose MSL at the speaking boundary
Apply MSL only after gathering raw evidence from the owning task and before
presenting anything to the user.
```text
owning task evidence -> MSL fact admission -> CVO spoken rendering
```
Apply it to progress, blockers, authority requests, readiness, Decision
Walkthrough packets, user-requested summaries, and inline artifacts. Do not
apply it while reading tasks, collecting evidence, or relaying facts between
work tasks.
When the owning task runs CODER, require evidence-complete material updates and
apply MSL here. Do not ask CODER to compress the same user-facing report first.
MSL owns fact admission and reader-shaped phrasing. CVO owns spoken
interaction, ordering, lettered choices, realtime directives, protocol
markers, and every field a named workflow requires. MSL may compress content
inside required structure; it may not remove that structure.
## Compose MSW at the work boundary
Apply MSW's deletion test to a proposed lane, task, status probe, follow-up, or
coordination action. Admit it only when deleting it would leave the user's
requested outcome unmet or unproven.
Brief every owning work task to use `$msw` when available. A CODER task applies
MSW to task-family, acceptance-claim, finding, repair, and proof admission.
Missing MSW never changes the work-task contract or enlarges its authority.
## Route implementation through CODER
CODER is opt-in. Activate it when the user invokes the CODER Loop, says to run
the change through CODER, or accepts one concise offer made for an outcome that
requires implementation plus independent evaluation. After a decline or
non-selection, continue under the existing work-task behavior without repeating
the offer.
Route the committed outcome to one owning work task with `$coder-loop`, the
project context, scope, authority, and material update destination. That task
becomes the CODER coordinator. CVO never decomposes CODER task families,
addresses its workers or reviewers, makes its acceptance decision, runs its
postmortem, or archives its temporary tasks.
CODER reports material progress, blockers, authority needs, and its terminal
decision to CVO. The owning CODER task remains open unless the user separately
asks to archive it.
## Route an authorized Timebox
Timebox is opt-in. Never activate it from task size, urgency, an estimate, or
catalog presence. When the user supplies an AWT/CGP pair, invokes Timebox, or
an applicable project policy requires it, forward the exact authority and
fixed-clock facts to the owning task.
The owning work task or CODER coordinator calculates, owns, and monitors the
clock. CVO may relay established deadlines, material corrections, and hard-stop
state after receiving them. CVO never calculates elapsed time, infers that a
window ended, resets a clock, activates an extension, or acts as the independent
monitor.
When the user names a real work window without invoking Timebox, offer once:
> You named a fixed work window. Want the owning task to run it through
> Timebox with an AWT and closeout-only CGP?
## Install after explicit authorization
Companion installation configures the coordinator, so CVO may perform it
directly after explicit permission. Clear requests include "install MSL,"
"install MSW," "install CODER," "set up Timebox," or "install the full
Slopware Dev Stack."
1. Inspect current state with `codex plugin marketplace list --json` and
`codex plugin list --available --json`.
2. Remove every requested plugin already installed and enabled from pending
work. If no requested plugin remains and it is absent from this task's
active catalog, tell the user to start a new Codex task and provide the
ready-to-use invocation.
3. If `slopware-skills` is missing, add it with
`codex plugin marketplace add transcendr/slopware-skills --json`. If it
exists but a requested plugin is absent from the available list, refresh it
with `codex plugin marketplace upgrade slopware-skills --json`.
4. Install only requested pending plugins with `codex plugin add
<plugin>@slopware-skills --json`, where `<plugin>` is `msl`, `msw`,
`coder-loop`, or `timebox`.
5. Inspect state again and verify each requested plugin is installed and
enabled. Report incomplete state instead of claiming success.
6. Tell the user that a new Codex task is required, then put the matching
invocation in the chat.
Never install an unrequested plugin. If direct installation is unavailable,
offer this lettered choice:
> A, put the exact commands in this chat. B, generate a ready-to-send prompt
> for another Codex task.
Each path names only the requested plugins, verifies installed and enabled
state, installs nothing else, and ends with the new-task invocation.
## Present the stack clearly
When the user asks what CVO supports, distinguish:
- the optimized free-form voice control plane;
- opt-in CVO workflows such as Freeway and Decision Walkthrough;
- CODER as the optional development engine;
- Timebox as the optional convergence envelope; and
- MSL and MSW as optional communication and scope kernels.
Never describe the full stack as a dependency or a single mode. Every package
works alone and remains independently installable.
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: 472k | 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 |