skills.rest
zxpmail
zxpmailCOMMUNITY
Explore all skills by this author →
GitHub

change-manager

Manage project changes against Product-Spec.md through propose, apply, verify, and archive steps.

18|4|Updated May 16, 2026
Search Tags:#workflow orchestration#change management#spec-driven development#brownfield project#project iteration
One-click install
npx skills add https://github.com/zxpmail/ReqForge --skill change-manager
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: change-manager
Source: https://github.com/zxpmail/ReqForge/tree/main/core/skills/change-manager
Command: npx skills add https://github.com/zxpmail/ReqForge --skill change-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The change-manager Skill unit simplifies managing incremental changes in projects that already have a Product-Spec.md, enabling structured changes without full spec rewrites.

Core Features & Use Cases

  • Change Proposals: Orchestrate scoped changes from proposal through archive.
  • Scoped Workflows: Propose, apply, verify, and archive changes with defined guardrails.
  • Brownfield Projects: Ideal for updating brownfield projects without extensive spec modifications.

Quick Start

Use the /change-manager command to start a change workflow: /change-manager propose <change-name>

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 in a brownfield project without rewriting the spec?▼

To manage incremental changes in a brownfield project without rewriting the spec, use a structured change management workflow. It executes propose, apply, verify, and archive steps to ensure changes align with existing spec requirements.

What is the best way to orchestrate scoped changes for spec-driven development?▼

The best way to orchestrate scoped changes for spec-driven development is defining a workflow from proposal through archive. This enforces structured guardrails ensuring changes remain well-documented and aligned with project specifications.

Do I need a Product-Spec.md to use this project iteration workflow?▼

Yes, you need a Product-Spec.md to use this project iteration workflow. The change management process has explicit dependencies on the Product-Spec.md to enforce structured guardrails and validate proposed modifications.

How do I start a change proposal for an existing project?▼

To start a change proposal for an existing project, invoke the change workflow command with the propose action and your change name. This initiates the scoped workflow to apply, verify, and archive modifications.

When should I not use a scoped change workflow for project updates?▼

You should not use a scoped change workflow for project updates requiring extensive spec modifications. It is designed for incremental changes in brownfield projects where the existing Product-Spec.md remains the primary constraint.

Related Skills

Explore More Software Engineering Skills→
srobinsonsrobinson

create-spec

Creates a structured SPEC.md template through interactive one-question-at-a-time elicitation.

Community
Intermediate
Magnatrix-LabMagnatrix-Lab
1

deploy-pipeline

Orchestrate building, testing, and deploying AI systems to staging and production.

Community
Advanced
benjaminshoemakerbenjaminshoemaker
39

setup

Initialize projects with AI Coding Toolkit components and metadata.

Community
Advanced
HerbertGaoHerbertGao
1

openspec-sync-specs

Merge incremental specification changes into the main specification.

Community
Advanced