skills.rest
luifertorres
luifertorresCOMMUNITY
Explore all skills by this author →
𝕏@luifertorresGitHub

openspec-new-change

Automate OpenSpec change scaffolding with a kebab-case name and default workflow.

1|Updated Nov 3, 2023
Search Tags:#workflow#cli#spec#openspec#change#change-management#artifact-workflow
One-click install
npx skills add https://github.com/luifertorres/trading-assistant --skill openspec-new-change-luifertorres
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/luifertorres/trading-assistant/tree/main/.cursor/skills/openspec-new-change
Command: npx skills add https://github.com/luifertorres/trading-assistant --skill openspec-new-change-luifertorres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting an OpenSpec change currently lacks a unified, artifact-driven blueprint. This tool provides a structured workflow to create a new change, ensuring naming consistency, schema selection, and artifact scaffolding.

Core Features & Use Cases

  • Guides users to derive a kebab-case change name and select a default workflow schema.
  • Orchestrates the scaffold of a new change via the openspec CLI.
  • Provides clear status updates and first-artifact instructions to begin work.

Quick Start

Run openspec new change with a kebab-case name to scaffold a new OpenSpec change.

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 workflow?▼

To start an OpenSpec change, you run the command with a kebab-case name. The workflow then applies a default schema, scaffolds the change via the CLI, and reports ready artifacts to begin work.

What is artifact-driven change management in OpenSpec?▼

Artifact-driven change management provides a unified blueprint for creating features or fixes. It ensures naming consistency and schema selection by orchestrating step-by-step scaffolding through the openspec CLI.

Do I need to manually format the change name before scaffolding an OpenSpec change?▼

No, you do not need to manually format the name. The workflow automatically derives a kebab-case name from your input before applying the default workflow schema and scaffolding the change.

Can I use this workflow to scaffold both features and fixes?▼

Yes, you can scaffold both features and fixes. The workflow applies a structured, step-by-step process with artifact-driven guidance for any modifications managed within OpenSpec.

What happens after the OpenSpec CLI finishes scaffolding a change?▼

After scaffolding finishes, the workflow provides clear status updates and first-artifact instructions. This guides you to immediately begin work on the newly created change artifacts.

Best way to ensure naming consistency when creating OpenSpec changes?▼

The best way to ensure naming consistency is using the guided workflow. It automatically derives a kebab-case name and selects the standard workflow schema before scaffolding the change artifacts.

Related Skills

Explore More Software Engineering Skills→
moltbook-experimentsmoltbook-experiments
3

openspec-new-change

Bootstrap a new OpenSpec change with kebab-case naming and schema selection.

Official
Intermediate
wtg42wtg42

openspec-new-change

Scaffold an OpenSpec change directory and fetch the first artifact template.

Community
Intermediate
kamansoftkamansoft

openspec-continue-change

Generate the next artifact in an OpenSpec change workflow.

Official
Intermediate
jankneumannjankneumann
4

plan-roadmap

Decompose markdown proposals into prioritized OpenSpec change candidates with a dependency DAG.

Community
Advanced