openspec-new-change

Scaffold structured OpenSpec changes with artifact-driven workflows and validation.

14|1|Updated May 6, 2026
One-click install
npx skills add https://github.com/wzyxdwll/ccgx-workflow --skill openspec-new-change-wzyxdwll
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/wzyxdwll/ccgx-workflow/tree/main/.agents/skills/openspec-new-change
Command: npx skills add https://github.com/wzyxdwll/ccgx-workflow --skill openspec-new-change-wzyxdwll

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a new change using the experimental artifact-driven approach.

The approach guides users through naming, schema selection, directory scaffolding, progress visibility, and artifact guidance without performing any artifacts yet.

Core Features & Use Cases

  • Guided change scaffolding: creates a structured OpenSpec change layout under openspec/changes/<name>/ with default or user-specified workflow.
  • Non-destructive previews: shows the first artifact template and status without creating artifacts.
  • Guardrails and validation: enforces kebab-case naming, default schema usage, and clear prompts for user direction.

Quick Start

Run openspec new change "<name>" to scaffold a new change under openspec/changes/<name>/ with the selected schema, then run openspec status --change "<name>" to review progress and openspec instructions <first-artifact-id> --change "<name>" to view the first artifact template.

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 using command-line automation?

To scaffold a new OpenSpec change, run openspec new change "<name>" to validate kebab-case naming, select a default schema, and generate the directory structure under openspec/changes/<name>/.

What is the artifact-driven workflow for managing structured change lifecycles?

The artifact-driven workflow guides users through naming, schema selection, and directory scaffolding to manage structured change lifecycles, providing progress visibility and artifact guidance without immediately creating artifacts.

Can I preview the first artifact template before generating files in OpenSpec?

Yes, OpenSpec provides non-destructive previews by showing the first artifact template and status without creating artifacts, allowing you to review the structure before committing to generation.

How do I check the progress of an OpenSpec change after scaffolding?

After scaffolding an OpenSpec change, run openspec status --change "<name>" to review progress, or use openspec instructions <first-artifact-id> --change "<name>" to view the first artifact template.

Does the OpenSpec change scaffolding enforce specific naming conventions?

Yes, the OpenSpec change scaffolding enforces kebab-case naming validation for change names, ensuring directory structures under openspec/changes/<name>/ adhere to required formatting standards.

Do I need to specify a workflow schema when creating a new OpenSpec change?

No, you do not need to manually specify a workflow schema; OpenSpec applies a default schema automatically during scaffolding while still allowing user-specified workflow selection if needed.