skills.rest
futuretea
futureteaCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Scaffold an OpenSpec change and retrieve first-artifact instructions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and spec authors start a new OpenSpec change in a structured, artifact-driven way so they don't have to manually scaffold directories, query workflow schemas, or guess the first artifact to create.

Core Features & Use Cases

  • Guided Scaffolding: Creates a new change scaffold using openspec new change with optional schema selection.
  • Artifact Discovery: Runs status checks to identify which artifacts are required and which are ready.
  • First-Artifact Instructions: Retrieves the template and context for the first ready artifact without creating any artifacts.
  • Use Case: When adding a new feature or fix, run this workflow to generate the change directory, inspect artifact status, and obtain the first artifact template to begin authoring.

Quick Start

Start a new OpenSpec change named add-user-auth by asking to scaffold the change and show the 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 and get the first artifact template?▼

OpenSpec change management is an artifact-driven workflow where you scaffold a change directory, inspect required artifacts via status checks, and author templates sequentially. It prevents manual directory creation and guessing which spec artifact to write first.

How do I check which artifacts are required for an OpenSpec change?▼

Yes, OpenSpec scaffolding supports optional schema selection. When creating a new change with the CLI, you can specify a schema to structure the artifact workflow according to your specific feature or modification requirements.

Do I need the openspec CLI to start a new change management workflow?▼

Yes, the openspec CLI is required to scaffold a new change. It validates kebab-case naming, applies optional schema selection, inspects artifact status, and retrieves the first-artifact template for the experimental artifact workflow.

Does the OpenSpec scaffold automatically create artifacts when starting a change?▼

No, the OpenSpec scaffold does not create artifacts automatically. It generates the change directory and retrieves the template and context for the first ready artifact, leaving the actual artifact authoring to the developer or spec author.

Why does my OpenSpec change name fail validation when scaffolding?▼

OpenSpec change names fail validation if they are not in kebab-case format. You must use lowercase letters separated by hyphens, such as add-user-auth, to successfully scaffold the change directory.

Related Skills

Explore More Software Engineering Skills→
CatsofsufferingCatsofsuffering
5

openspec-new-change

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

Community
Intermediate
tonysyutonysyu
2

openspec-continue-change

Generate the next OpenSpec workflow artifact using the OpenSpec CLI.

Community
Advanced
roger8broger8b

openspec-continue-change

Generate OpenSpec change artifacts to continue workflow progression.

Community
Intermediate
sgiathsgiath
4

openspec-new-change

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

Community
Intermediate