openspec-new-change

Initialize an OpenSpec change scaffold with artifact-driven workflows.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/memorysaver/agentpit-gg --skill openspec-new-change
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/memorysaver/agentpit-gg/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/memorysaver/agentpit-gg --skill openspec-new-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables teams to initiate an OpenSpec change using an artifact-driven workflow, providing a structured, repeatable scaffold for new features, fixes, or modifications.

Core Features & Use Cases

  • Artifact-driven change scaffolding: Creates a scaffold at openspec/changes/<name> based on the selected workflow and validates naming.
  • Workflow selection & validation: Allows using the default workflow or a named schema, checking compatibility and readiness.
  • Status guidance: Provides commands to inspect change status and instructions for the first artifact, keeping you in control before creating any artifacts.

Quick Start

Use openspec to create a new change with a kebab-case name, then check status and fetch first-artifact instructions:

  • openspec new change "<name>"
  • openspec status --change "<name>"
  • openspec instructions <first-artifact-id> --change "<name>"
  • Ready to create the first artifact? Just describe what this change is about and I'll draft it, or ask me to continue.

Frequently Asked Questions about openspec-new-change

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

FAQPage Schema
How do I initialize a new OpenSpec change with artifact workflow?

Initialize an OpenSpec change by running `openspec new change "<kebab-case-name>"`. This scaffolds a change under openspec/changes with artifact-driven workflow support, validates naming, and guides you to inspect status and first-artifact instructions without creating artifacts yet.

What is artifact-driven workflow in OpenSpec changes?

Artifact-driven workflow structures feature development, bug fixes, and modifications through formal artifact lifecycles. Each change follows a named or default workflow schema, ensuring consistent scaffolding, validation, and guided progression from initialization through artifact creation.

Can I use a custom workflow schema or must I use the default?

You can select either the default workflow or specify a named workflow schema during change initialization. OpenSpec validates workflow compatibility and readiness before scaffolding, letting you choose the structure that fits your change type.

How do I check the status of my OpenSpec change and get artifact instructions?

Run `openspec status --change "<name>"` to inspect change status, then use `openspec instructions <first-artifact-id> --change "<name>"` to fetch first-artifact guidance. This keeps you informed before committing to artifact creation.

What naming requirements does OpenSpec enforce for new changes?

OpenSpec requires kebab-case naming for changes—lowercase words separated by hyphens (e.g., `add-user-auth`, `fix-payment-bug`). The validation occurs during initialization and ensures consistent, machine-readable change identifiers across your workflow.

Does OpenSpec change scaffolding work for feature development, bug fixes, and modifications?

Yes, artifact-driven change scaffolding applies to feature development, bug fixes, and any modifications requiring formal artifact lifecycles. The same initialization and workflow-validation process handles all three change types through configurable workflow schemas.