skills.rest
LippyyDev
LippyyDevCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-new-change

Scaffold OpenSpec changes with naming conventions and artifact sequencing.

1|Updated Apr 7, 2026
Search Tags:#scaffolding#cli#openspec#project-setup#change-management#artifact-workflow#feature-fix
One-click install
npx skills add https://github.com/LippyyDev/Agate-Antigravity-Helper- --skill openspec-new-change-lippyydev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/LippyyDev/Agate-Antigravity-Helper-/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/LippyyDev/Agate-Antigravity-Helper- --skill openspec-new-change-lippyydev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Starting a new OpenSpec change requires a structured approach to ensure consistency and repeatability across projects. This skill provides a guided process to initialize a change with a clear name, select the appropriate artifact workflow, and align expectations for feature requests, fixes, or modifications.

Core Features & Use Cases

  • Guided initialization: creates a scaffold for a new OpenSpec change with a standard artifact sequence.
  • Workflow consistency: enforces the default artifact workflow and naming conventions to reduce ambiguity across teams.
  • First-artifact templating: offers a ready-to-run first artifact template to jumpstart the change lifecycle across OpenSpec projects.

Quick Start

Provide a kebab-case change name and I will scaffold the change using the default artifact 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?▼

Scaffolding a new OpenSpec change requires providing a kebab-case name to initialize the project structure using the default artifact-driven workflow and a ready-to-run first-artifact template.

What is the artifact-driven workflow for OpenSpec project setup?▼

The artifact-driven workflow is a structured process that sequences artifacts for feature requests, fixes, or modifications, enforcing naming conventions and consistency across OpenSpec projects.

How do I enforce naming conventions for OpenSpec feature fixes and modifications?▼

You can enforce naming conventions for OpenSpec feature fixes by using a guided initialization process that suggests standard naming formats and scaffolds changes according to default workflow rules.

Can I use this guided workflow for both feature requests and bug fixes?▼

Yes, the guided workflow supports initiating changes for feature requests, fixes, or modifications, aligning expectations and applying the appropriate artifact sequence for each change type.

Do I need any dependencies to start the OpenSpec change management workflow?▼

No dependencies are required to start the OpenSpec change management workflow; you only need to provide a kebab-case change name to generate the initial scaffold and first artifact.

Related Skills

Explore More Software Engineering Skills→
moltbook-experimentsmoltbook-experiments
3

openspec-new-change

Bootstrap a new OpenSpec change with kebab-case naming and schema selection.

Official
Intermediate
Yager-42Yager-42

openspec-continue-change

Generate the next OpenSpec change artifact from completed artifacts.

Community
Advanced
johnqxujohnqxu

openspec-ff-change

Generate OpenSpec change artifacts from a user-provided change description.

Community
Advanced
sgiathsgiath
4

openspec-new-change

Scaffold a new OpenSpec change directory with an artifact-driven workflow.

Community
Intermediate