skills.rest
HalseyYang
HalseyYangCOMMUNITY
Explore all skills by this author →
GitHub

openspec

Guides spec-driven development workflows using the OpenSpec CLI and OPSX commands.

1|Updated Jul 13, 2026
Search Tags:#workflow#requirements#cli#sdd#spec-driven development#openspec#opsx
One-click install
npx skills add https://github.com/HalseyYang/Skills-HY --skill openspec-halseyyang
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec
Source: https://github.com/HalseyYang/Skills-HY/tree/main/openspec
Command: npx skills add https://github.com/HalseyYang/Skills-HY --skill openspec-halseyyang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It removes ambiguity from feature development by enforcing a spec-driven workflow where proposals, requirements, designs, and tasks are written and validated before implementation begins. ## Core Features & Use Cases - Spec-Driven Workflow: Create proposals, requirements, designs, and task lists through OPSX commands like /opsx:propose, /opsx:apply, and /opsx:archive. - CLI Integration: Initialize projects, inspect state, and validate changes with the openspec CLI using structured JSON output. - Validation & Archiving: Verify implementations against specs with openspec validate and archive completed changes into source-of-truth specs. - Use Case: When starting a new feature, use /opsx:propose to draft the change, implement only after specs are approved, then run openspec validate --all before archiving the completed change. ## Quick Start Ask the assistant to initialize OpenSpec in the current repository and create a proposal for the feature you want to build.

Frequently Asked Questions about openspec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start spec-driven development with OpenSpec?▼

Run openspec init --tools codex in your repository to set up the workflow, then use /opsx:propose to create a change with proposal, requirements, design, and tasks before writing any implementation code.

What are the main OpenSpec OPSX commands?▼

Core commands include /opsx:propose to draft changes, /opsx:apply to implement approved specs, /opsx:verify to check implementation against artifacts, and /opsx:archive to merge completed changes into source-of-truth specs.

How do I validate OpenSpec changes before completion?▼

Run openspec validate --all --json to validate all changes and specs with structured output, or target a specific change. Validation should pass before claiming implementation work is complete.

Should I implement code before writing OpenSpec specs?▼

No. The workflow requires proposal, requirements, design, and task artifacts to be clear before substantial implementation begins. Specs serve as the durable record of requirements rather than chat history.

What happens if OpenSpec is not initialized in my repo?▼

Check whether an openspec/ directory already exists first. If not, confirm the target repository path with the user, then run openspec init to set up the spec-driven workflow structure.

Related Skills

Explore More Software Engineering Skills→
hexian2001hexian2001
31

doc-coauthoring

Create structured documentation through context gathering, iterative refinement, and simulated reader testing.

Community
Advanced
haposofthaposoft
54

hapo:code

Automate implementation of approved software specification tasks with design context.

Official
Intermediate
AnveioAnveio
1

role-software-engineer

Apply software engineer principles and success criteria to development workflows.

Community
Basic
Busboom-FooBusboom-Foo

oop

Apply small code changes directly to master with a deterministic test workflow.

Official
Intermediate