openspec-new-change

Initiate a new OpenSpec change with an artifact-driven workflow.

2.6k|399|Updated Jan 7, 2026
One-click install
npx skills add https://github.com/Soju06/codex-lb --skill openspec-new-change-soju06
Or copy as Structured Prompt for Agentâ–¼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/Soju06/codex-lb/tree/main/.agents/skills/openspec-new-change
Command: npx skills add https://github.com/Soju06/codex-lb --skill openspec-new-change-soju06

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the creation of new features, fixes, or modifications within the OpenSpec framework by initiating a structured, artifact-driven workflow.

Core Features & Use Cases

  • Initiates Structured Development: Starts a new change using a predefined or default schema for a consistent development process.
  • Guides Artifact Creation: Provides instructions and templates for the initial artifacts required for the change.
  • Use Case: A developer needs to add a new authentication module to a project. They use this Skill to create a new change, which scaffolds the necessary files and provides the first artifact's instructions, guiding them through the proposal phase.

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 OpenSpec change for feature development?â–¼

You start a new OpenSpec change by selecting or defaulting to a workflow schema, which scaffolds the initial change directory and provides instructions for the first artifact.

What is an artifact-driven workflow in change management?â–¼

An artifact-driven workflow structures development by guiding users through predefined schemas and templates for initial artifacts, ensuring consistent proposals for features, bug fixes, and modifications.

Do I need the openspec CLI to scaffold a new change directory?â–¼

Yes, the openspec CLI is required to execute the artifact-driven workflow, select a schema, and scaffold the initial change directory for your development process.

Can I use this scaffolding workflow for both bug fixes and feature modifications?â–¼

Yes, the scaffolding workflow supports feature development, bug fixes, and modifications by initiating a structured change using a predefined or default schema tailored to the task.

What happens after the initial change directory is scaffolded?â–¼

After scaffolding the change directory, the workflow provides instructions and templates for the initial artifacts required, guiding you through the proposal phase of the development process.