openspec-new-change

Initiate new changes in the OpenSpec framework with an artifact-driven workflow.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/hiro1989/copy-path-for-claude-code --skill openspec-new-change-hiro1989
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/hiro1989/copy-path-for-claude-code/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/hiro1989/copy-path-for-claude-code --skill openspec-new-change-hiro1989

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec.

What problem does it solve?

This Skill streamlines the creation of new changes within the OpenSpec framework, ensuring a structured and artifact-driven approach for features, fixes, or modifications.

Core Features & Use Cases

  • Initiates structured changes: Creates a new change directory with a chosen schema.
  • Guides artifact creation: Identifies and provides instructions for the first artifact in the workflow.
  • Use Case: When you need to implement a new user authentication feature, this Skill will set up the necessary structure and guide you through the initial proposal artifact.

Quick Start

Use the openspec-new-change skill to start a new change for adding user authentication.

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 change in OpenSpec for feature development?

To start a new OpenSpec change, use this Skill to create a structured change directory with a chosen schema, which then guides you through creating the initial artifact for your feature development workflow. It requires the OpenSpec CLI to manage directories and artifacts.

What is an artifact-driven workflow for managing code changes?

An artifact-driven workflow structures change management by requiring step-by-step artifact creation within a dedicated change directory. This approach scopes feature development, bug fixes, and modifications into a tracked, sequential process managed by the OpenSpec CLI.

Do I need the OpenSpec CLI to create new change directories?

Yes, the OpenSpec CLI is required to create new change directories and manage artifacts. This Skill initiates the structured workflow and provides instructions for the first artifact, but the CLI handles the underlying directory and artifact management operations.

Can I use this structured change workflow for bug fixes and modifications?

Yes, this workflow scopes to feature development, bug fixes, and modifications requiring a structured approach. It initiates a new change directory with a chosen schema and guides you through the initial proposal artifact for any of these use cases.

What's the best way to structure a new user authentication feature in OpenSpec?

The best way to structure a new feature like user authentication is to use this Skill to set up the necessary change directory and schema. It then identifies and provides instructions for creating the first proposal artifact in the workflow.