$git clone https://github.com/clawplays/ospecThe official OSpec CLI package is @clawplays/ospec-cli, and the official command is ospec. OSpec is a spec-driven, agentic workflow framework for AI coding agents — it brings spec-driven development (SDD) and Loop Engineering (a verifiable plan → act → verify goal loop) to Cl
| 1 | <h1><a href="https://ospec.ai/" target="_blank" rel="noopener noreferrer">OSpec.ai</a></h1> |
| 2 | |
| 3 | <p align="center"> |
| 4 | <a href="https://www.npmjs.com/package/@clawplays/ospec-cli"><img src="https://img.shields.io/npm/v/%40clawplays%2Fospec-cli?style=for-the-badge&logo=npm&label=npm" alt="npm"></a> |
| 5 | <a href="https://www.npmjs.com/package/@clawplays/ospec-cli"><img src="https://img.shields.io/npm/dm/%40clawplays%2Fospec-cli?style=for-the-badge&logo=npm&label=downloads&cacheSeconds=300" alt="npm downloads"></a> |
| 6 | <a href="https://github.com/clawplays/ospec/stargazers"><img src="https://img.shields.io/github/stars/clawplays/ospec?style=for-the-badge&logo=github" alt="GitHub stars"></a> |
| 7 | <a href="LICENSE"><img src="https://img.shields.io/github/license/clawplays/ospec?style=for-the-badge&color=green" alt="License"></a> |
| 8 | </p> |
| 9 | |
| 10 | <p align="center"> |
| 11 | <img src="https://img.shields.io/badge/Node.js-18%2B-339933?style=flat-square&logo=node.js&logoColor=white" alt="Node.js 18+"> |
| 12 | <img src="https://img.shields.io/badge/npm-8%2B-CB3837?style=flat-square&logo=npm&logoColor=white" alt="npm 8+"> |
| 13 | <img src="https://img.shields.io/badge/language-TypeScript-3178C6?style=flat-square&logo=typescript&logoColor=white" alt="TypeScript"> |
| 14 | <img src="https://img.shields.io/badge/workflow-3_steps-0F766E?style=flat-square" alt="3-step workflow"> |
| 15 | </p> |
| 16 | |
| 17 | <p align="center"> |
| 18 | <strong>English</strong> | |
| 19 | <a href="docs/README.zh-CN.md">中文</a> | |
| 20 | <a href="docs/README.ja.md">日本語</a> | |
| 21 | <a href="docs/README.ar.md">العربية</a> |
| 22 | </p> |
| 23 | |
| 24 | The official OSpec CLI package is `@clawplays/ospec-cli`, and the official command is `ospec`. OSpec is a spec-driven, agentic workflow framework for AI coding agents — it brings spec-driven development (SDD) and Loop Engineering (a verifiable plan → act → verify goal loop) to Claude Code, Codex, Gemini, OpenCode, MCP-based agents, and plain CLI workflows. |
| 25 | |
| 26 | <p align="center"> |
| 27 | <a href="docs/prompt-guide.md">Prompt Guide</a> | |
| 28 | <a href="docs/usage.md">Usage</a> | |
| 29 | <a href="docs/project-overview.md">Overview</a> | |
| 30 | <a href="docs/installation.md">Installation</a> | |
| 31 | <a href="docs/external-plugins.md">External Plugins</a> | |
| 32 | <a href="docs/plugin-release.md">Plugin Release</a> | |
| 33 | <a href="https://github.com/clawplays/ospec/issues">Issues</a> |
| 34 | </p> |
| 35 | |
| 36 | ## Why OSpec? |
| 37 | |
| 38 | AI coding assistants are powerful, but requirements that live only in chat history are hard to inspect, review, and close out cleanly. OSpec adds a lightweight workflow layer so the repository can hold the change context before code is written and after the work ships. |
| 39 | |
| 40 | - **Spec-driven work, saved to your repo** — OSpec turns a request into files (proposal, design, plan, tasks, reviews, verification evidence) that live in your repo instead of in chat history, so any assistant (Codex/GPT, Claude Code, Gemini, OpenCode, or plain CLI) can pick up exactly where the last one stopped. |
| 41 | - **`ospec change` — the everyday fast flow** — one requirement becomes one active change on a short `init -> change -> verify/finalize` path, kept lightweight and easy to review. |
| 42 | - **`ospec goal` for larger or riskier work** — describe the result you need; the AI asks important questions, writes an inspectable plan, implements the work, runs tests, requests an independent review, updates project docs, and continues until the result is proven. |
| 43 | - **One predictable Goal workflow** — every Goal uses the same fast quality path, pauses for material user decisions, and saves progress in the repository so a later session can resume it. |
| 44 | |
| 45 | ## Install With npm |
| 46 | |
| 47 | ```bash |
| 48 | npm install -g @clawplays/ospec-cli |
| 49 | ``` |
| 50 | |
| 51 | Official package: `@clawplays/ospec-cli` |
| 52 | Command: `ospec` |
| 53 | Verify install: `ospec --help` |
| 54 | |
| 55 | ## Quick Start |
| 56 | |
| 57 | OSpec only takes 3 steps: |
| 58 | |
| 59 | 1. initialize OSpec in your project directory |
| 60 | 2. create and advance one change for a requirement, document update, or bug fix |
| 61 | 3. archive the accepted change after deployment and validation are complete |
| 62 | |
| 63 | ### 1. Initialize OSpec In Your Project Directory |
| 64 | |
| 65 | Recommended prompt: |