skills.rest
yazelin
yazelinCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-new-change

Create new OpenSpec changes with structured schemas and artifact tracking.

31|10|Updated Dec 10, 2025
Search Tags:#CLI tool#change management#OpenSpec#structured workflow#schema-driven development
One-click install
npx skills add https://github.com/yazelin/ching-tech-os --skill openspec-new-change-yazelin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/yazelin/ching-tech-os/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/yazelin/ching-tech-os --skill openspec-new-change-yazelin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

Streamlines the process of initiating new changes in OpenSpec, offering a structured and efficient way to develop new features, fixes, or modifications.

Core Features & Use Cases

  • Structured Workflows: Guided process for starting new changes with step-by-step instructions.
  • Input Validation: Assists users in defining their change clearly by providing guidance and automated naming.
  • Schema Selection: Offers the flexibility to choose between default and custom workflows based on project needs.
  • Artifact Tracking: Tracks the progress of artifacts required for a change, ensuring a smooth development process.

Quick Start

Create a new change for feature 'add user authentication' by using the command 'start change add-user-auth'.

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

To start a new OpenSpec change, use the command 'start change' followed by a kebab-case name, such as 'start change add-user-auth'. This initiates a structured workflow with step-by-step guidance and automated artifact tracking.

What is a structured workflow for change management?▼

A structured change management workflow provides a step-by-step guided process for defining modifications clearly. It uses schema selection and input validation to ensure artifacts are tracked systematically throughout feature development or bug fixes.

Can I use a custom schema for OpenSpec changes?▼

Yes, you can use a custom schema for OpenSpec changes. The workflow offers the flexibility to choose between default and custom schemas, allowing you to tailor the structured change process based on specific project needs.

Do I need the openspec CLI to create structured changes?▼

Yes, the openspec CLI is required. This workflow is designed for users familiar with the openspec CLI, depending on it to initiate changes, validate inputs, and track required artifacts systematically.

How does artifact tracking work during feature development?▼

Artifact tracking monitors the progress of required artifacts for a change, ensuring a smooth development process. It validates inputs and guides users step-by-step to guarantee all modifications are clearly defined and recorded.

When should I use a schema-driven development workflow?▼

Use a schema-driven development workflow when you need a systematic approach to feature development or bug fixes. It is ideal for streamlining new modifications by offering structured guidance, input validation, and artifact tracking.

Related Skills

Explore More Software Engineering Skills→
earchibaldearchibald
1

statusline-config

Configure the Claude statusline with a schema-driven UI and seeded config.

Community
Intermediate
icliniciclinic
9

implementing

Orchestrate subagent-driven development tasks during the implementing phase.

Official
Advanced
afadhityaafadhitya
4

openspec-continue-change

Create OpenSpec workflow artifacts and track schema progress.

Community
Advanced
pertrai1pertrai1

openspec-new-change

Initiate a new OpenSpec change and create essential artifacts via the openspec CLI.

Community
Intermediate