skills.rest
arestivo
arestivoCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-new-change

Create OpenSpec change scaffolds with artifact-driven workflows.

Updated Feb 5, 2026
Search Tags:#automation#workflow#cli#openspec#change-management#artifact-driven
One-click install
npx skills add https://github.com/arestivo/qoodle --skill openspec-new-change-arestivo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/arestivo/qoodle/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/arestivo/qoodle --skill openspec-new-change-arestivo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams start new OpenSpec changes using an experimental, artifact-driven workflow, providing a repeatable scaffold and guided steps to kick off development.

Core Features & Use Cases

  • Artifact-driven change scaffolding: Creates a new OpenSpec change scaffold at openspec/changes/<name> with the default workflow.
  • Schema flexibility: Uses the default workflow schema and allows switching to a different schema with --schema <name>.
  • Guided first artifact: Provides instructions for creating the first artifact without performing actions.
  • Repeatable process: Supports consistent change setup across multiple features or fixes.

Quick Start

Provide a kebab-case change name. Optionally specify a schema, then run the OpenSpec CLI to create the scaffold. For example: openspec new change "my-feature"

Frequently Asked Questions about openspec-new-change

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

FAQPage Schema
What is an artifact-driven workflow for managing code changes?▼

An artifact-driven workflow structures development by scaffolding changes into specific output artifacts. It provides a repeatable process to create features or fixes, generating a guided plan for artifact creation rather than executing actions directly.

How do I start a new OpenSpec change using the CLI?▼

To start a new OpenSpec change, provide a kebab-case name and run the CLI command. This creates a scaffold at openspec/changes/<name> using the default workflow schema, outputting a ready-to-follow artifact creation plan.

Can I use a custom schema when scaffolding an OpenSpec change?▼

Yes, you can switch from the default workflow schema to a specific one by passing the --schema <name> argument. This allows flexible, structured change management tailored to your team's specific artifact requirements.

Do I need to format my feature names in a specific way for change scaffolding?▼

Yes, you must provide a kebab-case name for your feature, fix, or modification. This naming convention is required to correctly generate the scaffold directory at openspec/changes/<name>.

Does the OpenSpec change workflow automatically generate and execute artifacts?▼

No, the workflow does not perform actions automatically. It provides guided instructions for creating the first artifact, outputting a ready-to-follow creation plan to keep the setup process structured and manual.

When should I use an artifact-driven change management workflow?▼

Use this workflow when you need a structured, repeatable process to kick off development for multiple features or fixes. It ensures consistent change setup by scaffolding artifacts before development begins.

Related Skills

Explore More Software Engineering Skills→
moltbook-experimentsmoltbook-experiments
3

openspec-new-change

Bootstrap a new OpenSpec change with kebab-case naming and schema selection.

Official
Intermediate
sgiathsgiath
4

openspec-new-change

Scaffold a new OpenSpec change directory with an artifact-driven workflow.

Community
Intermediate
knopkiknopki
1

openspec-new-change

Scaffold new OpenSpec change directories using the OpenSpec CLI.

Community
Intermediate
tonysyutonysyu
2

openspec-new-change

Scaffold a new OpenSpec change with a kebab-case name and workflow schema.

Community
Intermediate