openspec-new-change

Scaffold a new OpenSpec change directory with a workflow schema.

30|4|Updated Aug 2, 2024
One-click install
npx skills add https://github.com/belingud/gptcomet --skill openspec-new-change-belingud
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/belingud/gptcomet/tree/main/.codex/skills/openspec-new-change
Command: npx skills add https://github.com/belingud/gptcomet --skill openspec-new-change-belingud

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change scaffolding requires a consistent, artifact-driven approach to ensure changes are traceable, reproducible, and aligned with project standards. This Skill automates creating a new change scaffold and guides the user through schema selection and first-artifact preparation.

Core Features & Use Cases

  • Artifact-driven scaffolding: Generates a structured change directory at openspec/changes/<name>/ with the chosen workflow schema.
  • Guardrails: Validates the change name (kebab-case) and checks for existing changes to prevent duplicates.
  • Status & Instructions: Guides the user to inspect artifact readiness and fetch the first artifact instructions without creating artifacts prematurely.

Quick Start

Run the OpenSpec CLI to scaffold a new change and then select a workflow schema when prompted.

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 directory for spec-driven development?

To scaffold an OpenSpec change, run the OpenSpec CLI with a valid kebab-case name. This creates a structured directory at openspec/changes/<name>/ using the artifact-driven workflow to ensure changes are traceable and reproducible.

What is the artifact-driven workflow for OpenSpec change management?

The artifact-driven workflow is a structured process that organizes spec-driven development tasks under openspec/changes. It generates a consistent change directory and guides schema selection to align new features or fixes with project standards.

Do I need the OpenSpec CLI installed to create new change artifacts?

Yes, the OpenSpec CLI is required to scaffold new changes. You must provide a valid kebab-case change name, and the CLI validates the input and checks for existing directories to prevent duplicate artifacts.

How does the scaffolding process handle the first artifact template?

The scaffolding process presents the first artifact template without committing any artifacts prematurely. This allows users to inspect artifact readiness and fetch initial instructions before generating files in the change directory.

What happens if I try to create an OpenSpec change with a duplicate name?

The scaffolding process includes guardrails that validate the kebab-case change name and check for existing changes. If a duplicate is detected, the process prevents the creation of conflicting directories to maintain artifact integrity.

Can I use this scaffolding workflow for both new features and bug fixes?

Yes, the artifact-driven scaffolding applies to various spec-driven development tasks, including creating new features and fixes. It organizes all changes consistently under the openspec/changes directory for traceable project management.