skills.rest
deicer
deicerCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

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

Updated Mar 8, 2026
Search Tags:#development#bug fix#change management#openspec#artifact workflow#feature creation
One-click install
npx skills add https://github.com/deicer/codex-lb --skill openspec-new-change-deicer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/deicer/codex-lb/tree/main/.agents/skills/openspec-new-change
Command: npx skills add https://github.com/deicer/codex-lb --skill openspec-new-change-deicer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of new changes within the OpenSpec framework, guiding users through an artifact-driven workflow for features, fixes, or modifications.

Core Features & Use Cases

  • Structured Change Creation: Initiates a new change with a user-defined name or description.
  • Workflow Schema Management: Selects a default or user-specified schema for the change process.
  • Artifact Scaffolding: Generates the necessary directory structure and provides instructions for the initial artifact.
  • Use Case: A developer needs to add a new authentication feature to a project. They use this Skill to start a new change, define its scope, and get the initial steps for creating the proposal artifact.

Quick Start

Start a new OpenSpec change for adding user authentication.

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 for a feature or bug fix?▼

To start a new OpenSpec change, initiate the workflow with a user-defined name or description, select a default or custom schema, and generate the directory structure and initial artifact instructions.

What is artifact-driven workflow for change management?▼

Artifact-driven change management is a structured, step-by-step approach that scaffolds necessary directories and guides creation of initial proposal artifacts for features, fixes, or modifications.

Do I need the OpenSpec CLI to manage change directories and schemas?▼

Yes, the OpenSpec CLI is required to manage change directories, apply workflow schemas, and handle artifact generation during the structured change creation process.

Can I use a custom schema for OpenSpec change creation instead of the default?▼

Yes, you can select a user-specified schema to override the default workflow schema when initiating a new OpenSpec change for features or modifications.

What's the best way to structure a new modification in OpenSpec?▼

The best way to structure a new modification is using the artifact scaffolding workflow, which generates the required directory structure and provides instructions for the initial artifact proposal.

Why does OpenSpec generate an initial artifact when starting a change?▼

OpenSpec generates an initial artifact to provide structured, step-by-step instructions for defining the scope and proposal of a new feature, fix, or modification within the workflow.

Related Skills

Explore More Software Engineering Skills→
Alexander-TyagunovAlexander-Tyagunov
12

almanac

Initialize Magician workspaces with directory structure, CLAUDE.md, and permissions allowlist.

Community
Advanced
tungnguyen10tungnguyen10

openspec-propose

Generate structured change proposal artifacts with the openspec CLI.

Community
Intermediate
hnabyz-bothnabyz-bot

moai-workflow-spec

Plan and orchestrate MoAI-ADK SPEC workflows using EARS and Plan-Run-Sync.

Community
Advanced
PBH-BTNPBH-BTN
6.2k

openspec-ff-change

Generate OpenSpec change artifacts in dependency order via the OpenSpec CLI.

Official
Advanced