Install OSpec with npm
Use the official package before anything else.
npm install -g @clawplays/ospec-cli- Use @clawplays/ospec-cli
- The supported command is ospec
Docs
Use OSpec in 4 clear steps
Install first, initialize the project in AI chat, start one clear change, then archive it after testing or deployment succeeds.
Initialize the project in AI chat
Open AI chat in the project directory and use $ospec to initialize the repository.
$ospec initialize this project.- Run this in the project directory
- Finish initialization before you start a change
Use $ospec-change to start delivery work
When you want to build a feature, fix a bug, or update docs, start one explicit change in AI chat.
$ospec-change work on this requirement- Keep one requirement in one change
- Use this for features, bug fixes, and documentation updates
Archive the accepted change
After testing passes or deployment succeeds, archive the accepted change with $ospec.
$ospec archive- Do this after testing or deployment succeeds
- Archive only after the change is accepted
Built-in Plugins
After the core 4-step flow, use these plugins when a change needs UI review or runtime validation.
Stitch
Use Stitch for page design review and preview collaboration, especially for landing pages, marketing pages, and UI-heavy changes. Codex/Gemini is the provider used to connect AI to Stitch so it can generate, edit, and review screens in the plugin workflow.
$ospec open the Stitch plugin for me and use Codex/Gemini to connectCheckpoint
Use Checkpoint for app flow validation and automated checks, especially for submission flows, critical paths, and pre-acceptance runtime verification. When Stitch is also enabled, Checkpoint can reuse Stitch exports for page checks.
$ospec open the Checkpoint plugin for me