skills.rest
moogah
moogahCOMMUNITY
Explore all skills by this author →
GitHub

opsx-new

Scaffold new changes under openspec/changes/<name>/ using the spec-driven-tasks schema.

Updated Jan 20, 2026
Search Tags:#workflow#spec-driven#openspec#change-management#opsx#task-artifacts
One-click install
npx skills add https://github.com/moogah/emacs --skill opsx-new-moogah
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: opsx-new
Source: https://github.com/moogah/emacs/tree/main/.claude/skills/opsx-new
Command: npx skills add https://github.com/moogah/emacs --skill opsx-new-moogah

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Start new changes using the OPSX workflow to scaffold a change folder and task artifacts under openspec/changes/<name>/ with the spec-driven-tasks schema.

Core Features & Use Cases

  • Scaffolds a new change directory configured for a structured spec-driven-tasks workflow.
  • Creates an artifact plan and trackable tasks to guide implementation and testing.
  • Fits for feature iterations, fixes, or enhancements that require formal specs and task-tracking.

Quick Start

Execute openspec new change "<name>" using the spec-driven-tasks schema to initialize the change scaffold.

Frequently Asked Questions about opsx-new

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

FAQPage Schema
How do I start a new feature change with spec-driven task tracking?▼

To start feature changes with spec-driven task tracking, scaffold a new change directory under openspec/changes/<name>/ using the spec-driven-tasks schema. This initializes an artifact plan and trackable tasks to guide implementation and testing.

What is the OPSX workflow for managing software iterations?▼

The OPSX workflow is a structured change management process that scaffolds task artifacts under openspec/changes/. It enables formal specification and artifact tracking from design through implementation and testing for feature iterations and fixes.

How do I create a change directory for formal specifications and task artifacts?▼

Create a change directory for formal specifications by executing the openspec new change command with your desired name. This scaffolds a structured folder configured for the spec-driven-tasks workflow, generating an initial artifact plan to track implementation.

Does the spec-driven-tasks schema require manual input before proceeding?▼

The spec-driven-tasks schema integrates with status and instruction commands to guide first artifacts and will not proceed without user input. This ensures structured artifact tracking remains controlled throughout the design and implementation phases.

When should I use a spec-driven workflow for software enhancements?▼

Use a spec-driven workflow for software enhancements when your feature iterations or fixes require formal specs and structured task-tracking. It scaffolds trackable task artifacts to maintain organization from design through testing.

Can I track implementation and testing artifacts across multiple tasks?▼

Tracking implementation and testing artifacts across multiple tasks is enabled by scaffolding a change under openspec/changes/<name>/. This creates an artifact plan that maintains structured tracking throughout all subsequent tasks.

Related Skills

Explore More Software Engineering Skills→
inflexa-aiinflexa-ai
29

openspec-propose

Generate proposal.md, design.md, and tasks.md via the openspec CLI.

Official
Advanced
costrict-plugins-repocostrict-plugins-repo

executing-plans

Execute written implementation plans with critical review checkpoints.

Official
Advanced
MeetTechnologyMeetTechnology

openspec-continue-change

Automate OpenSpec change progression by generating the next artifact via CLI.

Community
Advanced
KahtafKahtaf
9

source-command-opsx-apply

Automate task application from an OpenSpec change with user interaction.

Community
Advanced