skills.rest
open-platform-model
open-platform-modelOFFICIAL
Explore all skills by this author →
GitHub

openspec-new-change

Scaffold a new OpenSpec change workflow from user input.

Updated Dec 8, 2025
Search Tags:#workflow#cli#scaffold#openspec#artifact#change
One-click install
npx skills add https://github.com/open-platform-model/cli --skill openspec-new-change-open-platform-model
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/open-platform-model/cli/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/open-platform-model/cli --skill openspec-new-change-open-platform-model

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates scaffolding a new OpenSpec change workflow from user input, reducing manual setup and ensuring a repeatable process for feature work and fixes.

Core Features & Use Cases

  • Guided change scaffolding: creates a structured change layout under openspec/changes/<name>, ready for artifact work.
  • Artifact-driven workflow: supports an artifact-centric process with optional schemas and status checks.
  • Fosters consistency: enforces naming conventions and a repeatable kickoff procedure for teams.

Quick Start

Provide a clear change name in kebab-case to scaffold a new OpenSpec change.

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 workflow for feature planning?▼

Scaffolding an OpenSpec change workflow requires providing a kebab-case change name to generate a structured skeleton under openspec/changes/<name>. This automates the directory layout and enforces naming conventions without creating the actual artifacts.

What is an artifact-driven workflow and when do I need it for software fixes?▼

An artifact-driven workflow structures feature work or fixes around sequential artifacts with optional schemas and status checks. You need it when planning changes that require a repeatable kickoff procedure and consistent artifact sequencing across a software team.

Does the OpenSpec change scaffolding process create artifacts automatically?▼

No, the OpenSpec scaffolding process does not create artifacts automatically. It generates a change skeleton, enforces a default workflow schema, and reports readiness, leaving the actual artifact creation to the user.

How do I ensure consistent naming conventions when creating OpenSpec changes?▼

To ensure consistent naming conventions when creating OpenSpec changes, use the guided scaffolding process which enforces kebab-case naming. This reduces manual setup errors and standardizes the kickoff procedure for software teams.

Can I select a custom schema during the OpenSpec change workflow setup?▼

Yes, the OpenSpec change workflow setup supports optional schema selection during the guided scaffolding process. This allows teams to apply specific artifact-driven schemas while maintaining a default workflow structure.

What are the limitations of using a CLI scaffold for OpenSpec change workflows?▼

A limitation of using a CLI scaffold for OpenSpec change workflows is that it only generates the directory layout and reports readiness. It does not create the actual artifacts, requiring manual artifact population afterward.

Related Skills

Explore More Product & Management Skills→
moltbook-experimentsmoltbook-experiments
3

openspec-new-change

Bootstrap a new OpenSpec change with kebab-case naming and schema selection.

Official
Intermediate
psaccpsacc

openspec-ff-change

Generate OpenSpec change artifacts in dependency order until apply-ready.

Community
Intermediate
Max-LooMax-Loo
2

openspec-continue-change

Create the next OpenSpec change artifact after checking status and dependencies.

Community
Advanced
tim-hubtim-hub
2

openspec-new-change

Scaffold an OpenSpec change directory without generating artifacts.

Community
Intermediate