skills.rest
em-jones
em-jonesCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

openspec-new-change

Initiates a new OpenSpec change via an artifact-driven workflow.

1|Updated Feb 13, 2026
Search Tags:#development workflow#change management#openspec#artifact-driven#epic tracking#schema selection
One-click install
npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-new-change-em-jones
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/em-jones/staccato-toolkit/tree/main/.opencode/skills/openspec-new-change
Command: npx skills add https://github.com/em-jones/staccato-toolkit --skill openspec-new-change-em-jones

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the creation of new changes within the OpenSpec framework, ensuring a structured and consistent approach to feature development, bug fixes, and modifications.

Core Features & Use Cases

  • Guided Change Creation: Initiates a new change with a step-by-step, artifact-driven workflow.
  • Schema Selection: Supports default and custom workflow schemas for diverse development needs.
  • Dependency Management: Integrates with td for epic tracking and artifact management.
  • Use Case: A developer needs to add a new authentication module. This Skill guides them through creating the necessary artifacts, associating it with an epic, and generating the initial 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 create a new OpenSpec change for feature development?▼

To create a new OpenSpec change, this Skill guides you through an artifact-driven workflow: defining a change name, selecting a workflow schema, acquiring an epic ID, and generating the initial proposal directory and instructions.

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

An artifact-driven workflow structures change management by guiding you through creating specific artifacts sequentially. It ensures consistent development by associating changes with an epic ID and providing instructions for each required artifact step.

Do I need the OpenSpec CLI and td tool to track epics?▼

Yes, you need the OpenSpec CLI to initiate the change directory and the `td` tool for epic management. These dependencies are required to acquire epic IDs and integrate task tracking into the artifact workflow.

Can I use a custom workflow schema when starting a new OpenSpec change?▼

Yes, you can use a custom workflow schema. The Skill supports both default and custom schema selection during the change creation process, allowing you to adapt the artifact workflow to diverse development needs.

How do I get instructions for the first artifact after creating a change directory?▼

After defining the change name, selecting a schema, and creating the change directory, the Skill automatically obtains and provides instructions for the first artifact, guiding you to generate the initial proposal.

Related Skills

Explore More Software Engineering Skills→
em-jonesem-jones
1

openspec-apply-change

Implement OpenSpec change tasks and update progress via TD CLI.

Community
Advanced
Zouu-XZouu-X

openspec-new-change

Creates a new change directory and initiates artifact-driven workflow in OpenSpec framework.

Community
Intermediate
Covcloud-LLCCovcloud-LLC

pjm

Coordinate multi-session AI development workflows across git repositories.

Official
Advanced
sgiathsgiath
4

openspec-new-change

Scaffold a new OpenSpec change directory with an artifact-driven workflow.

Community
Intermediate