openspec-new-change

Initiate an OpenSpec change scaffold with a kebab-case name.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/anaclumos/verifidia --skill openspec-new-change-anaclumos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/anaclumos/verifidia/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/anaclumos/verifidia --skill openspec-new-change-anaclumos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly scaffolds a new OpenSpec change using the experimental artifact workflow, eliminating manual setup and guesswork.

Core Features & Use Cases

  • Guided change creation: creates a new change scaffold with a clearly defined workflow.
  • Artifact-first guidance: provides step-by-step instructions for the first artifact based on the OpenSpec schema.
  • Safe, non-destructive planning: helps you align naming and schema before generating artifacts.

Quick Start

Provide a change name in kebab-case to begin the OpenSpec change workflow and let me guide you through the first artifact.

Frequently Asked Questions about openspec-new-change

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

FAQPage Schema
How do I start a new OpenSpec change for a software feature?

To start an OpenSpec change, provide a kebab-case change name to scaffold the new workflow. This initiates the artifact-driven process and guides you through the first artifact based on the OpenSpec schema.

What is the artifact-driven workflow in OpenSpec change management?

The artifact-driven workflow is a structured development process that scaffolds changes using a guided artifact sequence. It eliminates manual setup by providing step-by-step instructions for each artifact based on the OpenSpec schema.

Do I need to follow a specific naming convention to create an OpenSpec change?

Yes, you need to provide a change name in kebab-case to create an OpenSpec change. This safe, non-destructive planning step helps align naming and schema before generating any artifacts.

Can I use OpenSpec for planning fixes as well as new feature development?

Yes, you can use OpenSpec for structured feature changes or fixes. It applies to software development projects seeking a guided artifact sequence to manage the change creation process safely.

What's the best way to scaffold a structured change without manual setup?

The best way to scaffold a structured change without manual setup is using the OpenSpec artifact workflow. It automatically creates the change scaffold and provides artifact-first guidance to eliminate guesswork.

Does the OpenSpec change workflow require any specific dependencies?

No, the OpenSpec change workflow does not require any specific dependencies to initiate. It directly scaffolds the change and guides you through the first artifact once you provide a kebab-case name.