openspec-new-change

Name: openspec-new-change
Availability: InStock
Author: dvazquezd

Scaffold a new OpenSpec change directory using a workflow schema.

Updated Aug 23, 2026

Search Tags:#workflow #development #scaffolding #change management #openspec #artifact

Ready to run

npx skills add https://github.com/dvazquezd/openspec-governance --skill openspec-new-change-dvazquezd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/dvazquezd/openspec-governance/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/dvazquezd/openspec-governance --skill openspec-new-change-dvazquezd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the initiation of new development changes within the OpenSpec framework, ensuring adherence to structured artifact workflows from the outset.

Core Features & Use Cases

Initiate New Changes: Start feature, bugfix, or refactor changes with a clear name and purpose.
Structured Workflow: Automatically scaffolds a new change directory with a selected or default workflow schema.
Artifact Guidance: Provides the template and context for the first artifact required by the chosen workflow.
Use Case: When a developer needs to begin implementing a new user authentication feature, they can use this skill to create the necessary project structure and get started on the initial proposal artifact.

Quick Start

Use the openspec new change skill to start a new 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 development change with a structured workflow?▼

To start a new development change, you need a structured scaffolding workflow that creates a dedicated directory and applies a schema. This approach initiates the change and provides the template for your first artifact automatically.

Do I need a feature branch to scaffold a new OpenSpec change?▼

Yes, you need a feature branch to scaffold a new OpenSpec change. A feature branch is required for operation, alongside the OpenSpec CLI, to ensure your changes are isolated before the workflow scaffolding begins.

What is an artifact-driven workflow for software development?▼

An artifact-driven workflow structures development changes by requiring specific artifacts to be created and documented sequentially. It solves the problem of starting new tasks by scaffolding a clear directory structure and guiding the initial proposal artifact.

Can I start a new change using just a description instead of a name?▼

Yes, you can start a new change using just a description. The workflow supports deriving an explicit change name from your provided description, applying a default workflow schema if a specific one is not designated.

What's the best way to manage scaffolding for feature, bugfix, and refactor changes?▼

The best way to manage scaffolding for these changes is using an artifact-driven approach that supports explicit naming and purposes. It automatically applies a selected or default workflow schema to structure the change directory from the outset.