openspec-new-change

Scaffold a new OpenSpec change with the artifact-driven workflow.

Updated Mar 9, 2025
One-click install
npx skills add https://github.com/rock-hu/vitamin-compose --skill openspec-new-change-rock-hu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/rock-hu/vitamin-compose/tree/main/.qwen/skills/openspec-new-change
Command: npx skills add https://github.com/rock-hu/vitamin-compose --skill openspec-new-change-rock-hu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides users to start a new OpenSpec change using the experimental artifact-driven workflow, providing a structured, step-by-step approach for feature development or fixes.

Core Features & Use Cases

  • Guided OpenSpec change scaffolding: create a new change with an organized artifact workflow.
  • Step-by-step guidance: clear instructions for naming, workflow selection, and artifact preparation.
  • OpenSpec CLI-centric: ensures compatibility with the OpenSpec CLI and default schema workflows.

Quick Start

Use the skill to scaffold a new OpenSpec change by providing a kebab-case name, then follow the prompts:

  • Run: openspec new change "<name>"
  • Check status with: openspec status --change "<name>"
  • Retrieve first artifact instructions with: openspec instructions <first-artifact-id> --change "<name>"
  • When ready, describe what you want to achieve and I'll draft the next artifact or continue.

Frequently Asked Questions about openspec-new-change

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

FAQPage Schema
How do I start a new OpenSpec change for feature development?

To start a new OpenSpec change, use the CLI to scaffold the change with a kebab-case name, then follow the guided steps to select a workflow and prepare your first artifact. The default artifact schema structures the entire modification process.

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

The artifact-driven workflow is an experimental process that structures feature development and fixes through guided scaffolding. It uses a default schema to organize changes into sequential artifacts, ensuring systematic progression from naming to first artifact preparation.

Do I need the OpenSpec CLI to scaffold a new change?

Yes, the OpenSpec CLI is required to scaffold a new change. The skill relies on CLI commands like 'openspec new change' to initialize the workflow, check status, and retrieve instructions for the first artifact.

How do I check the status of an OpenSpec change after scaffolding?

You can check the status of an OpenSpec change by running 'openspec status --change "<name>"' in your CLI. This command tracks the progress of your artifact-driven workflow after the initial scaffolding.

Can I use OpenSpec changes for bug fixes and modifications?

Yes, OpenSpec changes apply to feature development, fixes, and modifications. The guided artifact workflow adapts to various software engineering tasks, providing structured scaffolding for any code alteration.

How do I retrieve instructions for the next artifact in an OpenSpec change?

Retrieve first artifact instructions using 'openspec instructions <first-artifact-id> --change "<name>"'. After retrieving instructions, describe your goals to draft the next artifact and continue the workflow.