openspec-new-change

Scaffold an OpenSpec change directory and fetch the first artifact template.

Updated Dec 25, 2025
One-click install
npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-new-change-wtg42
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/wtg42/tty-clock-timer/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/wtg42/tty-clock-timer --skill openspec-new-change-wtg42

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, artifact-driven process to start a new OpenSpec change so users can consistently scaffold and prepare the first artifact for a feature, fix, or modification without accidentally creating artifacts prematurely.

Core Features & Use Cases

  • Guided Change Creation: Prompts for a valid kebab-case change name or derives one from a user description, validates naming, and checks for existing changes.
  • Workflow Selection & Discovery: Uses the default schema unless the user requests a specific schema, with instructions to list available schemas when asked.
  • Artifact Preparation: Runs openspec commands to scaffold the change, show artifact status, and fetch the template and context for the first ready artifact so the user can author it.
  • Use Case: A developer wants to propose "add-user-auth" as a new feature; this Skill scaffolds openspec/changes/add-user-auth, shows which artifacts are required, and provides the template for the first artifact.

Quick Start

Start a new OpenSpec change named add-user-auth using the default experimental artifact workflow and show the template for the first 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 change directory for an OpenSpec feature proposal?

You can scaffold an OpenSpec change by providing a kebab-case name or a feature description. The process validates naming, checks for existing changes, and creates the directory structure using the openspec CLI.

What is an artifact-driven workflow and when do I need it for software changes?

An artifact-driven workflow structures software changes by requiring specific artifacts to be authored in sequence. You need it when initiating features, bug fixes, or modifications to ensure consistent documentation and preparation before implementation begins.

Does OpenSpec create artifacts automatically when scaffolding a change?

No, OpenSpec does not create artifacts automatically when scaffolding a change. It creates the directory structure, displays artifact status, and retrieves the template and context for the first ready artifact so you can author it manually.

Can I use a specific schema instead of the default for OpenSpec change creation?

Yes, you can request a specific schema for OpenSpec change creation. The default schema is applied automatically unless you specify otherwise, and you can ask to list available schemas to choose the appropriate workflow for your project.

What naming conventions are required for a new OpenSpec change directory?

OpenSpec change directories require valid kebab-case naming, such as 'add-user-auth'. The name can be provided directly or derived from a feature description, and the workflow validates it against existing changes to prevent conflicts.

How do I check the artifact status after creating an OpenSpec change scaffold?

After scaffolding an OpenSpec change, the workflow runs openspec commands to show artifact status automatically. This displays which artifacts are required for your change and fetches the template for the first ready artifact to begin authoring.