skills.rest
mazhewitt
mazhewittCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Create an OpenSpec change scaffold with status and first-artifact instructions.

Updated Feb 15, 2026
Search Tags:#workflow#scaffolding#cli#openspec#change-management#artifact-workflow
One-click install
npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-new-change-mazhewitt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/mazhewitt/budget-analyser/tree/main/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/mazhewitt/budget-analyser --skill openspec-new-change-mazhewitt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams starting OpenSpec changes often encounter inconsistent scaffolds and unclear steps. This Skill provides a consistent, artifact-driven workflow to initialize a new change with a defined structure and guardrails.

Core Features & Use Cases

  • Scaffold a new OpenSpec change at openspec/changes/<name> with a chosen or default schema
  • Show status and provide first-artifact instructions without creating anything yet
  • Validate the change name (kebab-case) and suggest continuation if a change already exists
  • Works for feature additions, fixes, or modifications across OpenSpec projects

Quick Start

Run openspec new change "openspec-new-change" to create a scaffold and then review the status and first-artifact instructions.

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 new OpenSpec change for a feature or fix?▼

To scaffold an OpenSpec change, run the new change command to create a structured directory at openspec/changes/<name>. This initializes the change with a chosen or default schema, providing status reporting and first-artifact instructions without creating artifacts yet.

What is the artifact-driven workflow for OpenSpec change management?▼

The OpenSpec artifact workflow provides a consistent, repeatable setup to initialize changes with defined structures and guardrails. It offers scaffold creation, status reporting, and first-artifact instructions to ensure teams follow clear steps without inconsistent setups.

Does the OpenSpec change scaffold validate the change name format?▼

Yes, the OpenSpec change scaffold validates the change name to ensure it uses kebab-case formatting. If a change with that name already exists, it suggests continuation and provides status reporting instead of overwriting the existing scaffold.

Can I use the OpenSpec scaffolding workflow for modifications to existing projects?▼

Yes, the OpenSpec scaffolding workflow works for feature additions, fixes, or modifications across OpenSpec projects. It creates a structured scaffold at openspec/changes/<name> applicable to any software team needing a repeatable change setup.

Why does the OpenSpec scaffold only provide first-artifact instructions without creating them?▼

The OpenSpec scaffold provides first-artifact instructions without performing artifact creation to maintain a clear separation between setup and execution. This ensures teams review the status and structure before committing to the actual artifact workflow steps.

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
mrclrchtrmrclrchtr
54

openspec-new-change

Create scaffolded OpenSpec changes with kebab-case validation and artifact instructions.

Community
Intermediate
ondataondata
9

openspec-new-change

Initialize a new OpenSpec change with an artifact-driven workflow scaffold.

Official
Advanced
CatsofsufferingCatsofsuffering
5

openspec-new-change

Scaffold an OpenSpec change directory and validate kebab-case names.

Community
Intermediate