openspec-new-change

Create a scaffolded change directory with workflow schema selection.

43|24|Updated Jul 3, 2018
One-click install
npx skills add https://github.com/tsedio/tsed-cli --skill openspec-new-change-tsedio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/tsedio/tsed-cli/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/tsedio/tsed-cli --skill openspec-new-change-tsedio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of initiating new changes within the OpenSpec framework, ensuring a structured and artifact-driven approach.

Core Features & Use Cases

  • Initiate New Changes: Creates a new, scaffolded change directory based on user input.
  • Workflow Schema Selection: Supports default or user-specified workflow schemas for change management.
  • Artifact Guidance: Provides initial instructions for the first artifact in the change workflow.
  • Use Case: A developer needs to propose a new feature for an API. They use this Skill to start a new change, get the initial template for the proposal artifact, and understand the next steps.

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 feature proposal using an artifact-driven workflow?

To start a new feature proposal, you initiate a scaffolded change directory using the OpenSpec CLI, which generates the initial artifact template and provides instructions for the first workflow step.

Can I use a custom workflow schema for change management instead of the default?

Yes, you can specify a custom workflow schema when initiating a new change, allowing you to adapt the artifact-driven process to fit your project's specific feature development or modification requirements.

Do I need the openspec CLI installed to create a new change directory?

Yes, the openspec CLI must be installed and configured on your system, as it is required to scaffold the change directory and generate the initial artifact instructions.

What is the best way to scaffold a new change for an API modification?

The best way to scaffold a new change for an API modification is to use the OpenSpec new change command, which establishes a structured, artifact-driven directory for your proposed fixes or features.

What happens after I initiate a new OpenSpec change?

After initiating a new OpenSpec change, the system provides initial instructions for the first artifact in the workflow, guiding you through the structured proposal process for your new feature or fix.

When should I use an artifact-driven change process for feature development?

You should use an artifact-driven change process when you need a structured approach to propose features, fixes, or modifications, ensuring changes are properly scaffolded and documented before implementation.