openspec-new-change

Create an OpenSpec change scaffold and present the first artifact template.

1|1|Updated May 5, 2026
One-click install
npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-new-change-cynkra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/cynkra/cynkra.ai.day/tree/main/indietypst/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/cynkra/cynkra.ai.day --skill openspec-new-change-cynkra

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It removes friction from starting an OpenSpec-driven workflow by guiding you to create the correct change scaffold, inspect artifact readiness, and generate the template for the first required artifact.

Core Features & Use Cases

  • Change Scaffolding with Experimental Artifact Workflow: Creates a new OpenSpec change directory using the requested change name and (when applicable) a specified workflow schema.
  • Artifact-Ready Discovery: Uses status output to determine which artifact is ready first and fetches the corresponding instructions template.
  • Guardrailed First-Artifact Kickoff: Stops after presenting the first artifact instructions to prevent accidental advancement or unintended artifact creation.

Use cases: initiating a new feature spec, preparing a structured fix workflow, or executing a modification with consistent artifact-driven documentation and review.

Quick Start

Tell the skill the change you want to work on (use a kebab-case change name if you have one), and it will create the scaffold plan and show you the template for the first artifact without generating artifacts yet.

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 an OpenSpec change for a new feature spec?

To scaffold an OpenSpec change, provide a kebab-case change name and the tool creates the change directory structure, applies the selected workflow schema, and presents the template for the first required artifact.

What is an artifact workflow in project planning and how does it structure feature development?

An artifact workflow structures feature development by breaking changes into sequential, ready-to-generate documentation templates, ensuring consistent review and preventing unintended advancement before each step is completed.

How do I start a structured fix workflow using OpenSpec?

Start a structured fix workflow by requesting a new change scaffold with a kebab-case name; the tool inspects artifact readiness, selects the workflow schema, and retrieves instructions for the first ready artifact.

Does the OpenSpec change scaffolding process generate all artifacts at once?

No, the scaffolding process stops after presenting the first artifact instructions to prevent accidental advancement, ensuring you review the initial template before generating any subsequent artifacts.

Can I explicitly select a workflow schema when creating a new OpenSpec change?

Yes, you can explicitly request a specific workflow schema during change scaffolding, or allow the tool to apply a default schema if no explicit schema selection is provided.

Why does my OpenSpec change require a kebab-case naming format?

OpenSpec change scaffolding requires kebab-case naming to maintain consistent directory structures and artifact generation, enforcing a standardized format for feature development and fix workflows.