How do I install the Openspec Workflow skill?

Run npx skillmds@latest add tomevault-io/openspec-workflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Openspec Workflow safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Openspec Workflow?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Openspec Workflow free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Openspec Workflow?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Openspec Workflow by tomevault-io — Agent Skill

Name: Openspec Workflow
Author: tomevault-io

File contents

OpenSpec Workflow Skill

You are an expert in spec-driven development using OpenSpec.

Project OpenSpec Structure

openspec/
├── AGENTS.md           # Instructions for AI
├── project.md          # Project context
├── specs/              # Current truth (25 specs, 198 requirements)
│   ├── game-engine/
│   ├── player/
│   ├── world/
│   ├── dqn-agent/
│   ├── reinforcement-learning/
│   └── ...
└── changes/            # Proposals
    └── archive/        # Completed changes

OpenSpec CLI Commands

# List all specs
openspec list --specs

# View specific spec
openspec show <spec-name>

# List active changes
openspec list

# Validate specs
openspec validate --specs --strict --no-interactive

# Validate specific change
openspec validate <change-id> --strict --no-interactive

# Archive completed change
openspec archive <change-id> --yes

Creating a Change Proposal

1. Choose a verb-led change ID

Examples: add-new-strategy, update-reward-function, refactor-pathfinding

2. Create the structure

mkdir -p openspec/changes/<change-id>/specs/<capability>

3. Create proposal.md

# Change: Brief description

## Why
1-2 sentences on problem/opportunity

## What Changes
- Bullet list of changes
- Mark breaking changes with **BREAKING**

## Impact
- Affected specs: [list]
- Affected code: [key files]

4. Create tasks.md

## 1. Implementation
- [ ] 1.1 First task
- [ ] 1.2 Second task
- [ ] 1.3 Write tests

5. Create spec delta

## ADDED Requirements
### Requirement: New Feature
The system SHALL provide...

#### Scenario: Success case
- **WHEN** condition
- **THEN** expected result

## MODIFIED Requirements
### Requirement: Existing Feature
[Complete updated requirement]

6. Validate

openspec validate <change-id> --strict --no-interactive

Workflow Summary

Draft: Create proposal with spec updates
Review: Iterate until aligned
Implement: Work through tasks.md
Archive: Merge to specs/ after deployment

Spec Format Rules

Use #### Scenario: (4 hashtags) for scenarios
Every requirement MUST have at least one scenario
Use SHALL/MUST for normative requirements
Delta headers: ## ADDED|MODIFIED|REMOVED|RENAMED Requirements

Source: sdd330/ctf-ai — distributed by TomeVault.

---name: openspec-workflowdescription: OpenSpec spec-driven development workflow. Use when creating proposals, updating specs, planning features, or following the spec-driven development process. Use when this capability is needed.---# OpenSpec Workflow SkillYou are an expert in spec-driven development using OpenSpec.## Project OpenSpec Structure```openspec/├── AGENTS.md # Instructions for AI├── project.md # Project context├── specs/ # Current truth (25 specs, 198 requirements)│ ├── game-engine/│ ├── player/│ ├── world/│ ├── dqn-agent/│ ├── reinforcement-learning/│ └── ...└── changes/ # Proposals └── archive/ # Completed changes```## OpenSpec CLI Commands```bash# List all specsopenspec list --specs# View specific specopenspec show <spec-name># List active changesopenspec list# Validate specsopenspec validate --specs --strict --no-interactive# Validate specific changeopenspec validate <change-id> --strict --no-interactive# Archive completed changeopenspec archive <change-id> --yes```## Creating a Change Proposal### 1. Choose a verb-led change IDExamples: `add-new-strategy`, `update-reward-function`, `refactor-pathfinding`### 2. Create the structure```bashmkdir -p openspec/changes/<change-id>/specs/<capability>```### 3. Create proposal.md```markdown# Change: Brief description## Why1-2 sentences on problem/opportunity## What Changes- Bullet list of changes- Mark breaking changes with **BREAKING**## Impact- Affected specs: [list]- Affected code: [key files]```### 4. Create tasks.md```markdown## 1. Implementation- [ ] 1.1 First task- [ ] 1.2 Second task- [ ] 1.3 Write tests```### 5. Create spec delta```markdown## ADDED Requirements### Requirement: New FeatureThe system SHALL provide...#### Scenario: Success case- **WHEN** condition- **THEN** expected result## MODIFIED Requirements### Requirement: Existing Feature[Complete updated requirement]```### 6. Validate```bashopenspec validate <change-id> --strict --no-interactive```## Workflow Summary1. **Draft**: Create proposal with spec updates2. **Review**: Iterate until aligned3. **Implement**: Work through tasks.md4. **Archive**: Merge to specs/ after deployment## Spec Format Rules- Use `#### Scenario:` (4 hashtags) for scenarios- Every requirement MUST have at least one scenario- Use SHALL/MUST for normative requirements- Delta headers: `## ADDED|MODIFIED|REMOVED|RENAMED Requirements`---> Source: [sdd330/ctf-ai](https://github.com/sdd330/ctf-ai) — distributed by [TomeVault](https://tomevault.io).

Frequently asked questions

Openspec Workflow