openspec

Plans feature development with explicit specs, YAML frontmatter, and dash spec/openspec CLI tools.

2|Updated Jan 16, 2026
One-click install
npx skills add https://github.com/seikaikyo/dash-skills --skill openspec-seikaikyo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec
Source: https://github.com/seikaikyo/dash-skills/tree/main/skills/openspec
Command: npx skills add https://github.com/seikaikyo/dash-skills --skill openspec-seikaikyo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan feature development with explicit specifications to prevent drift.

Core Features & Use Cases

  • Spec-driven workflow: create specs, changes, and archived decisions to track feature progress.
  • CLI tooling: uses dash spec and openspec commands to manage specs and changes.
  • Team collaboration: supports multi-person ideation and proposals; integrates with dev workflows.

Quick Start

Install the OpenSpec CLI and run dash spec init . to begin defining features as specs.

Frequently Asked Questions about openspec

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

FAQPage Schema
How does spec-driven development prevent requirements drift during feature planning?

Spec-driven development prevents requirements drift by enforcing explicit specifications across ideation, change proposals, and implementation. Using a structured file format with YAML frontmatter tracks feature progress and aligns team collaboration.

How do I create a new feature specification and manage changes with OpenSpec?

To create a feature specification, install the OpenSpec CLI and run dash spec init. This sets up the defined workflow directories for specs, changes, and archive to manage proposals and track feature progress end-to-end.

Can I use spec-driven workflows for team collaboration and multi-person proposals?

Yes, spec-driven workflows support multi-person ideation and proposals. The structured workflow integrates with dev workflows, allowing teams to submit changes and archive decisions collaboratively to prevent specification drift.

What is the best way to structure specification files for change management?

The best way to structure specification files for change management is using a defined workflow with YAML frontmatter. Organize files into specs, changes, and archive directories to explicitly track feature progress and prevent drift.

Do I need the OpenSpec CLI to manage specs and changes in my project?

Yes, you need the OpenSpec CLI to manage specs and changes in your project. Running dash spec commands initializes the structured workflow and integrates tooling to enforce the spec-driven development process.