openspec-new-change

Initialize an OpenSpec change workflow with schema selection and status checks.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Rushtu99/Codex-ReVamped --skill openspec-new-change-rushtu99
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/Rushtu99/Codex-ReVamped/tree/main/.agents/skills/openspec-new-change
Command: npx skills add https://github.com/Rushtu99/Codex-ReVamped --skill openspec-new-change-rushtu99

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a guided, safe way to initialize an OpenSpec change using the experimental artifact workflow, reducing setup overhead and ensuring consistent scaffolding.

Core Features & Use Cases

  • Guided change initialization: Sets up a new OpenSpec change with a sensible default workflow and schema.
  • Status-driven workflow: Guides the user through checking artifact readiness and obtaining the first artifact instructions, without creating artifacts yet.
  • Safe scaffolding: Enforces guardrails such as kebab-case naming and prevents overwriting existing changes.

Quick Start

Provide a kebab-case change name and a brief description to initialize the OpenSpec change workflow.

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

To scaffold a new OpenSpec change, provide a kebab-case change name and a brief description to initialize the artifact-driven workflow, which sets up the schema and status checks.

What is the artifact-driven workflow for change management?

The artifact-driven workflow is an experimental OpenSpec process that guides users through a stepwise change lifecycle, including schema selection, status reporting, and obtaining first artifact instructions without creating artifacts immediately.

Does OpenSpec change initialization require a specific naming format?

Yes, OpenSpec change initialization requires a kebab-case naming format, which acts as a safe scaffolding guardrail to prevent overwriting existing changes and ensure consistent setup.

How do I get first artifact instructions in OpenSpec?

You get first artifact instructions by initializing the change workflow with a name and description, which triggers a status-driven check that provides a ready-to-fill template for the first artifact.

What is the best way to manage feature requests and fixes in OpenSpec?

The best way to manage feature requests and fixes in OpenSpec is using the guided change initialization workflow, which safely applies a default schema and stepwise lifecycle to formal modifications.

Why does OpenSpec prevent overwriting existing changes during scaffolding?

OpenSpec prevents overwriting existing changes during scaffolding to enforce safe setup guardrails, ensuring that your artifact workflow initialization does not accidentally destroy active change proposals.