openspec-new-change

Initiate a new change in the OpenSpec framework with artifact tracking.

Updated May 5, 2022
One-click install
npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-new-change-blackbelttechnology
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/BlackBeltTechnology/judo-runtime-core/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/BlackBeltTechnology/judo-runtime-core --skill openspec-new-change-blackbelttechnology

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the creation of new changes within the OpenSpec framework, ensuring a structured and artifact-driven approach for features, fixes, or modifications.

Core Features & Use Cases

  • Guided Change Creation: Initiates a new change with a user-defined name or description.
  • Workflow Schema Selection: Defaults to a standard schema but allows for explicit selection of alternative workflows.
  • Artifact Status Tracking: Provides visibility into the progress of artifacts required for the change.
  • Use Case: A developer needs to add a new authentication module. They use this Skill to start the process, defining the change name and following the prompts to scaffold the necessary artifacts.

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 change in the OpenSpec framework?

To start a new change in the OpenSpec framework, you use a guided artifact-driven workflow that scaffolds the necessary files and tracks artifact status. You provide a change name or description, and the system initiates the structured process for your features or fixes.

What is an artifact-driven workflow for change management?

An artifact-driven workflow for change management structures the development process around required artifacts, providing visibility into their status. It guides users step-by-step through scaffolding features or fixes, ensuring a standardized approach to modifications within the OpenSpec framework.

Can I select a different workflow schema when creating an OpenSpec change?

Yes, you can select a different workflow schema when creating an OpenSpec change. While the system defaults to a standard schema for scaffolding, it allows explicit selection of alternative workflows to better suit your specific feature, fix, or modification requirements.

Do I need the OpenSpec CLI to scaffold new features and fixes?

Yes, you need the OpenSpec CLI to scaffold new features and fixes using this process. The CLI is required for execution to manage the artifact-driven workflow, track artifact status, and guide the structured creation of modifications.

What is the best way to track artifact status for a new software modification?

The best way to track artifact status for a new software modification is using an artifact-driven workflow. This approach provides visibility into the progress of all required artifacts during change scaffolding, ensuring structured development from start to finish.