skills.rest
emilianoeloi
emilianoeloiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-workflow

Manages spec-driven change proposals with OpenSpec validation and SDLC lifecycle tracking.

6|Updated Feb 25, 2026
Search Tags:#validation#governance#sdlc#change management#spec-driven development#openspec#proposal
One-click install
npx skills add https://github.com/emilianoeloi/cowboy --skill openspec-workflow-emilianoeloi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-workflow
Source: https://github.com/emilianoeloi/cowboy/tree/main/.github/skills/openspec-workflow
Command: npx skills add https://github.com/emilianoeloi/cowboy --skill openspec-workflow-emilianoeloi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It enforces spec-driven development by requiring every code change to be planned, documented, and validated through OpenSpec artifacts before any implementation begins, preventing untracked or unspecified modifications. ## Core Features & Use Cases - Change Proposal Workflow: Creates the four canonical artifacts (.openspec.yaml, proposal.md, design.md, tasks.md) inside openspec/changes/<change-name>/ with strict kebab-case naming. - Lifecycle Operations: Guides opsx-propose, opsx-apply, and opsx-archive operations, including harness phase synchronization via phase_cli.py. - Strict Validation: Runs openspec validate <change-name> --strict to mechanically verify change compliance before and after implementation. - Use Case: When adding a new operation to a COBOL calculator, use this Skill to draft the proposal, design decisions, and phased task checklist, then validate the change before writing any source code. ## Quick Start Ask the agent to create an OpenSpec change proposal named in kebab-case for the feature you want, then validate it with openspec validate --strict.

Frequently Asked Questions about openspec-workflow

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

FAQPage Schema
How do I create an OpenSpec change proposal?▼

Create a kebab-case directory under openspec/changes/<change-name>/ containing .openspec.yaml, proposal.md, design.md, and tasks.md. Then run openspec validate <change-name> --strict to confirm the artifacts meet the schema requirements.

What files does an OpenSpec change require?▼

Each change requires four canonical artifacts: .openspec.yaml for metadata, proposal.md for motivation and scope, design.md for architecture decisions, and tasks.md for a phased implementation checklist.

Can I write code during the OpenSpec proposal phase?▼

No. The proposal phase forbids editing source directories like src/ or docs/. A pre-tool-write guard hook restricts edits to planning paths such as openspec/ and spdd/ until the change is validated.

Why does openspec validate --strict fail on my change?▼

Validation fails when required sections are missing, the change name is not kebab-case, or artifact structure does not match the spec-driven schema. Fix the reported sections and re-run the strict validation before proceeding.

When should I archive an OpenSpec change?▼

Archive a change with openspec archive <change-name> only after all tasks in tasks.md are checked off, the final strict validation passes, and the change has been merged into the codebase.

Related Skills

Explore More Software Engineering Skills→
TheBoomerDevTheBoomerDev

feature-spec

Write standardized feature specifications aligning PRDs, requirements, and delivery plans.

Community
Advanced
JNZader-VaultJNZader-Vault

verification-before-completion

Run a verification checklist covering tests, code quality, Git workflow, functionality, and documentation.

Official
Intermediate
ElvinOuyangElvinOuyang

harness-troubleshoot

Diagnose Claude Code harness enforcement failures using a structured decision tree.

Community
Intermediate
Busboom-FooBusboom-Foo

oop

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

Official
Intermediate