openspec-new-change

Creates scaffolded workflows for managing agile project portfolios and products.

Updated Aug 23, 2026

Search Tags:#workflow #scaffold #openspec #change-management #feature-development #artifact-workflow

Ready to run

npx skills add https://github.com/terry90918/horse-blessing-2026 --skill openspec-new-change-terry90918

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/terry90918/horse-blessing-2026/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/terry90918/horse-blessing-2026 --skill openspec-new-change-terry90918

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often struggle to start OpenSpec changes consistently, wasting time on setup and alignment.

Core Features & Use Cases

Structured scaffold: creates a new change directory at openspec/changes/<name>/ with a ready-to-use skeleton.
Workflow guidance: prompts for naming, selecting a schema, and obtaining first-artifact instructions.
Guardrails and status checks: standardizes the initial workflow and keeps teams aligned on artifact sequencing.

Quick Start

Run openspec new change "<name>" to scaffold a new change and follow the prompts to define the workflow and first artifact.

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 feature development?▼

To scaffold an OpenSpec change, run the new change command with a chosen name. It generates a structured directory skeleton at openspec/changes/<name> with guided prompts for naming, workflow schema selection, and first-artifact instructions.

What is the OpenSpec artifact-driven workflow and when do I need it?▼

The OpenSpec artifact-driven workflow standardizes feature development, fixes, and modifications by guiding teams through structured artifact sequencing. It is needed when aligning teams on consistent change management scaffolds to reduce setup time.

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

Yes, you can request a specific workflow schema during the scaffolding process. The system uses the default workflow schema for artifact sequencing unless a specific schema is explicitly requested.

How do I initialize the first artifact after creating an OpenSpec change directory?▼

After creating the OpenSpec change directory, follow the guided prompts to define the workflow and obtain first-artifact instructions. These prompts provide status checks and guardrails for standardizing the initial workflow setup.

What's the best way to manage OpenSpec change scaffolding across feature, fix, and modification requests?▼

The best way to manage OpenSpec change scaffolding is using guided workflows that prompt for naming and schema selection. This ensures consistent artifact sequencing across feature, fix, and modification requests while maintaining status checks.

Why does my OpenSpec change scaffold need status checks and guardrails?▼

OpenSpec change scaffolds need status checks and guardrails to keep teams aligned on artifact sequencing. This standardizes the initial workflow, preventing inconsistencies when creating structured change directories for feature development.