openspec-new-change

Guides users through creating an OpenSpec change workflow step-by-step.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill openspec-new-change-inspedralbes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW/tree/main/prj-entrades-nou/.cursor/skills/openspec-new-change
Command: npx skills add https://github.com/inspedralbes/prj-entrades-bielDom-nguez-2DAW --skill openspec-new-change-inspedralbes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a new change using the experimental artifact-driven approach to organize feature work, fixes, or modifications with a clear, step-by-step workflow.

Core Features & Use Cases

  • Structured workflow: guides the user through schema selection, change creation, status checks, and artifact instructions.
  • Guardrails and prompts: prompts for user input when unclear, and defers artifact creation until user direction.
  • Use Case: teams implementing OpenSpec changes for new features or bug fixes can follow a repeatable process from planning to first artifact instruction.

Quick Start

Describe the change you want to work on to begin the OpenSpec change process.

Frequently Asked Questions about openspec-new-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a structured OpenSpec change for a new feature request?

To create a structured OpenSpec change, describe the feature you want to implement. The workflow guides you through schema selection, change creation, status checks, and first artifact instructions with guardrails and prompts for input.

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

The artifact-driven workflow is a step-by-step process for organizing feature work, fixes, or modifications. It uses schema selection and status checks to scaffold changes safely, deferring artifact creation until the user explicitly authorizes the next step.

How do I start an OpenSpec change lifecycle for a bug fix?

To start an OpenSpec change for a bug fix, describe the modification you want to work on. The guided process prompts you for necessary input, scaffolds the change structure, and provides first artifact instructions while deferring creation until you direct it.

Does the OpenSpec change workflow require manual authorization before creating artifacts?

Yes, the OpenSpec change workflow requires manual authorization. It provides guardrails that defer artifact creation until the user explicitly directs the next step, ensuring safe and controlled change management throughout the lifecycle.

Can I use this guided workflow for both feature requests and modifications?

Yes, you can use this guided workflow for feature requests, fixes, or modifications. It applies a structured step-by-step OpenSpec change lifecycle to any development task, including schema selection, status checks, and artifact instructions.

What are the limitations of deferring artifact creation in OpenSpec changes?

Deferring artifact creation acts as a guardrail to prevent premature scaffolding. The limitation is that the workflow pauses and cannot proceed to artifact instructions or status checks until the user provides explicit direction to authorize the next step.