skills.rest
AGIBuild
AGIBuildCOMMUNITY
Explore all skills by this author →
GitHub

openspec-new-change

Initiate a new OpenSpec change with artifact status tracking.

10|Updated Jan 28, 2026
Search Tags:#workflow#cli#development process#change management#openspec#artifact
One-click install
npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill openspec-new-change-agibuild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/AGIBuild/Agibuild.Fulora/tree/main/.cursor/skills/openspec-new-change
Command: npx skills add https://github.com/AGIBuild/Agibuild.Fulora --skill openspec-new-change-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users initiate a new change within the OpenSpec system using a structured, artifact-driven workflow, ensuring a consistent and traceable process for new features, fixes, or modifications.

Core Features & Use Cases

  • Initiate New Changes: Starts a new change with a user-defined name.
  • Workflow Schema Selection: Uses a default schema or allows users to specify a different workflow.
  • Artifact Status Tracking: Shows the status of artifacts required for the change.
  • Instruction Generation: Provides templates and context for creating the first artifact.
  • Use Case: A developer needs to add a new authentication module. They use this Skill to create a new change, get the initial instructions for the proposal artifact, and then proceed to draft the proposal.

Quick Start

Start a new OpenSpec change for adding user authentication.

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 change in OpenSpec for a new feature?▼

To start a new change in OpenSpec, you initiate the process using an artifact-driven workflow with a user-defined name. The system then generates status updates and instructions for creating the initial proposal artifact.

What is an artifact-driven workflow in software change management?▼

An artifact-driven workflow structures software development changes by requiring specific artifacts, like proposals, to be created and tracked. This ensures a consistent, traceable process for new features or fixes within the OpenSpec system.

Do I need the openspec CLI tool to create a new change?▼

Yes, you need the openspec CLI tool installed to execute the commands that initiate a new change. The Skill relies on this CLI tool to process the workflow schema selection and start the artifact generation.

Can I select a custom workflow schema when initiating an OpenSpec change?▼

Yes, you can specify a custom workflow schema when initiating a new OpenSpec change. If no custom schema is provided, the system defaults to a standard schema to guide the artifact creation process.

What is the best way to track artifact status during a development process change?▼

The best way to track artifact status is by initiating the change through the OpenSpec system, which automatically shows the status of required artifacts. This provides structured tracking throughout the development process.

Related Skills

Explore More Software Engineering Skills→
moltbook-experimentsmoltbook-experiments
3

openspec-new-change

Bootstrap a new OpenSpec change with kebab-case naming and schema selection.

Official
Intermediate
agentxmagentxm
5

openspec-new-change

Scaffold OpenSpec change directories with guided artifact workflows.

Official
Intermediate
TranVanTienDatTranVanTienDat

openspec-new-change

Start a new OpenSpec change by selecting a schema and creating artifacts.

Community
Intermediate
HsienWHsienW
63

openspec-continue-change

Create the next artifact in an OpenSpec change sequence.

Community
Intermediate