skills.rest
ZanebonoAlter
ZanebonoAlterCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-new-change

Scaffold OpenSpec changes with kebab-case naming and status checks.

19|4|Updated Jan 11, 2026
Search Tags:#cli#scaffold#kebab-case#openspec#change-management#artifact-workflow
One-click install
npx skills add https://github.com/ZanebonoAlter/Syntopica --skill openspec-new-change-zanebonoalter
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/ZanebonoAlter/Syntopica/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/ZanebonoAlter/Syntopica --skill openspec-new-change-zanebonoalter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec users often need a consistent, repeatable way to start a new change (feature, fix, or modification) using a structured workflow.

Core Features & Use Cases

  • Guides users to name changes in kebab-case and select a default artifact workflow
  • Scaffolds the change directory, checks status, and provides the first artifact instructions without creating artifacts
  • Supports scenarios for features, fixes, or modification requests in OpenSpec projects

Quick Start

Describe the change you want to work on and I will scaffold it using the experimental artifact 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 a structured artifact workflow?▼

To start an OpenSpec change, the workflow scaffolds the change directory, checks status, and provides first artifact instructions. It enforces kebab-case naming and guides users through selecting a default artifact workflow.

What is the artifact workflow process for creating an OpenSpec feature or fix?▼

The OpenSpec artifact workflow process automates naming, scaffolds directories, and reports status. It stops before artifact creation, providing structured instructions for features, fixes, or modifications.

Does the OpenSpec change workflow enforce kebab-case naming for all modification requests?▼

Yes, the OpenSpec change workflow enforces kebab-case naming for all modification requests. It ensures consistent naming conventions across features, fixes, and modifications during the scaffolding process.

Can I use this workflow to scaffold OpenSpec changes without automatically generating artifacts?▼

Yes, you can scaffold OpenSpec changes without automatic artifact generation. The workflow stops before artifact creation, providing status checks and first artifact instructions instead of generating files automatically.

What are the limitations of the OpenSpec change scaffolding workflow?▼

The OpenSpec change scaffolding workflow stops before artifact creation and does not generate artifacts automatically. It focuses on directory scaffolding, kebab-case naming, and status reporting for the experimental artifact workflow.

Related Skills

Explore More Software Engineering Skills→
tneztnez

bootstrap

Initialize the .docent directory structure and configuration for new projects.

Community
Basic
daodaoedudaodaoedu

openspec-ff-change

Generate OpenSpec change artifacts in dependency order using the openspec CLI.

Official
Intermediate
optionioptioni

openspec-new-change

Automate initiation of a new OpenSpec change with structured user interaction.

Official
Intermediate
LippyyDevLippyyDev
1

openspec-new-change

Scaffold OpenSpec changes with naming conventions and artifact sequencing.

Community
Intermediate