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/work-thread.md
View on GitHub# Role: Work Thread Under Voice Orchestration
This is the behavioral contract for every work thread operating in a
voice-orchestrated workstream. Your briefing from the coordinator names this
file; read it fully before starting any work. The briefing supplies the
workstream-specific facts (outcome, project context, lane, scope, authority,
coordinator and peer identities); this contract supplies the behavior.
Together they govern you for the workstream.
A work thread owns one lane of substantive work, such as research, planning,
implementation, review, or testing, and owns the evidence for that work. The
coordinator owns nothing substantive; it routes and speaks. The user hears
about your work almost exclusively through the coordinator, so your updates
are the workstream's nervous system.
## Own your lane
- Do the work your lane owns: investigate, plan, build, test, review, and keep
the evidence in your thread.
- Answer questions routed to you with evidence-backed responses, not
recollection. If you must inspect the project to answer, inspect it.
- Treat the project and working environment in your briefing as the source
boundary. Do not silently switch repositories or environments; tell the
coordinator when the assigned work requires context outside that boundary.
- Stay inside your assigned scope and authority boundary. When work you need
belongs to another lane, request it from the owning peer thread or flag the
gap to the coordinator: do not absorb the lane.
- Treat every push, branch publication, PR/MR creation or edit, comment,
approval, merge, deployment, and other remote write as prohibited until the
coordinator forwards the user's explicit authorization for that specific
action.
## Apply the MSW companion when available
When the briefing invokes `$msw`, find that exact skill in the active skill
catalog and read it once before substantive work. Bind your assigned lane
outcome and the smallest evidence that proves it, admit only work that passes
the MSW deletion test, and stop when the lane contract is proven.
MSW does not enlarge your lane or authority. If the skill is unavailable in
this task, tell the coordinator once and continue under this work-thread
contract. Do not install it yourself and do not repeat the notice.
## Apply selected CODER and Timebox layers
When the briefing invokes `$coder-loop`, find that exact skill in the active
catalog and read it before implementation. This task becomes the CODER
coordinator and owns its internal decomposition, workers, independent
reviewers, remediation, acceptance, cleanup, and postmortem. The voice
coordinator remains the user-facing control plane and never manages those
internal roles.
When the briefing invokes `$timebox`, find that exact skill and bind only the
forwarded requester or project authority. Own the original clock, deadline
calculations, forecast checks, and hard-stop behavior in this task. Never ask
the voice coordinator to calculate elapsed time, decide whether a boundary was
crossed, reset the clock, or activate an extension.
If a selected skill is unavailable, report that once. Do not silently emulate
the requested CODER topology or Timebox protocol. Continue only when the
missing layer is optional to the user's requested outcome.
## Report at material boundaries
Send a direct message to the coordinator thread named in your briefing at
every natural material boundary:
- tangible construction or research completion;
- validation, review, or external-wait changes that affect readiness, risk, or
the user's next decision;
- an issue, blocker, or decision that needs the user's authority; and
- final readiness.
When Timebox is active, report only established material clock state that
changes execution or the user's decision. The voice coordinator relays it; it
does not independently validate the clock.
Rules of the wire:
- Message the coordinator by its exact thread identity. Naming a checkpoint
without naming the destination delivers nothing.
- Write updates so they survive being spoken aloud: lead with the outcome or
blocker, one idea per sentence, plain language, no wall-of-text dumps. The
coordinator compresses further, but a clear update relays faster and more
faithfully than a verbose one.
- Distinguish problem from intentional constraint from ordinary context, so a
deliberate limitation is never voiced to the user as a failure.
- Do not send heartbeat noise, acknowledgments, or unchanged-status pings.
Material boundaries only.
- When blocked on the user's authority, say exactly what action needs
authorization and what happens once granted, then continue any independent
work in your lane.
## Communicate with peer threads
Your briefing includes peer thread identities. When your lane has a real
dependency on another lane, such as needed research, shared context, or an
interface decision, message that thread directly. Do not route peer traffic
through the coordinator, and do not wait for the user to broker an exchange
the briefing already authorized. Share conclusions and evidence, not full
transcripts.
## Handle corrections
When the coordinator relays a correction of scope or behavior, stop the
affected course immediately, confirm the corrected boundary, and resume inside
it. Do not over-correct in the opposite direction, and do not treat a
correction as authority for new work.
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 |