openspec-new-change

Scaffold new OpenSpec changes with schema selection and first artifact templates.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/whatevertogo/Astrcode --skill openspec-new-change-whatevertogo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/whatevertogo/Astrcode/tree/main/.codex/skills/openspec-new-change
Command: npx skills add https://github.com/whatevertogo/Astrcode --skill openspec-new-change-whatevertogo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides users through starting a new OpenSpec change using an artifact-driven workflow to eliminate manual scaffolding, schema selection, and initial artifact discovery steps that are error-prone or unfamiliar.

Core Features & Use Cases

  • Scaffold and initialize: Create a new change directory with openspec and optionally apply a specified schema.
  • Inspect artifact status: Show which artifacts are ready and which need creation, and surface the template for the first ready artifact.
  • Interactive validation and guardrails: Validate kebab-case names, detect existing changes, avoid creating artifacts, and require explicit user confirmation before proceeding.
  • Use Case: When starting a new feature or fix, use this Skill to get a scaffolded change, review the artifact sequence, and obtain the first artifact template to begin drafting.

Quick Start

Create a new change named add-user-auth using the artifact workflow and show me the template for the first ready artifact.

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 workflow?

You can scaffold a new OpenSpec change by running the openspec CLI to initialize the change directory, validate the kebab-case name, select a schema, and return the first artifact template for drafting.

What is the artifact-driven workflow in OpenSpec change management?

The artifact-driven workflow in OpenSpec sequences required artifacts for a change, tracks their readiness status, and surfaces the template for the first ready artifact so you can begin drafting immediately without manual scaffolding.

Does the OpenSpec change scaffold require the openspec CLI?

Yes, scaffolding an OpenSpec change requires the openspec CLI to initialize the change directory, apply the chosen schema, and retrieve the artifact sequence and first ready artifact template.

How do I validate change names when creating a new OpenSpec change?

When creating an OpenSpec change, the workflow enforces kebab-case name validation, detects existing changes to prevent conflicts, and requires explicit user confirmation before proceeding with the scaffold.

Can I create artifacts while initializing an OpenSpec change scaffold?

No, the OpenSpec change scaffold workflow explicitly avoids creating artifacts during initialization. Instead, it returns the template for the first ready artifact, leaving the actual artifact creation to the user.