openspec-new-change

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

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/yandiaan/penginfo-handal-hackathon --skill openspec-new-change-yandiaan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/yandiaan/penginfo-handal-hackathon/tree/main/.qoder/skills/openspec-new-change
Command: npx skills add https://github.com/yandiaan/penginfo-handal-hackathon --skill openspec-new-change-yandiaan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start a new change using the experimental artifact-driven workflow to structure feature requests, fixes, or modifications with a guided, step-by-step approach.

Core Features & Use Cases

  • Provides a repeatable scaffold for OpenSpec changes, including status visibility and first-artifact instructions.
  • Enforces guardrails like input validation, schema choice, and explicit user direction before artifact creation.
  • Useful for teams adopting artifact-driven development to standardize change creation and tracking.

Quick Start

Initiate a new OpenSpec change by providing a kebab-case name and follow the artifact-driven workflow to scaffold the change.

Frequently Asked Questions about openspec-new-change

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a new OpenSpec change for a feature request?▼

To create a new OpenSpec change, provide a kebab-case name and follow the artifact-driven workflow to scaffold the change with step-by-step guidance, status visibility, and first-artifact instructions.

What is the artifact-driven workflow for software change management?▼

The artifact-driven workflow is a guided, step-by-step process for structuring software changes. It standardizes change creation by enforcing input validation, schema selection, and artifact statuses before any modification is applied.

How do I scaffold a code modification using a structured template?▼

You can scaffold a code modification by initiating an OpenSpec change with a kebab-case name, which applies a first-artifact template and enforces guardrails to structure the modification process.

Does the OpenSpec change workflow validate inputs before creating artifacts?▼

Yes, the OpenSpec workflow enforces input validation, schema choice, and explicit user direction. It stops before artifact creation until the user provides the necessary guidance for the software change.

Can I use this scaffolding workflow for both bug fixes and new features?▼

Yes, the workflow applies to development projects requiring a guided process to structure new features, bug fixes, or modifications using artifact statuses and a standardized template.

What are the limitations of artifact-driven development for change management?▼

A key limitation is that the workflow stops before artifact creation until explicit user direction is provided, requiring manual input to proceed through the schema selection and validation steps.