skills.rest
knopki
knopkiCOMMUNITY
Explore all skills by this author →
𝕏@knopkiGitHub

openspec-new-change

Scaffold new OpenSpec change directories using the OpenSpec CLI.

1|Updated Jun 18, 2025
Search Tags:#workflow#development#scaffolding#change management#openspec
One-click install
npx skills add https://github.com/knopki/dotfiles --skill openspec-new-change-knopki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/knopki/dotfiles/tree/main/home/private_dot_config/opencode/skills/openspec-new-change
Command: npx skills add https://github.com/knopki/dotfiles --skill openspec-new-change-knopki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of starting new development changes within the OpenSpec framework, ensuring a structured and consistent approach to feature development and bug fixing.

Core Features & Use Cases

  • New Change Creation: Generates a new, scaffolded change directory based on user input.
  • Workflow Schema Selection: Allows for the use of default or specific workflow schemas for structured development.
  • Use Case: When a developer needs to implement a new user authentication feature, they can use this Skill to initiate the change, setting up the necessary directory structure and workflow according to OpenSpec standards.

Quick Start

Start a new OpenSpec 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 scaffold a new OpenSpec change directory for a feature?▼

To scaffold a new OpenSpec change directory, you initiate a new change using an artifact-driven workflow, which sets up the necessary directory structure and workflow according to OpenSpec standards.

What is the OpenSpec artifact-driven workflow used for?▼

The OpenSpec artifact-driven workflow is used to initiate new development changes, ensuring a structured and consistent approach to creating new features, fixes, or modifications.

Do I need the OpenSpec CLI to start a new change?▼

Yes, you need the OpenSpec CLI to start a new change, as it is required to scaffold new change directories and manage the artifact workflows.

Can I select a specific workflow schema when creating an OpenSpec change?▼

Yes, when creating an OpenSpec change, you can select specific workflow schemas for structured development, or you can use the default schema provided by the framework.

What's the best way to initiate a bug fix within the OpenSpec development process?▼

The best way to initiate a bug fix within the OpenSpec development process is to use this scaffolding workflow to generate a new change directory that manages the modification artifacts.

Why does starting a new OpenSpec change require scaffolding?▼

Starting a new OpenSpec change requires scaffolding to streamline the development process, ensuring that all new features and bug fixes follow a structured directory layout and consistent artifact workflow.

Related Skills

Explore More Software Engineering Skills→
studyzystudyzy
10.2k

openspec-new-change

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

Community
Advanced
woutervanranstwoutervanranst
1

openspec-new-change

Scaffold a new OpenSpec change with a kebab-case name under openspec/changes.

Community
Intermediate
YangYuS8YangYuS8

openspec-continue-change

Generate the next OpenSpec change artifact from completed dependencies.

Community
Advanced
TbK0ngTbK0ng
1

openspec-new-change

Create a new OpenSpec change directory with artifact workflow instructions.

Community
Intermediate