source-command-opsx-new

Automate new change initiation with artifact-driven workflows using openspec CLI.

Updated Nov 15, 2025

Search Tags:#code development #change management #work tracking #artifact-driven #change workflow

Ready to run

npx skills add https://github.com/morganabel/daily-workout --skill source-command-opsx-new

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: source-command-opsx-new
Source: https://github.com/morganabel/daily-workout/tree/main/.agents/skills/source-command-opsx-new
Command: npx skills add https://github.com/morganabel/daily-workout --skill source-command-opsx-new

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openspec, and includes scripts (resource) components.

What problem does it solve?

Manually initiating a new change can be time-consuming and error-prone, especially when using artifact-driven workflows.

Core Features & Use Cases

Automate Change Initiation: Simplifies the process of starting a new change using an artifact-driven approach.
User Interaction: Prompts users for change details and helps determine the correct workflow schema.
Change Management: Creates a change directory, shows artifact status, and provides instructions for the first artifact.

Quick Start

Use the source-command-opsx-new skill by running /opsx:new [change_name].

Frequently Asked Questions about source-command-opsx-new

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate change initiation for an artifact-driven workflow?▼

Automating change initiation involves interacting with a CLI to collect change details, select the appropriate schema, and generate step-by-step instructions for the first artifact. This reduces manual errors when starting a new change lifecycle.

What is an artifact-driven change workflow?▼

An artifact-driven change workflow manages the software development lifecycle by generating and tracking specific artifacts. It uses a schema system to guide the creation of changes, ensuring structured progress from initiation through completion.

Do I need the openspec CLI to manage artifact-driven code changes?▼

Yes, you need the openspec CLI and the openspec schema system installed. These dependencies are required to manage change lifecycles, select schemas, and automate the creation of change directories and artifacts.

How do I start a new change using openspec?▼

To start a new change, run the `/opsx:new [change_name]` command. The system will prompt you for change details, create a dedicated change directory, and provide instructions for generating your first artifact.

Can I track artifact status during code development?▼

Yes, after initiating a new change, the workflow displays artifact status and provides step-by-step instructions. This allows you to track progress and manage the change lifecycle directly through the schema system.

What is the best way to structure a new change directory for work tracking?▼

The best way to structure a new change directory is using an automated artifact-driven approach that selects the correct schema. This ensures all initial artifacts are correctly organized for tracking the change workflow.