Claude
Skills
Sign in
Back

openspec

Included with Lifetime
$97 forever

Spec-driven development (SDD) workflow for AI-assisted coding. Use this skill whenever the user wants to plan a feature before implementing it, create a spec for a change, generate a proposal + design + tasks structure, review requirements before coding, or use commands like /opsx-propose, /opsx-new, /opsx-ff, /opsx-apply, /opsx-archive, /opsx-explore, /opsx-verify, or /opsx-onboard. Also trigger when the user says "let's plan this properly", "write a spec for this", "create a proposal", "what should we build", or starts a feature discussion before any code exists. This skill installs OpenSpec slash commands into the project and teaches Claude how to execute them.

Design

What this skill does


# OpenSpec — Spec-Driven Development for Claude Code

OpenSpec adds a lightweight spec layer so you and Claude agree on *what* to
build before any code is written. Plans live in the repo alongside your code —
context that persists across sessions.

## Philosophy

```
→ fluid not rigid      — update any artifact anytime
→ iterative not waterfall — plan enough, then start building
→ brownfield-first     — works on existing codebases
→ specs in the repo    — context that survives session resets
```

---

## Directory Structure

```
openspec/
├── specs/                     # Living capability specs
│   └── <capability>/
│       └── spec.md
└── changes/                   # Active and archived changes
    ├── <change-id>/           # Active change
    │   ├── proposal.md
    │   ├── design.md
    │   ├── tasks.md
    │   └── specs/             # Delta specs for this change
    │       └── <capability>/
    │           └── spec.md
    └── archive/               # Completed changes
        └── <date>-<change-id>/
```

---

## Slash Commands

Read the corresponding file in `commands/` for the full instructions of each
command. Summary:

| Command | Purpose |
|---|---|
| `/opsx-propose <id>` | One-shot: create change + all planning artifacts |
| `/opsx-new <id>` | Create a new change scaffold (no artifacts yet) |
| `/opsx-ff` | Fast-forward: generate all remaining artifacts |
| `/opsx-continue` | Generate the next artifact (incremental) |
| `/opsx-explore` | Think through ideas before committing to a change |
| `/opsx-apply [id]` | Implement tasks from tasks.md |
| `/opsx-verify [id]` | Validate implementation against spec |
| `/opsx-archive [id]` | Merge specs, archive the change |
| `/opsx-bulk-archive` | Archive all completed changes |
| `/opsx-onboard` | Interactive tutorial using your codebase |
| `/opsx-status [id]` | Show artifact completion status |

---

## Core Spec Format

Specs use SHALL/GIVEN/WHEN/THEN language. Read `references/spec-format.md` for
the full format guide and templates.

---

## When OpenSpec Is Not Installed

If a user invokes an `/opsx-*` command and the `openspec/` directory doesn't
exist, run the setup procedure:

1. Create `openspec/specs/` and `openspec/changes/` directories
2. Create a `openspec/README.md` explaining the structure
3. Copy all command files from `commands/` into `.claude/commands/`
4. Confirm: "OpenSpec initialized. Try `/opsx-propose <feature-name>`"

---

## Reading This Skill

- For command behavior: read `commands/<command>.md`
- For spec/artifact formats: read `references/spec-format.md`
- For artifact templates: read `references/artifact-templates.md`

Related in Design