openspec-new-change

Name: openspec-new-change
Availability: InStock
Author: vuthuonghai-steve

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

Updated Aug 23, 2026

Search Tags:#automation #workflow #scaffold #devtools #openspec #artifact #change

Ready to run

npx skills add https://github.com/vuthuonghai-steve/KLTN --skill openspec-new-change-vuthuonghai-steve

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/vuthuonghai-steve/KLTN/tree/main/.cursor/skills/openspec-new-change
Command: npx skills add https://github.com/vuthuonghai-steve/KLTN --skill openspec-new-change-vuthuonghai-steve

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users to create a new OpenSpec change using the experimental artifact-driven workflow, providing a safe, repeatable process to initiate feature changes or fixes without immediately generating artifacts.

Core Features & Use Cases

Guides users to derive a kebab-case change name from their description.
Determines and applies the default OpenSpec workflow schema when creating a change.
Scaffolds the change structure under openspec/changes/<name>/ and surfaces the current status and the first artifact template for execution.

Quick Start

Describe your change in kebab-case name and I will scaffold it, show status, and present the first artifact template without creating anything yet.

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 software changes?▼

An artifact-driven workflow scaffolds OpenSpec changes by deriving a kebab-case name from your description, applying the default schema, and presenting the first artifact template. It prevents premature file creation by guiding modifications step-by-step.

Do I need to manually create the openspec/changes/ directory before scaffolding?▼

No, you do not need to manually create directories. The workflow automatically scaffolds the change structure under openspec/changes/<name>/ and reports the current status, ensuring a repeatable process without manual setup.

How do I scaffold a new feature fix using OpenSpec?▼

To scaffold a new feature fix, provide a kebab-case change name. The system applies the default OpenSpec workflow schema, generates the change directory, and surfaces the first artifact template to begin execution.

Does the OpenSpec scaffolding process create artifacts automatically?▼

No, the OpenSpec scaffolding process does not create artifacts automatically. It establishes guardrails by scaffolding the change structure and providing the first artifact template for execution without generating the actual artifacts.

Why use an artifact-driven workflow for new software modifications?▼

Using an artifact-driven workflow for new software modifications provides a safe, repeatable process. It ensures structured implementation by deriving the change name, selecting the schema, and guiding artifact creation step-by-step.