openspec-new-change

Initialize and manage OpenSpec changes with artifact-driven scaffolding.

2|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/dshearer/misatay --skill openspec-new-change-dshearer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/dshearer/misatay/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/dshearer/misatay --skill openspec-new-change-dshearer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the initialization and ongoing management of OpenSpec changes through a deterministic artifact-driven workflow.

Core Features & Use Cases

  • Artifact-driven change scaffolding: Creates a structured change directory and plan using the OpenSpec CLI.
  • Deterministic workflows: Applies a repeatable process with status checks and guided instructions before creating artifacts.
  • Use Case: A developer wants to start a new feature with a clear, auditable change history.

Quick Start

Open the command palette and run openspec new change with a kebab-case name to scaffold a new change.

Frequently Asked Questions about openspec-new-change

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

FAQPage Schema
How do I scaffold a structured feature change for software development?

Scaffolding a structured feature change requires automating the initialization of specific directories, frontmatter with name and description, and status tracking. This creates an auditable artifact workflow for managing feature work from start to finish.

What is an artifact-driven change workflow in software engineering?

An artifact-driven change workflow is a repeatable process that uses status checks and guided instructions before creating artifacts. It applies deterministic workflows to maintain consistent change management and status tracking across feature work.

How do I create a new change with the OpenSpec CLI?

Creating a new change with the OpenSpec CLI involves running the initialization command with a kebab-case name. This scaffolds the structured change directory and plan, applying built-in guardrails for safe orchestration.

Does change scaffolding support optional directories for scripts and assets?

Change scaffolding supports optional scripts, references, and assets directories alongside required frontmatter. This structure accommodates diverse development needs while maintaining built-in guardrails for safe orchestration.

When do I need a deterministic workflow for change management?

You need a deterministic workflow for change management when your software team requires consistent change scaffolding and auditable history. It applies repeatable processes with status checks before creating artifacts to ensure safe orchestration across feature work.

Are there built-in guardrails for safe orchestration during change initialization?

Built-in guardrails for safe orchestration exist during change initialization. These guardrails apply status checks and guided instructions before creating artifacts, ensuring deterministic workflows and consistent change scaffolding across feature work.