oh-my-openspec

Plugin oh-my-openspec in hashgraph-online/awesome-codex-plugins. Commands read from the repo's manifest — today.

Skills (18)

• 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.

• omos-archive

  Archive completed OpenSpec changes through the vendored archive workflows, delegating to the bundled $openspec-archive-change skill ($openspec-bulk-archive-change for two or more ids). Invoke via $oh-my-openspec:omos-archive.

• omos-init

  Bootstrap baseline specs via $oh-my-openspec:omos-init — research the codebase, agree on capabilities, write openspec/specs/** describing what exists, critique and validate. Invoke via $oh-my-openspec:omos-init.

• omos-plan

  Plan an OpenSpec change via $oh-my-openspec:omos-plan — coverage interview, parallel research, adversarial grill, agent-drafted artifacts, critique loop, mechanical CLI validation. Invoke via $oh-my-openspec:omos-plan.

• omos-retro

  Retrospect a finished run via $oh-my-openspec:omos-retro — compile the evidence bundle, dispatch the retrospector, relay ≤8 cited findings. Read-only. Invoke via $oh-my-openspec:omos-retro.

• omos-setup

  Install the oh-my-openspec Codex host pieces: the seven ~/.codex/agents/omos-*.toml role agents via the bundled installer, then the openspec MCP-server approval. Invoke via $oh-my-openspec:omos-setup.

• openspec-apply-change

  Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks. Also use when the user says "openspec apply", "opsx apply", or "openspec implement".

• openspec-archive-change

  Archive a completed OpenSpec change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete. Also use when the user says "openspec archive" or "opsx archive".

• openspec-bulk-archive-change

  Archive multiple completed OpenSpec changes at once. Use when archiving several parallel changes. Also use for a plural archive request - "openspec bulk-archive", "opsx bulk-archive", "openspec archive all", or "openspec archive these changes".

• openspec-continue-change

  Continue working on an OpenSpec change by creating the next artifact. Use when the user wants to progress their change, create the next artifact, or continue their workflow. Also use when the user says "openspec continue" or "opsx continue".

• openspec-explore

  Enter OpenSpec explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements in a project that uses OpenSpec. Use when the user wants to think through something before or during an OpenSpec change. Also use when the user says "openspec explore" or "opsx e

• openspec-ff-change

  Fast-forward through OpenSpec artifact creation. Use when the user wants to quickly create all artifacts needed for implementation without stepping through each one individually. Also use when the user says "openspec ff" or "opsx ff".

• openspec-new-change

  Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach. Also use when the user says "openspec new change" or "opsx new".

• openspec-onboard

  Guided onboarding for OpenSpec - walk through a complete workflow cycle with narration and real codebase work. Also use when the user says "openspec onboard" or "opsx onboard".

• openspec-propose

  Propose a new OpenSpec change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation. Also use when the user says "openspec propose" or "opsx propose".

• openspec-sync-specs

  Sync delta specs from an OpenSpec change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change. Also use when the user says "openspec sync" or "opsx sync".

• openspec-update-change

  Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Also use when the user says "openspec update change" or "opsx upd

• openspec-verify-change

  Verify implementation matches OpenSpec change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving. Also use when the user says "openspec verify" or "opsx verify".

MCP servers (1)

• openspec

  runs: node ./assets/mcp-server.mjs

Similar plugins