# Mux Ospec

> Thin package-owned alias for `ac-workflow-mux-ospec`. Uses `pimux` as the runtime-only stage orchestration control plane.

- Skill: `matiascomercio/mux-ospec-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add matiascomercio/mux-ospec-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/matiascomercio/mux-ospec-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: MatiasComercio (https://skillmd.com/u/matiascomercio)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/matiascomercio/mux-ospec-2

---


# mux-ospec

This skill is a package-owned trigger alias for `ac-workflow-mux-ospec`. It is not an independent spec-stage workflow definition.

Delegate workflow semantics to `../ac-workflow-mux-ospec/SKILL.md` and runtime semantics to `../../extensions/pimux/docs/`.

## Mandatory trigger behavior

If the user explicitly triggers `mux-ospec`, keep work in the tmux-backed stage lane.

Required sequence:
1. after spawn, do not poll pimux or use Bash sleep/wait loops; wait for delivered child bridge activity
2. pass through an explicit spec path unchanged when the user provides one; if the target is valid but missing, let the authoritative `pimux` runtime create it instead of blocking
3. if the user provides an inline prompt without a spec path, let the authoritative `pimux` runtime derive/create the next current-branch spec path by following recent current-branch spec-path patterns and the spec skill convention
4. use `AskUserQuestion` only when the user provided neither a spec path nor an inline prompt that is sufficient to spawn
5. let the authoritative `pimux` extension enforce the fail-closed parent control-plane lock
6. spawn the stage-owning `pimux` child before substantive stage work
7. after spawn, run notify-first rather than poll-first: do not call `status`, `capture`, `tree`, `list`, or `open` on the happy path
8. after a child progress report, use at most one `send_message` if input is needed, then wait again
9. use `status` / `capture` / `tree` / `list` / `open` only for explicit live inspection, suspected stall/protocol violation/failure, or the inactivity watchdog
10. after terminal settlement, do one final `pimux status` verification and then advance

Do not run spec-stage execution directly in the parent while this skill is active.
Do not use parent-side `Read`, `Bash`, or manual repo discovery to figure out the spec before spawn.
Do not poll pimux or use Bash sleep/wait loops; wait for delivered child activity, and treat `status` / `capture` / `tree` / `list` / `open` as recovery-only.