openspec-new-change

Scaffold an OpenSpec change and display the first artifact template.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/chuangkevin/project-bridge --skill openspec-new-change-chuangkevin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/chuangkevin/project-bridge/tree/main/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/chuangkevin/project-bridge --skill openspec-new-change-chuangkevin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps initialize a structured, artifact-driven OpenSpec change so users can scaffold a new feature, fix, or modification with clear next steps without manually inspecting workflow requirements.

Core Features & Use Cases

  • Scaffold Creation: Creates a new change directory scaffold using the openspec CLI and identifies the first artifact to produce.
  • Workflow Guidance: Shows artifact status and prints the template/instructions for the first ready artifact so the user knows exactly what to author next.
  • Use Case: A product manager or engineer who wants to start a formal spec change (e.g., add-user-auth) can get a ready scaffold and the first artifact template without accidentally creating artifacts.

Quick Start

Use the openspec-new-change skill to start a new change by providing a kebab-case name or a description of what you want to build.

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 for a feature or fix?

To scaffold an OpenSpec change, provide a kebab-case change name or descriptive prompt. The skill creates the change directory structure and displays the first artifact template without generating any artifacts automatically.

What is an artifact-driven OpenSpec workflow?

An artifact-driven OpenSpec workflow structures feature development into sequential document artifacts. This skill initializes the workflow by scaffolding the change directory and presenting instructions for authoring the first required artifact.

Can I start a spec change without knowing the exact artifact schema?

Yes, you can start a spec change using a descriptive prompt. The skill identifies the appropriate schema, scaffolds the change directory, and presents the first artifact template to guide your authoring process.

Does the openspec-new-change skill create the artifacts for me?

No, the skill enforces guardrails to prevent automatic artifact creation. It only scaffolds the change directory and prints the template instructions for the first ready artifact, leaving the actual authoring to you.

What is the best way to initialize a structured spec change for product managers?

Product managers can initialize a structured spec change by providing a kebab-case name like add-user-auth. The skill scaffolds the directory and shows the first artifact template, clarifying exactly what needs to be authored next.

How do I know which artifact to author next in an OpenSpec change?

The skill shows artifact status and prints the template instructions for the first ready artifact. This ensures you know exactly which artifact to author next without manually inspecting workflow requirements.