skills.rest
zh-impact
zh-impactCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Initiate OpenSpec changes with artifact-driven workflow and kebab-case validation.

Updated Aug 23, 2026
Search Tags:#scaffolding#openspec#command-line#change-management#workflow-guidance#artifact-workflow
One-click install
npx skills add https://github.com/zh-impact/fcollections --skill openspec-new-change-zh-impact
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/zh-impact/fcollections/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/zh-impact/fcollections --skill openspec-new-change-zh-impact

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a new OpenSpec change using the experimental artifact-driven workflow, providing a structured, repeatable process for creating features, fixes, or modifications.

Core Features & Use Cases

  • Guided change initiation: collects a kebab-case name, selects the appropriate workflow schema (default or non-default), and scaffolds the change directory.
  • Artifact-first status: shows which artifacts are ready and what remains, without creating artifacts automatically.
  • Guardrails and clarity: validates naming conventions, enforces workflow choices, and defers artifact creation until user confirmation.

Quick Start

Describe the change you want to start, and I will guide you through the OpenSpec change workflow.

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 OpenSpec change using the command-line?▼

To start an OpenSpec change, describe the desired modification and the guided workflow collects a kebab-case name, selects the appropriate schema, and scaffolds the change directory.

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

The artifact-driven workflow is a structured process that displays artifact readiness status and defers creation until explicit user confirmation, ensuring an artifact-first approach to change management.

Does the OpenSpec workflow enforce naming conventions for change directories?▼

Yes, the OpenSpec workflow enforces kebab-case validation for naming conventions. It applies strict guardrails to ensure your change directory names meet the required formatting standards before scaffolding proceeds.

Can I use a non-default workflow schema for scaffolding OpenSpec changes?▼

Yes, you can use non-default workflow schemas. The guided workflow handles default versus non-default schema selection based on your specific change scenario and scaffolds the directory accordingly.

Why does OpenSpec defer artifact creation until user confirmation?▼

OpenSpec defers artifact creation to prevent premature file generation. This guardrail ensures you retain full control over the workflow and only generate artifacts when initial preparation and status checks are complete.

Related Skills

Explore More Product & Management Skills→
luzhenqianluzhenqian
149

openspec-new-change

Scaffold OpenSpec changes with kebab-case names and default workflows.

Community
Intermediate
finger-gunfinger-gun
4

openspec-new-change

Scaffold a new OpenSpec change directory with artifact workflow instructions.

Official
Intermediate
fjpulidopfjpulidop
9

openspec-new-change

Scaffold OpenSpec change directories and guide first artifact creation.

Community
Advanced
inspedralbesinspedralbes

openspec-ff-change

Scaffold OpenSpec change artifacts in dependency order using templates.

Official
Advanced