openspec-new-change

Scaffold OpenSpec change directories and track artifact readiness.

113|19|Updated Apr 8, 2025
One-click install
npx skills add https://github.com/goern/forgejo-mcp --skill openspec-new-change-goern
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/goern/forgejo-mcp/tree/main/.claude/skills/openspec-new-change
Command: npx skills add https://github.com/goern/forgejo-mcp --skill openspec-new-change-goern

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenSpec change orchestration helps teams quickly scaffold and manage feature work using a standardized artifact-driven workflow, reducing setup time and ensuring consistent change governance.

Core Features & Use Cases

  • Scaffolds a new OpenSpec change directory with a consistent structure.
  • Lets teams select an artifact-driven workflow schema and monitor readiness across artifacts.
  • Provides templates and guidance to drive discussions with stakeholders and implement the change.

Quick Start

To begin a new change using this skill, run the following commands: openspec new change "<name>" openspec status --change "<name>" openspec instructions <first-artifact-id> --change "<name>"

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 directory for feature development?

To scaffold an OpenSpec change, run the `openspec new change` command to automatically generate a standardized directory structure for managing feature proposals and artifact definitions. This establishes a consistent baseline for tracking feature readiness.

What is the artifact workflow in OpenSpec change management?

The OpenSpec artifact workflow is an experimental schema that structures feature proposals through defined artifacts. It standardizes change governance by generating templates and monitoring readiness across each artifact required for implementation.

Do I need the OpenSpec CLI to manage feature proposals and track readiness?

Yes, the OpenSpec CLI is required to orchestrate changes, scaffold directories, and execute status checks. You use it to select an artifact-driven workflow schema and monitor the readiness of artifacts throughout the feature lifecycle.

How do I monitor readiness across artifacts for an OpenSpec change?

You monitor artifact readiness by running `openspec status --change` to view the workflow schema progress. The CLI tracks completion across generated artifacts, ensuring all defined governance steps are satisfied before implementation.

How do I generate implementation instructions for a specific OpenSpec artifact?

To generate instructions for a specific artifact, run `openspec instructions <artifact-id> --change`. This provides targeted templates and guidance to drive stakeholder discussions and implement the selected feature change.

Can I use OpenSpec change orchestration to standardize governance for product teams?

Yes, OpenSpec change orchestration is designed for product teams and developers to standardize feature governance. It reduces setup time by applying a consistent artifact-driven workflow schema to scaffold and track new feature changes.