openspec-new-change

Initialize OpenSpec change directories and retrieve artifact workflow instructions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers start new OpenSpec changes consistently by guiding them through the required artifact-driven workflow instead of manually creating and tracking change structures.

Core Features & Use Cases

  • Change Initialization: Creates a new OpenSpec change directory from a user-provided feature, fix, or modification request.
  • Workflow Guidance: Determines the correct schema usage, checks artifact status, and retrieves the first artifact instructions.
  • Use Case: When planning a new software feature, use this Skill to scaffold the OpenSpec change workflow and prepare the first artifact without prematurely generating implementation documents.

Quick Start

Use the openspec-new-change skill to start a new OpenSpec change for the feature or fix you want to build.

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 structured feature planning for a new software modification?

Structured feature planning starts by initializing an OpenSpec change workflow, which creates a new directory for your modification request and prepares the first artifact instructions without prematurely generating implementation documents.

How do I scaffold a new change directory for a bug fix using OpenSpec?

Scaffolding a new change directory requires the OpenSpec CLI to initialize the change from your bug fix request, determine the correct schema usage, and retrieve the first artifact workflow instructions.

What is artifact-driven development in software engineering?

Artifact-driven development is a workflow mechanism where software changes are planned and tracked through structured artifacts, ensuring consistent specification planning before any implementation documents are generated.

Do I need the OpenSpec CLI to manage feature change workflows?

Yes, the OpenSpec CLI is required to initialize new changes, inspect artifact status, determine correct schema usage, and retrieve workflow instructions for your feature planning tasks.

Can I use this approach to plan modifications without generating implementation code too early?

Yes, this workflow prepares the first artifact and guides you through the structured change process specifically to prevent prematurely generating implementation documents during feature planning.

What is the best way to manage new feature specification planning consistently?

The best way to manage feature specification planning consistently is using an artifact-driven workflow that scaffolds change directories and standardizes how modification requests are structured and tracked.