One-click install
npx skills add https://github.com/AngelMaldonado/skills --skill cx-change
Or copy as Structured Prompt for Agentβ–Ό
Please help me install this Agent Skill.
Skill: cx-change
Source: https://github.com/AngelMaldonado/skills/tree/main/.claude/skills/cx-change
Command: npx skills add https://github.com/AngelMaldonado/skills --skill cx-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinated change management framework that organizes proposals, designs, and tasks under docs/changes/ to ensure traceability and controlled evolution of software features.

Core Features & Use Cases

  • Scaffold and organize new changes with proposal.md, design.md, and tasks.md
  • Track dependencies and delta specs, and monitor change status with cx commands
  • Archive completed changes and keep a clean history for audit and reference

Quick Start

Run cx instructions <artifact> to bootstrap the change workflow and start filling proposal.md.

Frequently Asked Questions about cx-change

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

FAQPage Schema
How do I manage change requests and track feature proposals in software engineering?β–Ό

Change requests and feature proposals are managed by organizing proposal.md, design.md, and tasks.md files under a docs/changes/ directory. This structured change management approach ensures traceability and controlled evolution of software features from initial proposal to archive.

What is the best way to structure documentation for architectural updates and bug fixes?β–Ό

Structuring documentation for architectural updates involves creating dedicated scaffolds with proposal, design, and tasks files. This framework organizes feature work and bug fixes under docs/changes/ to maintain a clean history for audit and reference across multiple files.

How do I track dependencies and monitor status for ongoing feature changes?β–Ό

Dependencies and delta specs are tracked, and change status is monitored using cx commands. This workflow automation applies to software development teams managing feature work and architectural updates across multiple files and documentation.

Can I use this change management workflow for tracking multiple feature updates across different files?β–Ό

Yes, this change management workflow is designed for software development teams managing feature work, bug fixes, and architectural updates across multiple files and docs. It satisfies requirements for scaffold generation, dependency tracking, status updates, and archival workflows.

How do I archive completed feature changes and maintain a clean history for audits?β–Ό

Completed feature changes are archived using the workflow's archival commands, keeping a clean history for audit and reference. This ensures that finished proposals, designs, and tasks are organized and traceable throughout the software lifecycle.

How do I bootstrap a new change management workflow for a software feature?β–Ό

To bootstrap a new change management workflow, run cx instructions <artifact> to start filling proposal.md. This generates the necessary scaffold under docs/changes/ to begin tracking your feature proposal, design, and tasks.