openspec-new-change

Initiate OpenSpec changes with an artifact-driven workflow and CLI.

1|Updated Jul 30, 2023

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

Ready to run

npx skills add https://github.com/DanielShuguang/tool-box --skill openspec-new-change-danielshuguang

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/DanielShuguang/tool-box/tree/main/.trae/skills/openspec-new-change
Command: npx skills add https://github.com/DanielShuguang/tool-box --skill openspec-new-change-danielshuguang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of new changes within the OpenSpec framework, guiding users through a structured, step-by-step process for feature development, bug fixes, or modifications.

Core Features & Use Cases

Structured Change Creation: Guides users to create new changes using a defined workflow.
Automated Scaffolding: Generates initial change directories and artifacts based on user input and selected schemas.
Use Case: A developer needs to implement a new user authentication feature. They use this Skill to initiate the change, define its name, and get the initial scaffolding and instructions to begin development.

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 initiate a new change in OpenSpec for feature development?▼

To initiate a new OpenSpec change, use an experimental artifact-driven workflow that guides you step-by-step through defining and scaffolding new features, fixes, or modifications. The process generates initial change directories and artifacts based on your selected schemas.

What is an artifact-driven workflow for change management?▼

An artifact-driven workflow for change management structures development by generating initial directories and artifacts based on user input. This approach streamlines creating new features or bug fixes by enforcing a defined, step-by-step process from initiation.

Do I need the OpenSpec CLI to scaffold new change directories?▼

Yes, the OpenSpec CLI is required to scaffold new change directories and perform status checks. The CLI drives the automated generation of initial artifacts based on your provided input and selected schemas.

Can I use OpenSpec to structure bug fixes and modifications?▼

Yes, OpenSpec supports structured, step-by-step creation of bug fixes and modifications alongside new features. It guides you through defining the change name and generates the initial scaffolding needed to begin development.

What's the best way to scaffold a new user authentication feature using OpenSpec?▼

The best way to scaffold a user authentication feature is using the OpenSpec new change workflow. It initiates the change, helps define its name, and automatically generates the initial scaffolding and instructions needed to begin development.

Why does OpenSpec use an experimental workflow for change generation?▼

OpenSpec uses an experimental workflow to streamline structured change creation and automate scaffolding. This approach ensures new features, fixes, or modifications are consistently defined through generated artifacts rather than manual setup.