omos-apply
Apply an OpenSpec change via $oh-my-openspec:omos-apply — implement task groups in parallel waves, verify scenarios, review the diff. Never commits. Invoke via $oh-my-openspec:omos-apply.
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-14
- Stars
- ★ 1.6k
- Forks
- 491
01 前言 Front Matter
- name
- omos-apply
- description
- Apply an OpenSpec change via $oh-my-openspec:omos-apply — implement task groups in parallel waves, verify scenarios, review the diff. Never commits. Invoke via $oh-my-openspec:omos-apply.
03 SKILL.md 正文
Codex host adaptation (generated from skills/omos-apply/SKILL.md — source of truth stays there):
- Dispatch roles with
spawn_agent/send_input/wait_agent/close_agent. Subagents are asynchronous (default up to 6 concurrent threads), so a wave is one batch ofspawn_agentcalls followed bywait_agentcollection — never poll.openspec_validateis provided by this plugin's bundled MCP server asmcp__openspec__openspec_validate— call it withcwdset to your session's project directory (thechangefilter optional); the VALID/INVALID/UNAVAILABLE/ERROR one-look report format is identical to OpenCode.- This skill is invoked as a
$oh-my-openspec:omos-applymention (or picked from /skills). There is no argument substitution: arguments arrive as plain text in the user's message after the mention — read them from there; when absent, follow this skill's elicitation steps.- Roles run from
~/.codex/agents/omos-*.toml. Ifspawn_agentreports an unknown agent, stop and tell the user to run$oh-my-openspec:omos-setuponce.
omos-apply
Implement openspec/changes/<change-id>/ through dependency-ordered parallel
subagent waves with verification and review. The OpenSpec artifacts are the
contract. You never run git write commands — the user reviews and commits.
Flow
1. Select the change
Change: <id>given → use it.- Otherwise run
openspec list --json(or readopenspec/changes/). Exactly one active change → confirm it. Several → ask, one per run. None → tell the user to run$oh-my-openspec:omos-planand stop.
2. Mechanical gate
Run openspec_validate with the change id.
UNAVAILABLE→ offer to install the CLI now (npm install -g @fission-ai/openspec, orbrew install openspecon macOS; explicit yes required). Declined → stop — unlike plan, apply cannot verify without the gate.- Not VALID → stop, report the numbered violations, suggest a
$oh-my-openspec:omos-planfix round. Do not proceed.
3. Wave plan
Dispatch omos-planner with MODE: waves over tasks.md + design.md.
It returns ordered waves of task groups (groups run in parallel within a
wave; overlapping files serialize groups into later waves; conservative
choices on uncertainty). Each wave-table row lists its groups' exact file
paths, and the planner's MODE: waves rules are the source of truth for
how waves are formed. Record the wave table in the session before
dispatching.
4. Execute waves
For each wave, in order:
- Dispatch one
omos-implementerper group in the wave, all in a single parallel batch. On Codex the batch is one set ofspawn_agentcalls that return immediately — collect each report withwait_agent, relay follow-ups withsend_input, and release threads withclose_agent; never poll. - Each implementer prompt carries verbatim: the group's tasks, the spec requirement/scenario sections they implement, design.md decisions touching the group, and the full wave table, including each group's assigned files.
- Implementers tick their own
- [ ]→- [x]intasks.md. - A user request arriving mid-wave is first checked against the wave table —
the single source of execution order (Guardrails) — and the remaining
tasks.mditems; a covering task is cited, never duplicated by a new dispatch.
5. Blockage and conflict
An implementer BLOCKED: answer stops the run's dispatch loop for the
affected wave:
file conflict→ re-dispatch the blocked group alone in a follow-up mini-wave after its conflicting sibling completes.- Guardrail or plan defect → halt and ask the user (irreversible action,
security change, external side effect, broken plan are always user
decisions). Never lower the bar to get green. Exception: a
prompt-truncation
BLOCKED:is the orchestrator's defect, not the plan's — re-dispatch the group with a numbered edit list of ≤150 lines referencingfile:line, not inlined spec or transcript text.
6. Verify
Before §7 Review, the orchestrator's ordering gate: every manual/eyeball
acceptance group in tasks.md is executed with the user and its
confirmation recorded — no change enters Review with any such group
unticked. DEFERRED: is inadmissible for tasks in those groups — they end
ticked or the run halts. This gate is ordering only; the verifier's
tasks.md consistency check stays a separate mechanical audit.
After the final wave: dispatch one omos-verifier per capability spec
file in parallel. Each runs the mechanical gate, executes every scenario's
WHEN/THEN, and checks tasks.md consistency.
- Any FAIL → one fix round: dispatch
omos-implementerper failing capability with the exact scenario lines, then re-run only the failed verifiers. - Rejected: verifier reports that repeat the original claim with a weakened bar (skipped test, widened assertion) → treat as FAIL, do not re-dispatch the same implementer unchanged.
- Relay every implementer
DEFERRED:line (DEFERRED: <task-id> — <reason> — <user action>) verbatim to the user before §7 Review starts; a deferral naming a task in a manual/eyeball group halts at the gate above instead of being relayed. - After the final wave, before §7 Review, the orchestrator (or a designated dispatch) performs the post-final-wave full check suite run once and cites its output in the reviewer payload; implementer-scoped runs do not replace it.
7. Review
Dispatch omos-reviewer over the cumulative diff (git diff --stat +
full diff) with a REVIEW FOCUS: block: the riskiest hunks from the wave
table, verifier notes, and the verbatim Choices: report lines of every
wave implementer (including Choices: none).
CHANGES-REQUESTED→ fix round (implementer), then scoped re-review: only the open findings, answeredADDRESSED/NOT-ADDRESSED.- On
CHANGES-REQUESTED, before dispatching the re-review, run the repo's own markdown/lint check over everyopenspec/artifact the fix round touched, when the repo has one, and paste its output into the re-review dispatch. - BLOCKING findings left at the user's explicit choice only, recorded as
ruling:lines.
8. Done
Final report:
- Groups completed per wave with evidence one-liners.
choice:entries — every implementerChoices:decision worth the user's eye, one line each (noneif empty).ruling:entries — user-approved deviations, verbatim.DEFERRED:entries — verbatim, one line each (DEFERRED: <task-id> — <reason> — <user action>).- Verification summary: scenarios PASS count / total, gate VALID;
PASS (composited)lines count as passes. NO-REGRESSION-TEST:entries — every verifier line relayed verbatim, one line each.git diff --statof the working tree.- Next steps for the user, in their hands: review the diff, commit, then
archive with
$oh-my-openspec:omos-archive <change-id>. Offered invocations are the plugin's$oh-my-openspec:omos-*skill mentions whenever one exists for the action; the upstreamopenspecCLI is offered only where the plugin has no equivalent. - Branching questions are answered by citing the repo's
CONTRIBUTING.mdbranch-naming convention, e.g.feat/<topic>— branch creation, renaming, and commits stay the user's; the flow performs no git writes.
Guardrails
- Implementation is bounded by the spec delta: any needed change outside it is a plan defect → stop and ask, do not sneak it in.
- Never commit, push, or stage; never run
openspec archive— archiving is a deliberate user act after review. - The wave table is the single source of execution order for this run.
04 同仓库更多 Skills
worktable-review-with-annotations
Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.
worktable-find-and-synthesize-context
Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.
worktable-create-or-update-docs
Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.
worktable-create-or-manage-records
Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.
worktable-create-or-manage-interactive-html
Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.
worktable-collaborate-threads
Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.