OSpec CLI
A CLI for spec-driven development: the agent carries a task through files in the repository from plan to verification and archive
- 390 ★ on the repository
- Last commit
- MIT
Broad access
Why this level
- Global installation updates agent skills; initialization and updates change project documents and settings
- The command with the --apply flag appends hooks to .claude/settings.json and changes Claude Code behavior
- In goal mode the agent launches subagents in batches and runs verification commands, including the project's tests
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/ospecDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Global installation updates agent skills; initialization and updates change project documents and settings
- The command with the --apply flag appends hooks to .claude/settings.json and changes Claude Code behavior
- In goal mode the agent launches subagents in batches and runs verification commands, including the project's tests
This is third-party code. Review the repository files before installing.
What it does
OSpec links requirements, agent work and acceptance through repository files. For a regular change, the change command creates a proposal, task list and verification records. Another session can read these materials to recover progress without the full chat archive. The goal mode adds design, planning and multiple workers. It stores a task graph and review results, while the current agent launches workers through its client’s native capabilities. The CLI prepares a launch plan; it does not start agent processes itself. Initialization adds the .ospec directory and project documents. Claude Code hooks can be enabled separately to check workflow state before subagents launch. Verification and archiving close a change but do not by themselves prove implementation correctness.
Who it is for. For developers and teams who run tasks through Claude Code, Codex, Gemini or OpenCode and want requirements, plans and verification evidence stored in the repository.
Good fit when
- A requirement, a documentation update or a bug fix needs to travel from proposal to archive with checkable files
- A larger task needs a plan, an independent review and tests before it counts as done
- Work moves between agents or sessions and the context should live in the repository, not in a chat
- An agent entering the project needs a brief on active changes and the next safe command
- Feature documentation should point at the code so an agent reads only the section it needs
Not a fit when
- A one-line edit: the proposal.md, tasks.md, verification.md and review.md set takes longer than the edit itself
- The client cannot launch its own subagents: the full goal mode then fails dispatch with an error
- You want to work without new files in the project: init creates .skillrc and an .ospec directory with docs and state
Example request
/ospec-change create a change for this requirement and carry it through verification: fix the login timeout in the admin panelLimitations
Documentation requires Node.js 18 and npm 8 or later. A global npm installation already attempts to update Codex and Claude Code skills and remove obsolete managed entries. This happens before project initialization; a synchronization failure can leave the CLI installed without working skills.
Goal mode needs native subagent support in the client. Generated document languages are en-US, zh-CN, ja-JP and ar, with no Russian option listed. The update command refreshes project files, not the npm package version. The chosen client’s model processes source code and plans and consumes that client’s allowances.
How to disable. Remove the CLI with npm uninstall -g @clawplays/ospec-cli. The ospec, ospec-change and ospec-goal skills sit in ~/.codex/skills/ and ~/.claude/skills/, so delete those folders. In the project remove .skillrc and the .ospec directory. If you installed the Claude Code hooks, delete their entries from .claude/settings.json: the hook files themselves live in .ospec/hooks/claude/.
FAQ
How do I install OSpec for Claude Code and Codex?
Run npm install -g @clawplays/ospec-cli and check ospec --help. Then in the project run ospec init . or tell the agent "/ospec initialize this project". The installer attempts to sync skills into ~/.codex/skills/ and, when ~/.claude exists, ~/.claude/skills/. Check the result: a sync failure may not abort package installation. Explicit install: ospec skill install ospec-goal for Codex and ospec skill install-claude ospec-goal for Claude Code.
How does ospec change differ from ospec goal?
Change keeps proposal.md, tasks.md, state.json, verification.md and review.md and stays the light path however large the task. Goal adds design.md, implementation-plan.md, a task graph, worker and reviewer artifacts and verification evidence. The user makes the choice and the tool never overrides it.
How do I resume after an interrupted OSpec session?
The ospec session command writes .ospec/session-brief.md with active and queued changes and the next safe command. The ospec loop status --brief command shows goal progress, and after a confirmed session loss ospec loop recover --force releases only unfinished items.
Which agents launch subagents in goal mode?
Documentation describes native mechanisms in Codex, Claude Code, Gemini and OpenCode. Check that the required mechanism is available in your environment. Without it, the plan is not automatically executed through another agent CLI.
How do I close a change after acceptance?
First run the deploy, tests and acceptance your project uses, then run ospec verify changes/active/<name> and ospec finalize changes/active/<name>. Finalization rebuilds the indexes and moves the change to the archive. The --force-archive mode demands the exact change name and a reason and marks the archive forced and incomplete.
Discussion
No questions or reviews yet.
Related
CLI toolsSpec-driven development for coding agents: proposal, requirements, design and tasks come before any code
GitHub toolkit for spec-driven development: the specify CLI adds agent commands and skills to a project, from principles to implementation
A CLI, MCP server and skill for spec-driven development: short markdown specs, a task board and search that an agent can read.
The spxa CLI and a skill set for spec-driven development in Claude Code, Codex and Cursor, from a change proposal to the archive
Two skills for spec-driven development: /spec asks questions and saves a document to specs/, /spec-impl implements an approved spec step by step
A CLI that guides AI coding from idea to review through requirements, plan, code and checks and keeps traces in the repo.
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| OSpec (this card) | no | 390 | |
| sudocode | no | 296 | a memory and coordination layer where specs and tasks live in git |
| Goal Workflow | no | 299 | a Claude Code skill set from PRD to pull request merge, without a separate CLI |
README in short
The project uses MIT and separates active, deferred and archived changes. A session brief helps identify the next command when work resumes after a pause.