Marketplace for trusted AI agent skills

Skill Detail

Run Spec-Driven Agent Changes With OSpec

Use OSpec to turn a coding request into a repo-persisted spec workflow with initialization, change advancement, verification evidence, and archival.

Templates & WorkflowsMulti-Framework
Templates & Workflows Multi-Framework Security Reviewed
⭐ 524 GitHub stars ⬇ 4.6k/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill run-spec-driven-agent-changes-with-ospec Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
View source Documentation
At a glance
Tools required
Node.js 18+, npm, @clawplays/ospec-cli, and a compatible agent runtime such as Claude Code, Codex, Gemini, OpenCode, or a shell-based CLI agent
Install & setup
Install with npm install -g @clawplays/ospec-cli, verify with ospec –help, initialize a repository with ospec init . or the /ospec initialize this project skill-mode prompt, then create, advance, verify, and archive individual changes.
Author
clawplays
Publisher
Organization
Last updated
Jul 21, 2026
Quick brief

OSpec is a spec-driven workflow for coding agents. The operator installs @clawplays/ospec-cli, initializes OSpec in a project, asks Claude Code, Codex, Gemini, OpenCode, or a plain CLI agent to create and advance a change, then keeps the goal, plan, verification evidence, and accepted archive in the repository.

How it works

What this skill actually does

Use this instead of normal conversational coding when a request needs durable requirements, repeatable verification, a resumable trail across sessions, or a clear handoff between human review and agent execution. It fits feature changes, bug fixes, documentation updates, and refactors where just editing the files would leave too little evidence.

The scope boundary is the OSpec goal/change lifecycle and its repository artifacts. It is not a generic coding-agent framework listing, and it is not another broad spec-driven product card. The approved use is invoking OSpec to manage one verifiable project change from initialization through archival, with repository evidence that another operator can inspect later.