openspec-new-change

Name: openspec-new-change
Availability: InStock
Author: sgiath

Scaffold a new OpenSpec change directory with an artifact-driven workflow.

4|3|Updated Jan 16, 2023

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

Ready to run

npx skills add https://github.com/sgiath/secp256k1 --skill openspec-new-change-sgiath

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a structured workflow to create new changes in OpenSpec using an artifact-driven approach, reducing setup time and errors.

Core Features & Use Cases

Guided change scaffolding: Creates a new change directory with a default artifact workflow ready for first artifact.
Artifact-driven workflow: Provides step-by-step guidance to generate and manage change artifacts using OpenSpec CLI.
Use Case: Teams deploying new features can quickly initialize a change with consistent naming and process.

Quick Start

Create a new change scaffold named openspec-new-change using the 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 start a new OpenSpec change using an artifact-driven workflow?▼

To start a new OpenSpec change, this skill automates scaffolding a change directory and provides guided instructions for generating artifacts using the default workflow. It reduces manual setup time and errors when initializing structured feature changes.

What is the best way to scaffold OpenSpec change artifacts without manual setup?▼

Scaffolding OpenSpec change artifacts is best handled by automating the creation of a new change directory with a default artifact workflow ready for the first artifact. This ensures consistent naming and process structure for teams deploying new features.

Do I need the OpenSpec CLI to automate change management workflows?▼

Yes, the OpenSpec CLI is required to automate this change management workflow. The skill relies on the CLI to adhere to the default artifact workflow, scaffold the change directory, and provide step-by-step guidance for generating and managing artifacts.

Can I use this to initialize a structured feature workflow for teams?▼

Yes, teams deploying new features can use this to quickly initialize a structured change with consistent naming and a guided process. It creates a default artifact-driven workflow ready for the first artifact to reduce setup time.

Why use an artifact-driven workflow for OpenSpec change management?▼

An artifact-driven workflow for OpenSpec change management provides step-by-step guidance to generate and manage change artifacts consistently. This structured approach reduces setup errors and ensures consistent process adherence across team feature deployments.

Does openspec-new-change support custom artifact workflows?▼

No, openspec-new-change adheres to the default artifact workflow to scaffold the change and provide guided instructions. It automates starting a structured OpenSpec change using this default artifact-driven approach without custom workflow configurations.