openspec-new-change

Scaffold new changes in the OpenSpec framework with artifact-driven workflows.

3|Updated Jan 27, 2026

Search Tags:#workflow #development #scaffolding #change management #openspec #artifact-driven

Ready to run

npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill openspec-new-change-agentic-engineering-agency

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/Agentic-Engineering-Agency/specsafe/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/Agentic-Engineering-Agency/specsafe --skill openspec-new-change-agentic-engineering-agency

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the initiation of new changes within the OpenSpec framework, ensuring a structured and artifact-driven approach to development.

Core Features & Use Cases

Initiates New Changes: Creates a new, scaffolded change directory based on user input.
Workflow Selection: Supports default and custom workflow schemas (e.g., TDD).
Artifact Guidance: Provides instructions for creating the first artifact in the chosen workflow.
Use Case: A developer needs to add a new authentication feature. They use this Skill to start the process, getting a clear path and initial instructions for defining the feature's specification.

Quick Start

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

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 an artifact-driven development workflow?▼

To start a new change in an artifact-driven workflow, you provide a change name or description to scaffold the necessary directory structure and generate initial artifact templates.

What is an artifact-driven workflow for change management?▼

An artifact-driven workflow for change management structures development around generating specification files and templates, ensuring new features are defined by concrete artifacts created in a scaffolded directory before implementation begins.

Do I need the openspec CLI installed to scaffold new change directories?▼

Yes, the openspec CLI must be installed and configured to scaffold new change directories, as it provides the underlying framework required to determine the workflow schema and generate the artifact structure.

Can I use a custom workflow schema like TDD when scaffolding a new change?▼

Yes, custom workflow schemas like TDD are supported when scaffolding a new change. The skill determines the appropriate workflow schema from your input and provides specific instructions for creating the first artifact.

What is the best way to define a new feature specification using OpenSpec?▼

The best way to define a new feature specification using OpenSpec is to scaffold the change directory and follow the provided artifact templates, ensuring your feature definition follows a structured, artifact-driven path.

Why use an artifact-driven approach for starting new development changes?▼

Using an artifact-driven approach for starting new development changes ensures a structured path for defining specifications, streamlining the initiation process by providing clear templates and directory scaffolding for new features.