OSpec is a document-driven workflow for AI-assisted development that helps teams initialize repositories, execute explicit changes, and archive accepted delivery.

What is the recommended OSpec workflow?

Most teams only need three steps: initialize the project, create and advance one explicit change, then verify and finalize after deployment and validation.

What is the official OSpec CLI package?

Use @clawplays/ospec-cli and run the ospec command. OSpec is not OpenSpec and should not use openspec or @fission-ai/openspec.

Prompt + Docs Workflow

Build with natural language,Generate a doc-driven workflow,Ship for real.

OSpec is a document-driven workflow for AI collaboration. Talk to your AI tool in natural language, and OSpec organizes development, validation, deployment, and delivery into a clear, trackable workflow.

Open Repository Read Usage

recommended-flow.md

STEP 1Recommended prompt

Use OSpec to initialize this project.

If project context is missing, AI-assisted init should ask at most one short follow-up.

STEP 2Recommended prompt

Use OSpec to create and advance a change for this requirement.

Keep the work inside one explicit change so proposal, tasks, state, verification, and review stay inspectable.

STEP 3Recommended prompt

Use OSpec to archive this accepted change.

After deploy and validation, archive the accepted change through the standard path.

Initialize

ONE CHANGE

VERIFY

ARCHIVE COMPLETE

Why OSpec

Keep changes in the repo, not only in AI chat

Requirements, progress, and closeout stay visible in the repository so people and AI can follow the work

Align before coding

Keep proposal, tasks, verification, and review in the repo

One requirement, one change

The default path moves one requirement through one active change

Keep the flow short

Initialize once, advance the change, archive after acceptance

Use your current AI assistants

Works with Codex, Claude Code, and direct CLI workflows

Plugin Capability

Let Stitch Handle UI Design, Let Playwright Handle Testing

Bring UI generation and verification testing into the OSpec workflow

// stitch-plugin

Stitch

Preview generation and matching code

Use Stitch to generate the page preview first and produce matching code at the same time. You can review the result and the code together, then keep iterating without switching contexts.

Preview generationCode generation

Suggested promptOpen the Stitch plugin and connect it with Codex or Gemini

// checkpoint-plugin

Checkpoint

Stitch UI verification and feature testing

Use Checkpoint with Playwright to verify the Stitch UI and walk through key product flows. It helps you check visuals, interactions, and core behavior before you ship.

UI verificationFeature testing

Suggested promptOpen the Checkpoint plugin

CHANGE-READY

After project initialization you can start submitting requirements and building

npm install -g @clawplays/ospec-cli

Install it, then initialize in your project directory to start

Open Repository Read Usage