A specification-driven development framework that ensures AI agents follow a structured, iterative process from proposal to archival.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install openspec-dev-flow
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install openspec-dev-flow using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
The OpenSpec Workflow is a professional development protocol tailored for AI coding agents to ensure high-quality software delivery. It moves away from rigid waterfall phases toward a fluid, action-based lifecycle where every change is documented and agreed upon before implementation. By integrating this into Openclaw Skills, developers can maintain a clean source of truth for their codebase requirements, ensuring that AI agents understand not just the 'what', but the 'why' and 'how' behind every code change.
At its heart, the workflow emphasizes Brownfield-first development, meaning it is optimized for existing codebases. It uses delta specifications to describe incremental changes rather than rewriting entire documents, making it highly efficient for ongoing projects. Whether you are performing a complex refactoring or adding a new feature, this workflow provides the guardrails necessary for predictable AI behavior.
To activate the OpenSpec Workflow in your development environment, ensure your AI agent is equipped with the necessary filesystem permissions. You can initiate the process by requesting a task using the standard OpenSpec triggers. Use the following command structure within your agent interface:
# Trigger a new proposal for a feature
/opsx:propose add-new-feature
# Or simply tell the agent
"Follow the OpenSpec flow to implement dark mode."
The agent will automatically scaffold the openspec/ directory structure if it does not already exist.
The workflow maintains a structured taxonomy within the openspec/ root directory to ensure clarity and traceability:
| Location | Artifact | Purpose |
|---|---|---|
specs/ |
Domain Specs | The permanent source of truth for current system behavior. |
changes/ |
Active Changes | Subfolders for each active task containing proposals and task lists. |
changes/archive/ |
Historical Records | Dated folders containing artifacts from successfully completed and merged changes. |
delta specs/ |
Requirement Deltas | Specific Markdown files describing ADDED, MODIFIED, or REMOVED requirements. |
All specifications utilize RFC 2119 keywords (MUST, SHOULD, MAY) and Gherkin-style (Given/When/Then) scenarios for maximum technical clarity.
/opsx:onboard) that guides new users through a real-world implementation to learn the protocol.Loading
An AI-driven analytical tool for projecting future metric trends, evaluating KPI feasibility, and simulating hypothetical business scenarios.

A comprehensive AI-powered training module for the Indonesian Informatics Olympiad featuring a massive question bank and intelligent performance analytics.

Skill Tracker is an automated auditing tool that identifies and lists specific AI skills used during an interaction, appending a summary report to every response.

A specialized orchestration layer that records current analysis steps and transforms them into automated, recurring scheduled tasks.

A strategic guidance skill that helps developers navigate complex decisions by providing clarity, trade-off analysis, and risk framing without creating AI dependency.

A strategic tool for interpreting blockchain data to identify patterns, anomalies, and fund flows with data-backed evidence.








































