openspec-new-change

Scaffold a new OpenSpec change directory using a workflow schema.

9|1|Updated Jun 6, 2018
One-click install
npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-new-change-edwardsnjd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/edwardsnjd/dot-files/tree/main/configuration/agents/.agents/skills/openspec-new-change
Command: npx skills add https://github.com/edwardsnjd/dot-files --skill openspec-new-change-edwardsnjd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

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

Core Features & Use Cases

  • Automated Change Scaffolding: Creates a new change directory with a predefined structure based on a chosen workflow schema.
  • Guided Workflow Initiation: Helps users define the change name and select the appropriate workflow schema.
  • Use Case: A developer needs to implement a new authentication module. They use this Skill to start a new change, ensuring it follows the standard 'spec-driven' workflow and provides the necessary templates for the initial artifacts.

Quick Start

Use the openspec new change skill to start a new 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 scaffold a new change directory for a feature development workflow?

You can scaffold a new change directory by initiating a change within the OpenSpec system, which uses an artifact-driven workflow to create structured development processes and manage dependencies automatically.

What is an artifact-driven workflow for change management?

An artifact-driven workflow for change management is a structured development process that uses predefined templates and schemas to guide modifications. It ensures feature development and bug fixes follow a consistent, structured approach across the project lifecycle.

Do I need the OpenSpec CLI to initiate a new change?

Yes, you need the OpenSpec CLI to initiate a new change. The Skill requires the CLI to scaffold new change directories and manage artifact dependencies during the structured workflow initiation process.

How do I select the appropriate workflow schema for a new modification?

You select the appropriate workflow schema during the guided workflow initiation process. The Skill helps you define the change name and choose the correct schema, providing necessary templates for the initial artifacts.

Can I use automated naming when starting a structured development process?

Yes, you can use automated naming when starting a structured development process. The Skill supports automatic naming and schema selection to streamline the initiation of new changes within the OpenSpec system.

What are the limitations of using a schema-based workflow for bug fixes?

The schema-based workflow requires strict adherence to the predefined artifact structure and dependencies. It is not suitable for ad-hoc edits, as it enforces a structured development process designed for formal change management and scaffolded directories.