openspec-new-change

Scaffold a new OpenSpec change directory with artifact workflow guidance.

6|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-new-change-remiverdiesen
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/remiverdiesen/ark-fork/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/remiverdiesen/ark-fork --skill openspec-new-change-remiverdiesen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you start a new OpenSpec change in a structured, repeatable way without skipping the setup steps or choosing the wrong workflow.

Core Features & Use Cases

  • Change Scaffolding: Creates a new change directory with the correct OpenSpec layout.
  • Workflow Selection: Uses the default schema unless a specific workflow is requested.
  • Artifact Guidance: Shows the current change status and the first ready artifact template so work can begin safely.
  • Use Case: A developer wants to add a feature or fix and needs the exact OpenSpec starting point, artifact order, and first drafting instructions before writing anything.

Quick Start

Ask to start a new OpenSpec change for your feature or fix, and include a kebab-case name if you already have one.

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 change in OpenSpec without missing setup steps?▼

To start a new OpenSpec change, you initiate a structured artifact-driven workflow that scaffolds the change directory, selects the correct schema, and provides first-artifact instructions before drafting begins.

What is an artifact-driven workflow for software change management?▼

An artifact-driven workflow structures change management by scaffolding a directory with predefined schemas, inspecting change status, and guiding the creation of specific artifacts sequentially to ensure a repeatable modification process.

How to scaffold a new directory for a feature request or bug fix?▼

Scaffolding a new directory for a feature or bug fix uses a change management workflow to create the correct layout, apply the default schema, and display the first ready artifact template for immediate drafting.

Can I use a custom workflow schema instead of the default for my OpenSpec change?▼

Yes, the change scaffolding process uses the default schema automatically, but you can request a specific workflow schema during setup to tailor the artifact-driven process to your planned modification.

What is the best way to ensure a repeatable change process for planned code modifications?▼

The best way to ensure a repeatable change process is using an artifact-driven workflow that enforces schema selection, directory scaffolding, status inspection, and first-artifact instructions before any drafting starts.

Does OpenSpec change scaffolding work for both feature requests and bug fixes?▼

Yes, OpenSpec change scaffolding applies to feature requests, bug fixes, and other planned modifications, providing the exact starting point, artifact order, and drafting instructions for any structured change.