openspec

Manage OpenSpec change artifacts and validate progress with the OpenSpec CLI.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/zdpk/skills --skill openspec-zdpk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec
Source: https://github.com/zdpk/skills/tree/main/dotfiles/skills/custom/openspec/openspec
Command: npx skills add https://github.com/zdpk/skills --skill openspec-zdpk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Align code changes with a formal spec by using the OpenSpec CLI to drive design, implementation, and validation within a structured openspec/ project directory.

Core Features & Use Cases

  • Artifact lifecycle: initialize projects, create/change artifacts (proposal, specs, design, tasks), validate progress, and archive completed work.
  • Project structure: maintain an openspec/ directory to organize artifacts and references for traceability.
  • Workflow automation: integrate with development tools to enforce spec-aligned development across teams.

Quick Start

Initialize an OpenSpec project with openspec init and start a new change, then create the required artifacts and run status checks.

Frequently Asked Questions about openspec

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

FAQPage Schema
How do I align code changes with a written spec?

Spec-driven development aligns code changes with written specs by using the OpenSpec CLI to drive design, implementation, and validation within a structured project directory. It initializes projects and manages change artifacts.

What is the best way to start a spec-driven project?

Start a spec-driven project by running openspec init to create a structured openspec/ directory. This establishes the environment required to organize artifacts, references, and trace progress across development workflows.

How does the OpenSpec CLI manage change artifacts?

The OpenSpec CLI manages change artifacts by creating and tracking proposals, specs, designs, and tasks. It validates progress against the formal spec and archives completed work to maintain project traceability.

Can I integrate spec-driven development into existing development workflows?

You can integrate spec-driven development into existing workflows by maintaining an openspec/ directory to organize artifacts. The OpenSpec CLI automates status validation and lifecycle management across team development tools.

When should I archive change artifacts in a spec-driven workflow?

Archive change artifacts in a spec-driven workflow once the code changes are validated and completed. The OpenSpec CLI enforces this archival step to ensure final implementations align with the formal spec.

Do I need any specific dependencies to use a spec-first development workflow?

No specific dependencies are required to use this spec-first development workflow. The OpenSpec CLI operates independently to initialize projects, manage artifact lifecycles, and validate progress within your development environment.