skills.rest
artagon
artagonOFFICIAL
Explore all skills by this author →
WebsiteGitHub

openspec-new-change

Create an OpenSpec change directory from a natural-language request.

Updated Nov 12, 2025
Search Tags:#openspec#artifact workflow#developer automation#spec templates#change scaffolding#workflow schema
One-click install
npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-new-change-artagon
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/artagon/artagon-vscode-profiles/tree/main/agents/skills/openspec-new-change
Command: npx skills add https://github.com/artagon/artagon-vscode-profiles --skill openspec-new-change-artagon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns a user’s idea into a correctly scaffolded OpenSpec change using an artifact-driven workflow, so you don’t have to guess the setup steps or artifacts sequence.

Core Features & Use Cases

  • Start a structured OpenSpec change: Creates a new change directory from a kebab-case name or derived description, using the experimental artifact workflow.
  • Select the right workflow schema: Uses the default schema unless the user explicitly requests a different one or asks to list available schemas.
  • Guide artifact creation safely: Shows artifact readiness, then outputs instructions/templates for only the first “ready” artifact without creating anything automatically.
  • Use Case: When you want to add a new feature or fix by following an opinionated sequence (proposal/spec-driven), letting the workflow tell you what to write first.

Quick Start

Ask the assistant: “Start an OpenSpec change for add user authentication, using the default workflow schema.”

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 from a feature request?▼

To scaffold an OpenSpec change, provide a natural-language request to generate a kebab-case directory name. The workflow then applies schema-aware scaffolding to output ordered artifact instructions for the first ready template.

What is the artifact-driven workflow for spec templates?▼

The artifact-driven workflow is an opinionated sequence showing artifact readiness and outputting instructions for only the first ready spec template. It enforces no-artifact creation beyond templates to guide structured proposal creation.

Do I need the openspec CLI to create a new change directory?▼

Yes, you need the openspec CLI for change creation. The Skill relies on the CLI to inspect status and retrieve instructions for the first ready artifact while enforcing no automatic artifact creation beyond templates.

Can I select a different workflow schema for change scaffolding?▼

Yes, you can request a specific workflow schema or ask to list available schemas during change scaffolding. If no schema is explicitly selected, the workflow applies the default schema to generate artifact instructions.

Why does the workflow only show instructions for the first ready artifact?▼

The workflow outputs only the first ready artifact to guide creation safely and sequentially. It enforces no-artifact creation beyond templates, preventing automatic generation of all artifacts out of order.

Related Skills

Explore More Software Engineering Skills→
JanuaryLabsJanuaryLabs
4

openspec-new-change

Scaffold OpenSpec change directories and retrieve the first artifact template.

Official
Intermediate
wtg42wtg42

openspec-continue-change

Create the next OpenSpec change artifact from CLI status and dependencies.

Community
Intermediate
JamesPrialJamesPrial
3

go-linting

Route Go linting tasks to vet, staticcheck, and golangci-lint.

Community
Intermediate
ywh0606ywh0606

opsx-ff-change

Create OpenSpec implementation artifacts from feature requests using the openspec CLI.

Community
Intermediate