change-manager

Orchestrate propose, apply, verify, and archive phases for changes in a 'changes/' directory.

Updated Apr 3, 2026
One-click install
npx skills add https://github.com/iJosueeh/nexora-web --skill change-manager-ijosueeh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-manager
Source: https://github.com/iJosueeh/nexora-web/tree/main/.opencode/skills/change-manager
Command: npx skills add https://github.com/iJosueeh/nexora-web --skill change-manager-ijosueeh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill facilitates managing incremental changes to existing projects with Product-Spec.md, automating the workflow (propose, apply, verify, archive) while adhering to OpenSpec-style SDD.

Core Features & Use Cases

  • Workflow Automation: Automates the propose, apply, verify, and archive phases of a change.
  • Scoped Changes: Manages changes within a changes/ directory, preserving the integrity of the Product-Spec.md.
  • Use Case: When adding a new feature or incrementally modifying an existing project, use this Skill to ensure the change is managed through a structured workflow.

Quick Start

Execute the change-manager Skill with the command '/change-manager propose <change-name>' to start a new change proposal.

Frequently Asked Questions about change-manager

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

FAQPage Schema
How do I manage incremental changes to an existing software project?

To manage incremental changes in brownfield development, you orchestrate structured workflows that coordinate propose, apply, verify, and archive phases within a designated changes directory. This approach preserves project integrity while automating the change management process.

What is OpenSpec-style SDD for change management?

OpenSpec-style SDD is a structured development approach that uses a Product-Spec.md file to maintain project specifications. Change management workflows adhere to this specification by automating incremental updates through scoped phases, ensuring modifications align with the existing project architecture.

How do I automate brownfield development workflows with structured phases?

You automate brownfield development workflows by executing commands that initiate a new change proposal, then sequentially processing the apply, verify, and archive phases. This structured workflow operates directly within a changes directory to manage software development increments.

Do I need a Product-Spec.md file to use structured change management?

Yes, a Product-Spec.md file and a changes directory are required prerequisites. This structured change management workflow assumes the presence of these elements to properly orchestrate and scope incremental modifications to your software project.

Can I use workflow automation for brownfield development without altering the main spec?

Yes, workflow automation for brownfield development manages changes within a scoped changes directory, preserving the integrity of your main Product-Spec.md. This isolation ensures incremental modifications are verified and archived before integration.

What are the limitations of using a changes directory for software development modifications?

The structured change management workflow is limited to projects utilizing a Product-Spec.md and a changes directory. It is designed specifically for brownfield development and incremental modifications, not for building standalone features outside the OpenSpec-style SDD framework.