skills.rest
styrene-lab
styrene-labOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec

Coordinate OpenSpec lifecycle artifacts across change directories, specs, and tasks.

47|11|Updated Feb 28, 2026
Search Tags:#verification#tasks#lifecycle#spec-driven development#openspec#design tree
One-click install
npx skills add https://github.com/styrene-lab/omegon --skill openspec-styrene-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec
Source: https://github.com/styrene-lab/omegon/tree/main/skills/openspec
Command: npx skills add https://github.com/styrene-lab/omegon --skill openspec-styrene-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec keeps complex software changes organized by linking intent, specs, design decisions, tasks, and verification into one lifecycle so implementation does not drift from requirements.

Core Features & Use Cases

  • Spec-driven change management: Create and evolve change folders with proposals, delta specs, design notes, and task plans.
  • Lifecycle reconciliation: Keep task state, design-tree bindings, and archive readiness aligned with the current implementation reality.
  • Verification workflows: Map scenarios to tests, register failing stubs when tooling is available, and confirm that completed work satisfies the spec.
  • Use case: A team shipping a multi-file API change can define the desired behavior first, break it into scenario-owned tasks, implement safely, and archive only after verification passes.

Quick Start

Use the openspec skill to summarize the current lifecycle stage of a change and tell me the next artifact or action needed to move it forward.

Frequently Asked Questions about openspec

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

FAQPage Schema
How do I keep specs and implementation aligned during complex software changes?▼

Spec-driven development coordinates lifecycle artifacts by linking intent, specs, design decisions, and tasks into one lifecycle so implementation does not drift from requirements.

What is the best way to track lifecycle states for spec-driven development?▼

Lifecycle state tracking requires strict monitoring across proposing, specifying, planning, implementing, verifying, and archiving phases, keeping task state and design-tree bindings aligned with current implementation reality.

How do I map scenarios to tests for verification workflows?▼

Verification workflows map scenarios to tests, register failing stubs when lifecycle tooling is available, and confirm that completed work satisfies the spec before archiving.

Can I organize multi-file API changes using spec-driven change management?▼

Spec-driven change management creates and evolves change folders with proposals, delta specs, design notes, and task plans, allowing teams to define behavior first and archive only after verification passes.

When should I not use a spec-driven development lifecycle?▼

Spec-driven development adds overhead through strict lifecycle-state tracking and scenario-owned task grouping, making it less suitable for trivial changes that do not require design-tree reconciliation or formal verification.

Related Skills

Explore More Software Engineering Skills→
NSObjectsNSObjects
4

archiving

Merge delta specs into main specs and archive completed change folders.

Community
Advanced
studyzystudyzy
10.2k

openspec-archive-change

Archive completed OpenSpec experimental changes into date-prefixed directories.

Community
Advanced
BrennonTWilliamsBrennonTWilliams
7

scope-epic

Decompose project themes into EPIC issue files and child issue stubs.

Community
Advanced
TingRuDengTingRuDeng
2

worker-review-orchestrator

Orchestrate multi-agent task dispatch, execution tracking, and review-based decisioning for ForgeFlow workers.

Community
Advanced