openspec-new-change

Scaffold a new OpenSpec change with a default artifact workflow.

Updated May 29, 2025

Search Tags:#automation #scaffolding #cli #openspec #change-management #feature-development #artifact-workflow

Ready to run

npx skills add https://github.com/crozzbite/DnDApp --skill openspec-new-change-crozzbite

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines starting new OpenSpec changes by providing a consistent, artifact-driven scaffold and governance during feature development.

Core Features & Use Cases

Artifact-driven scaffolding: creates a ready-to-use change skeleton at openspec/changes/<name>, guiding teams through the artifact lifecycle.
Standardized workflow: applies a default artifact-driven process so changes are traceable and reproducible.
First-artifact readiness: surfaces instructions for the initial artifact without creating any artifacts yet.

Quick Start

Describe the change you want to implement, and I will scaffold an OpenSpec change in openspec/changes with a 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 scaffold a new OpenSpec change for feature development?▼

To scaffold a new OpenSpec change, describe the desired feature implementation and the tool will generate a standardized change skeleton at openspec/changes/<name>. This scaffold includes a default workflow, status reporting, and first-artifact instructions without creating any artifacts until you confirm.

What is an artifact-driven workflow in OpenSpec change management?▼

An artifact-driven workflow in OpenSpec change management provides a standardized, traceable process for feature development. It creates a ready-to-use change skeleton that guides teams through the artifact lifecycle, ensuring changes remain reproducible and governed throughout implementation.

Can I use OpenSpec to manage fixes and enhancements without generating artifacts immediately?▼

Yes, you can use OpenSpec to manage fixes and enhancements without generating artifacts immediately. The tool surfaces first-artifact readiness instructions and waits for your explicit confirmation before creating any artifacts within the change scaffold.

Does OpenSpec change scaffolding work for both developers and product teams?▼

OpenSpec change scaffolding is designed for both developers and product teams adopting the OpenSpec CLI. It streamlines starting new changes by applying a consistent, artifact-driven scaffold that governs feature development across the entire team.

What is the best way to start tracking feature changes using the OpenSpec CLI?▼

The best way to start tracking feature changes using the OpenSpec CLI is to initiate a new change scaffold. This applies a default artifact-driven workflow at openspec/changes/<name>, making changes traceable and reproducible while providing status reporting.

When should I not use an automated scaffold for OpenSpec changes?▼

You should not use an automated scaffold for OpenSpec changes if your project does not adopt the OpenSpec CLI or lacks an openspec/changes directory structure. The tool relies on this specific artifact workflow to enforce traceability and standardized governance.