openspec-new-change

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

149|22|Updated Mar 6, 2026
One-click install
npx skills add https://github.com/luzhenqian/ai-coding-lab --skill openspec-new-change-luzhenqian
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/luzhenqian/ai-coding-lab/tree/main/agent/dev-bot/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/luzhenqian/ai-coding-lab --skill openspec-new-change-luzhenqian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes the initiation of OpenSpec changes by providing a guided, artifact-driven workflow that ensures every new feature, fix, or modification begins with a consistent scaffold.

Core Features & Use Cases

  • Guided change creation: scaffolds a new change directory and selects the default OpenSpec workflow.
  • Input-driven naming: derives a kebab-case change name from user-provided descriptions for consistency.
  • Guided artifact flow: presents the status of the change and first-artifact instructions without creating artifacts.

Quick Start

Describe a change you want to implement, and I will scaffold the OpenSpec change accordingly.

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 request with a standardized workflow?

To scaffold an OpenSpec change, describe the desired feature or fix, and the workflow derives a kebab-case name to initiate a standardized, artifact-driven directory structure for your project.

What is an artifact-driven workflow for managing code changes?

An artifact-driven workflow structures change management by scaffolding a default directory and providing first-artifact instructions, ensuring consistent initialization for features, fixes, or modifications without creating files prematurely.

How do I generate consistent kebab-case naming for feature requests and fixes?

Provide a natural language description of your modification or fix, and the workflow automatically derives a consistent kebab-case change name to standardize your project's scaffolding process.

Can I use this workflow to initiate different types of project modifications?

Yes, the workflow supports initiating diverse change types including new features, bug fixes, and modifications, applying a repeatable scaffolding process and default schema across all variations.

Does the scaffolding process create artifacts prematurely when starting a change?

No, the scaffolding process presents the change status and first-artifact instructions without creating artifacts prematurely, ensuring you maintain manual control over the initial file generation.

What is the best way to standardize the initialization of feature requests across a team?

Use a guided, artifact-driven workflow that enforces a default schema and derives consistent kebab-case names from user input, ensuring every team member scaffolds changes identically.