ospec
Spec-driven, agentic workflow framework for AI coding agents. Turn a request into a verifiable goal loop, plan, act, verify, with durable specs and evidence in your repo. Works with Claude Code, Codex, Gemini, OpenCode, and plain CLI.
Runs with mockssource: GitHubhomepageJavaScriptMITcommit be449f2ce698
JavaScript, MIT licensed. The project labels itself: agentic ai, agentic coding, ai, ai agents, ai coding assistant, ai workflow, claude code and cli.
ospec runs, with stand-ins for the services it depends on. An Argusic agent installed it in 4 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install completed without errors (Node 18 engine warnings only); ospec CLI v2.1.0 responds to --version, --help, init, status, change, session commands; release smoke test and content scan both pass; index rebuild tool works; global install via --prefix succeeds.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 86 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- vitest 4.x requires Node 20+ but environment has Node 18.19.1; rolldown uses 'styleText' from 'node:util' not available in Node 18
- npm link fails with EACCES: permission denied to /usr/local/lib/node_modules/@clawplays
- Install time
- 4 minutes
- Cold machine to finish
- 5 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- node dist/cli.js --version returned 'OSpec CLI v2.1.0'; node scripts/release-smoke.js completed with 'all checks passed'; ospec init, status, change, and session commands all return valid output on a temp directory; npm install -g . --prefix installed the ospec command; release-content-scan.js passed
- Model tokens used
- 56,714
- Exact commit tested
- be449f2ce698
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
The result has been printed. Let me summarize the work done for you. ## Summary **OSpec CLI v2.1.0** — a spec-driven development (SDD) framework for AI coding agents. ### What I did 1. **Read the README & docs** — Identified it as a Node.js CLI package published as `@clawplays/osp… 2. **Installed dependencies** — `npm install` resolved all 7 packages (2 prod: `js-yaml`, `semver`;… 3. **Verified the CLI** — `node dist/cli.js --version` → `OSpec CLI v2.1.0`. `--help` shows all com… 4. **Ran the release smoke test** — `node scripts/release-smoke.js` → `all checks passed`. This exe… 5. **Ran release content scan** — `node scripts/release-content-scan.js` → `scanned 324 publication… 6. **Built the SKILL index** — `node dist/tools/build-index.js` → rebuilt successfully. 7. **Tried vitest** — Fails because Node 18 lacks `styleText` in `node:util`, required by rolldown/… 8. **Global install** — `npm link` fails (EACCES); `npm install -g . --prefix ~/.npm-global` succee…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Installed in 4 minutes, faster than the median of the 7 comparable projects Argusic has measured.
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
Of the 8 agentic-ai projects Argusic has installed and timed, ospec was the 3rd fastest to reach a running state, and 5 of 8 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs with mocks | 92.00 | 0.03 | |
| Argusic Runner | 1/3 | Unverified | 80.00 | 0.03 |
Topics (from GitHub)
agentic-aiagentic-codingaiai-agentsai-coding-assistantai-workflowclaude-codeclicodexcoding-agentdeveloper-toolsllmloop-engineeringmcpmodel-context-protocolprompt-engineeringsddspec-driven-development
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/ospec)Questions
- Does ospec run?
- ospec runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 4 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test ospec?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit be449f2ce698. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test ospec?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does ospec take to install?
- 4 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does ospec need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing ospec?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does ospec compare with the alternatives?
- Of the 8 agentic-ai projects Argusic has installed and timed, ospec was the 3rd fastest to reach a running state, and 5 of 8 reached one at all.
- Where is the evidence for ospec?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.