openspec-new-change

Scaffold a new OpenSpec change directory with schema and status tracking.

10.2k|702|Updated Apr 12, 2012
One-click install
npx skills add https://github.com/studyzy/imewlconverter --skill openspec-new-change-studyzy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/studyzy/imewlconverter/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/studyzy/imewlconverter --skill openspec-new-change-studyzy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides teams to start a new OpenSpec change using a structured, artifact-driven workflow that ensures consistent scoping and progress tracking across initiatives.

Core Features & Use Cases

  • Guided change initiation: prompts for a change name and scaffolds a new OpenSpec change under openspec/changes/<name>.
  • Schema-aware workflow: uses the default workflow unless a specific schema is requested, enabling rapid prototyping and controlled variation.
  • Status and artifact guidance: reports current progress and provides instructions for the first artifact when ready, keeping teams aligned.

Quick Start

Start a new OpenSpec change named openspec-new-change using the default workflow to scaffold the change directory and initial artifacts.

Frequently Asked Questions about openspec-new-change

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

FAQPage Schema
How do I start a new OpenSpec change with a structured workflow?

To start an OpenSpec change, the skill guides you through naming, scaffolding the openspec/changes/<name> directory, and selecting a schema to initiate the artifact-driven workflow.

What is an artifact-driven workflow for change management?

An artifact-driven workflow manages change initiatives by generating structured templates and tracking readiness status, ensuring consistent scoping and progress alignment across teams.

Do I need the OpenSpec CLI installed to scaffold change directories?

Yes, the OpenSpec CLI is a required dependency. It must be installed locally to scaffold the change directory and generate the initial artifact templates.

Can I use a custom schema for OpenSpec change scaffolding?

Yes, you can specify a custom schema during change initiation. The workflow applies the default schema unless an alternative is requested for controlled variation.

How does OpenSpec track the status of a new feature or fix?

OpenSpec tracks status by reporting current progress after scaffolding. It provides instructions for the first artifact when ready, keeping teams aligned throughout the change lifecycle.

What is the best way to manage scoping for new feature additions in OpenSpec?

The best way is using guided change initiation. It prompts for a change name, scaffolds the directory structure, and outputs the first artifact template to ensure consistent scoping.