openspec-new-change

Scaffold a new OpenSpec change with schema selection and readiness checks.

Updated Feb 3, 2026
One-click install
npx skills add https://github.com/aniwei/vitamin-code --skill openspec-new-change-aniwei
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/aniwei/vitamin-code/tree/main/refs/opencode/.github/skills/openspec-new-change
Command: npx skills add https://github.com/aniwei/vitamin-code --skill openspec-new-change-aniwei

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines starting a new OpenSpec change by guiding you through the artifact-driven workflow, from naming to scaffolding and ready-to-fetch instructions.

Core Features & Use Cases

  • Guided change creation: Derives a kebab-case change name from user input and chooses an appropriate workflow schema.
  • Schema-aware workflow: Uses the default schema unless a specific one is requested, with an option to list available schemas.
  • Artifact readiness checks: Generates a scaffold at openspec/changes/<name> and shows artifact statuses without creating artifacts.
  • First artifact instructions: Retrieves the template and context for the first artifact based on the chosen schema.

Quick Start

Provide a kebab-case change name when prompted (e.g., 'add-new-feature'). The system will determine the workflow schema (default unless you specify otherwise) and scaffold the change at openspec/changes/<name>. Check the status with openspec status --change "<name>" and fetch the first artifact instructions with openspec instructions <artifact-id> --change "<name>".

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 OpenSpec change request for a feature or bugfix?▼

To scaffold an OpenSpec change, provide a kebab-case name and the system derives the identifier, applies the default or requested workflow schema, and generates the directory structure at openspec/changes/<name>.

What is the artifact workflow for OpenSpec change management?▼

The artifact workflow is a guided process that uses schemas to structure change requests, showing artifact readiness statuses and retrieving the first-artifact template and context without creating artifacts initially.

How do I check artifact readiness after scaffolding an OpenSpec change?▼

Run openspec status --change "<name>" to view artifact statuses for the scaffolded change, then use openspec instructions <artifact-id> --change "<name>" to fetch the first artifact template and context.

Does the OpenSpec scaffold creation process execute artifacts automatically?▼

No, the scaffold creation process does not execute artifacts. It generates the directory structure at openspec/changes/<name>, displays readiness checks, and shows the first-artifact template without creating any artifacts.

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

Yes, you can list available schemas and request a specific one when starting the change. If no schema is requested, the system automatically applies the default workflow schema to the scaffold.