openspec-new-change

Scaffold a new OpenSpec change directory with a selected workflow.

84|18|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/intent-driven-dev/openspec-schemas --skill openspec-new-change-intent-driven-dev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/intent-driven-dev/openspec-schemas/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/intent-driven-dev/openspec-schemas --skill openspec-new-change-intent-driven-dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams bootstrap a new OpenSpec change using a structured, artifact-driven workflow, ensuring guardrails and clear steps without executing artifacts prematurely.

Core Features & Use Cases

  • Scaffold a new change directory at openspec/changes/<name>/ with the selected workflow and default schema.
  • Present a status overview of artifacts needed and which are ready, so teams can plan next steps without risking partial builds.
  • Provide first-artifact instructions and guardrails to stop after guidance, enabling safe, incremental progress.

Quick Start

Describe your change goal and I will scaffold the OpenSpec change with the first artifact plan.

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 with a guided workflow?

To scaffold an OpenSpec change, the skill creates a directory at openspec/changes/<name>/ using an artifact-driven workflow, applying the selected workflow and default schema to structure your change safely.

What is an artifact-driven workflow for managing code changes?

An artifact-driven workflow ensures features and fixes are built incrementally by checking artifact readiness, providing guardrails, and pausing for user direction before any artifacts are produced.

How do I check which artifacts are ready before building a feature in OpenSpec?

You can check artifact readiness by viewing the status overview provided during the workflow setup, which details which artifacts are needed and which are ready to help you plan next steps safely.

Does the OpenSpec change scaffold generate artifacts automatically?

No, the scaffold does not generate artifacts automatically. It provides first-artifact instructions and guardrails, then pauses for user direction to ensure safe, incremental progress without premature execution.

Can I use this guided workflow for both features and fixes in OpenSpec projects?

Yes, the guided workflow applies to teams creating both features and fixes in OpenSpec projects, ensuring structured scaffolding and artifact readiness checks for any type of change.

When should I avoid using an artifact-driven scaffold for OpenSpec changes?

You should avoid using this scaffold if your project does not require strict guardrails or artifact readiness checks, as it intentionally pauses execution to enforce incremental, safe progress.