openspec-new-change

Scaffold a new OpenSpec change using an artifact-driven workflow.

26|1|Updated May 2, 2022
One-click install
npx skills add https://github.com/anssip/passlane --skill openspec-new-change-anssip
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/anssip/passlane/tree/main/.pi/skills/openspec-new-change
Command: npx skills add https://github.com/anssip/passlane --skill openspec-new-change-anssip

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a guided, artifact-driven process to initialize a new OpenSpec change by scaffolding the necessary directory structure, selecting the workflow schema, and presenting the first artifact template without creating anything yet.

Core Features & Use Cases

  • Scaffold a new change at openspec/changes/openspec-new-change with a standardized structure
  • Apply an experimental artifact-driven workflow to guide artifact creation
  • Preview artifact status and the first artifact template to align team expectations
  • Enforce guardrails to prevent premature artifact creation without confirmation

Quick Start

Provide a kebab-case change name to begin the artifact-driven 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 with a guided workflow?

To scaffold an OpenSpec change, provide a kebab-case change name to initialize the artifact-driven workflow. This generates the standardized directory structure at openspec/changes/ and presents the first artifact template to align team expectations.

What is an artifact-driven workflow in project management?

An artifact-driven workflow is an experimental process that guides change creation by previewing artifact status and templates before generating files. It enforces guardrails to prevent premature artifact creation without explicit confirmation.

Does the OpenSpec change workflow enforce kebab-case naming?

Yes, the OpenSpec change workflow enforces kebab-case naming for all new change scaffolding. This ensures consistent directory naming conventions across OpenSpec projects when initiating new features or modifications.

Can I preview the artifact template before creating files in OpenSpec?

Yes, you can preview the first artifact template and artifact status during the guided workflow. The process reports artifact status and presents templates without actually creating any artifacts until you confirm.

When do I need to use an artifact-driven change workflow?

You need an artifact-driven change workflow when initiating new features, fixes, or modifications across OpenSpec projects. It ensures consistent schema selection, standardized directory structure, and aligned team expectations before artifact creation.

Why does the OpenSpec scaffolding process not create artifacts automatically?

The OpenSpec scaffolding process does not create artifacts automatically because it enforces guardrails to prevent premature artifact creation. This ensures team members review the first artifact template and confirm before any files are generated.