openspec-new-change

Scaffold a new OpenSpec change using the experimental artifact workflow.

Updated Jan 23, 2026

Search Tags:#scaffolding #CLI #instructions #openspec #change-management #artifact-workflow

Ready to run

npx skills add https://github.com/hossam7amdy/easy-auth --skill openspec-new-change-hossam7amdy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/hossam7amdy/easy-auth/tree/main/.agent/skills/openspec-new-change
Command: npx skills add https://github.com/hossam7amdy/easy-auth --skill openspec-new-change-hossam7amdy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided workflow to start a new OpenSpec change using the experimental artifact-driven process. It helps teams structure feature, fix, or modification work with a deterministic sequence of steps.

Core Features & Use Cases

Artifact-driven change scaffolding: Creates a change scaffold and guides through the artifact workflow.
Schema-aware workflow: Uses the default workflow schema unless a specific one is requested.
Progressive instructions: Retrieves the first ready artifact instructions and shows next steps without executing artifacts.
Use Case: A developer wants to prototype a new feature and needs a repeatable, auditable change process.

Quick Start

Use the openspec-new-change skill to initialize a new change for your feature. Then run: openspec new change "<name>" to scaffold, openspec status --change "<name>" to view progress, openspec instructions <first-artifact-id> --change "<name>" to get the first artifact template.

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 change for a feature using OpenSpec?▼

To scaffold a new change, run `openspec new change "<name>" to create the artifact-driven change structure. This sets up a deterministic sequence of steps for your feature, fix, or modification work without executing the artifacts directly.

What is an artifact-driven change workflow?▼

An artifact-driven change workflow structures feature, bugfix, or modification work into a deterministic sequence of steps. It guides you through artifact creation progressively, retrieving ready artifact instructions and showing next steps without executing them.

Do I need the openspec CLI to manage artifact workflows?▼

Yes, the openspec CLI is required to manage artifact workflows. You use it to scaffold new changes, view progress with `openspec status`, and retrieve artifact templates using `openspec instructions` for your specified change.

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

Yes, you can use a custom workflow schema for change management. The skill applies the default workflow schema unless a specific one is explicitly requested to guide your artifact creation process.

How do I view progress after scaffolding an OpenSpec change?▼

To view progress after scaffolding an OpenSpec change, run `openspec status --change "<name>`. This command shows your current position in the artifact workflow and what steps remain in the deterministic sequence.

What are the limitations of the OpenSpec artifact workflow scaffolding?▼

The main limitation is that the workflow scaffolding outputs guidance for artifact creation without executing artifacts. It provides progressive instructions and templates, leaving the actual artifact execution and implementation to the developer.