openspec-new-change

Automate creation of a new OpenSpec change with a structured artifact workflow.

5|Updated Sep 17, 2022
One-click install
npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-new-change-kevinxo328
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: openspec-new-change
Source: https://github.com/kevinxo328/mercari-scraper/tree/main/.gemini/skills/openspec-new-change
Command: npx skills add https://github.com/kevinxo328/mercari-scraper --skill openspec-new-change-kevinxo328

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates creating a new OpenSpec change by providing a structured, artifact-driven workflow that ensures changes are properly scoped, documented, and prepared for review.

Core Features & Use Cases

  • Scaffold a new OpenSpec change with a clear artifact sequence.
  • Validate and track progress through the status of each artifact before activation.
  • Use cases include feature additions, bug fixes, or modifications that require formal review and artifact-driven processes.

Quick Start

Describe the change you want to work on in kebab-case to begin the change creation.

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 OpenSpec change proposal?

Scaffold a new OpenSpec change by describing the modification in kebab-case, which triggers a guided, artifact-driven workflow that provides initial artifact instructions without creating artifacts yet.

What is an artifact-driven workflow for change management?

An artifact-driven workflow enforces a structured, reproducible sequence of artifacts to ensure software changes are properly scoped, documented, and validated before activation.

How do I track artifact status during an OpenSpec change workflow?

Track artifact status by validating the progress of each artifact within the guided OpenSpec workflow, ensuring every step is properly documented and prepared before the change is activated.

Can I use custom schemas instead of the default OpenSpec change workflow?

You can use optional non-default schemas to modify the artifact workflow, though the system enforces a guided default workflow to ensure reproducible sequences for your change proposal.

When should I use a formal change proposal workflow for software modifications?

Use a formal change proposal workflow when your feature improvements, bug fixes, or modifications require clear scoping, formal review, and a reproducible sequence of documentation artifacts.