GraphCanon updated 4w · GitHub synced 4w
Decision brief
ospec, a spec-driven workflow framework for AI coding agents, employs iterative cycles of plans, actions, verification with evidence logged in the repository.
Good fit when
- Use ospec when you prefer an agentic method that aligns well with JavaScript environments and want to ensure that your goals are verifiable through clear specifications and evidence.
- Select ospec if you are working extensively with Claude Code, Codex, Gemini, OpenCode, or other coding agents and require a structured workflow engine that supports these integrations.
Avoid when
- Avoid using ospec if your project requires integration with non-JavaScript languages or frameworks that are not compatible with its spec-driven development model.
- If real-time feedback loops are critical to the success of your AI coding agent, and you need more instantaneous verification processes than what ospec's structured iterations can provide.
Observed Jul 15, 2026 · Source: enrich:decision_facts
Verify the decision
Adoption
Package downloads where a registry match exists. GitHub stars (524) are secondary evidence.
- npm downloads (30d)
- 5,207·npm downloads API·4w
Maintenance and security
Full trust report- Maintenance
- Very active (3d since push)
- As of 4w
- Provenance
- Not a fork · Personal account
- As of 4w
- Security (OSV)
- No MCP manifest
- As of 1mo
Public GitHub metadata and optional OSV scans. Signals, not a guarantee. Trust methodology.
Install
npm install ospecSimilar tools
Same-category neighbours. No typed graph edges are catalogued for this tool yet.
Evidence and technical details
Sourced facts, taxonomy, compatibility claims, README excerpt, and machine-readable endpoints.
Overview
ospec provides an agentic and spec-driven method to manage and verify goals through iterative cycles of plans, actions, verification with evidence tracked in the repository.
Capability facts
- CLI
- CLI entrypoint
Source: package.json:bin|scripts · Jul 27, 2026
- MCP server
- No MCP server detected
Source: repo_scan · Jul 27, 2026
- Languages
- javascript, typescript
Source: github.language+package.json · Jul 27, 2026
Categories
Compatibility
Sourced claims from the README excerpt - not unsourced marketing copy.
Source: README excerpt (regex_v1, Jul 27, 2026)
npm install -g @clawplays/ospec-cliSource link
Tags
README
Install With npm
npm install -g @clawplays/ospec-cli
Official package: @clawplays/ospec-cli
Command: ospec
Verify install: ospec --help
Quick Start
OSpec only takes 3 steps:
- initialize OSpec in your project directory
- create and advance one change for a requirement, document update, or bug fix
- archive the accepted change after deployment and validation are complete
Plugin Installation
OSpec supports plugins for UI review and runtime validation. Keep the public flow simple:
/ospec open Stitch for this project.
/ospec open Checkpoint for this project.
In AI / /ospec flows, requests like "open Stitch" or "open Checkpoint" should be handled as: check whether the plugin is already installed globally, install only when missing, then enable it in the current project.
Command line fallback:
ospec plugins list
ospec plugins install stitch
ospec plugins enable stitch .
ospec plugins install checkpoint
ospec plugins enable checkpoint . --base-url http://127.0.0.1:3000
Official npm plugin packages:
@clawplays/ospec-plugin-stitch@clawplays/ospec-plugin-checkpoint
After a plugin is enabled, its detailed setup docs are synced into .ospec/plugins/<plugin>/docs/.
Maintainers can find plugin publishing and automation details in docs/plugin-release.md.
License
This project is licensed under the MIT License.
For agents
This page has a .md twin and JSON over the API.