skills.rest
roger8b
roger8bCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Create a new OpenSpec change using a structured artifact-driven workflow.

Updated Mar 8, 2026
Search Tags:#change management#OpenSpec#codebase management#structured workflow#artifact-driven development
One-click install
npx skills add https://github.com/roger8b/slideflow --skill openspec-new-change-roger8b
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/roger8b/slideflow/tree/main/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/roger8b/slideflow --skill openspec-new-change-roger8b

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of starting a new OpenSpec change with a structured, step-by-step process for creating features, fixes, or modifications.

Core Features & Use Cases

  • Structured Change Creation: Guides users through creating a new OpenSpec change with an artifact-driven approach.
  • Schema Workflow: Offers a default workflow schema or allows selection of a specific one based on user input.
  • Change Tracking: Provides a clear view of the change's status and artifact requirements.

Quick Start

Start a new change in OpenSpec by naming your change and initiate the process with the command: 'start new change <change-name>'.

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?▼

Start a new change in OpenSpec by using the command 'start new change <change-name>'. This initiates a structured, step-by-step workflow to define requirements and guide artifact-driven development.

What is artifact-driven development for codebase management?▼

Artifact-driven development in codebase management structures your workflow around defining change requirements and specific artifacts. OpenSpec uses this approach to provide clear tracking of change status and artifact requirements.

Do I need OpenSpec CLI to create a structured change?▼

Yes, OpenSpec CLI is a required dependency to initiate a new change. It provides the underlying command execution and environment support necessary for the structured change creation process.

Can I define change requirements before modifying my codebase?▼

Yes, OpenSpec guides you through defining change requirements before codebase modifications. It assists in determining the workflow schema and outlines necessary artifacts prior to implementation.

What is the best way to track a codebase modification workflow?▼

The best way to track a codebase modification workflow is using OpenSpec's structured change creation. It provides a clear view of the change's status and artifact requirements throughout the development lifecycle.

Related Skills

Explore More Software Engineering Skills→
ywh0606ywh0606

opsx-new

Create OpenSpec change directories from kebab-case change names.

Community
Basic
ywh0606ywh0606

opsx-new-change

Create OpenSpec change directories and retrieve artifact instructions via the openspec CLI.

Community
Intermediate
roger8broger8b

openspec-continue-change

Generate OpenSpec change artifacts to continue workflow progression.

Community
Intermediate
hossam7amdyhossam7amdy

openspec-new-change

Scaffold a new OpenSpec change using the experimental artifact workflow.

Community
Advanced