skills.rest
caelaxie
caelaxieCOMMUNITY
Explore all skills by this author →
Website𝕏@caelaxieGitHub

openspec-new-change

Initiate a new OpenSpec change with an artifact-driven workflow.

Updated Apr 15, 2026
Search Tags:#automation#workflow#schema#cli#openspec#artifact#change
One-click install
npx skills add https://github.com/caelaxie/agenthub --skill openspec-new-change-caelaxie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/caelaxie/agenthub/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/caelaxie/agenthub --skill openspec-new-change-caelaxie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users initiate a new OpenSpec change—such as a feature, fix, or modification—by providing a clear, step‑by‑step, artifact‑driven workflow that reduces ambiguity and manual setup.

Core Features & Use Cases

  • Interactive Input Gathering: Uses the AskUserQuestion tool to clarify the change intent and generate a proper kebab‑case name.
  • Workflow Selection: Automatically chooses the default schema or lets the user pick a specific workflow when requested.
  • Scaffold Generation: Runs openspec new change to create the change directory with the appropriate schema.
  • Artifact Guidance: Shows the status of required artifacts and provides the template for the first artifact, pausing for user confirmation before proceeding.
  • Use Case: Ideal for developers or product teams needing a repeatable process to start new OpenSpec changes without missing steps.

Quick Start

Ask the skill to start a new OpenSpec change named “add-user-auth” using the default 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 workflow?▼

To start a new OpenSpec change, the workflow interactively gathers your input, selects a schema, and runs the CLI to scaffold the directory with a step-by-step artifact-driven approach.

What is an artifact-driven workflow in OpenSpec?▼

An artifact-driven workflow structures development by guiding you through required artifacts step-by-step, showing artifact status and providing templates to ensure no setup steps are missed.

Do I need the openspec CLI installed to create a new change?▼

Yes, the openspec CLI is required. The workflow runs the `openspec new change` command to generate the change directory and apply the selected schema.

Can I choose a specific schema when initiating an OpenSpec change?▼

Yes, you can choose a specific schema. The workflow automatically selects the default but lets you pick a specific workflow schema during the interactive input gathering phase.

How does the workflow generate a kebab-case name for a new feature?▼

The workflow uses the AskUserQuestion tool to interactively clarify your change intent, then generates a proper kebab-case name for the scaffolded directory.

What's the best way to ensure I don't miss steps when creating an OpenSpec fix?▼

Use a guided workflow to avoid missing steps. It shows the status of required artifacts, provides templates, and pauses for your confirmation before proceeding to the next step.

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
woutervanranstwoutervanranst
1

openspec-new-change

Scaffold a new OpenSpec change with a kebab-case name under openspec/changes.

Community
Intermediate
YangYuS8YangYuS8

openspec-verify-change

Validate change implementations against specs, tasks, and design documents.

Community
Advanced
zekiriabdzekiriabd
140

using-sddpro

Route software development requests through the SDDPro framework workflow.

Community
Advanced