change-planning

Define goals, constraints, risk, touchpoints, and a verification plan before editing.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/IAG-Patterns/DEMO_COPILOT_SKILLS --skill change-planning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: change-planning
Source: https://github.com/IAG-Patterns/DEMO_COPILOT_SKILLS/tree/main/.github/skills/change-planning
Command: npx skills add https://github.com/IAG-Patterns/DEMO_COPILOT_SKILLS --skill change-planning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Plan changes safely by defining goals, constraints, risk, touchpoints, and a verification plan before editing.

Core Features & Use Cases

  • Define goals and constraints to guide changes.
  • Assess risk and map touchpoints across files, configs, and tests.
  • Create a change map and a verification/test plan for safe delivery.
  • Use Case: When refactoring a module, outline the goal, list constraints (backwards compatibility), identify files touched, and specify a test plan before making changes.

Quick Start

Restate the goal in one sentence, list constraints and risks, draft the change map, and prepare a verification plan.

Frequently Asked Questions about change-planning

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

FAQPage Schema
How do I plan a safe code refactor before making changes?

Plan safe changes by defining the goal, listing constraints, scoring risk, mapping touched files and configs, and outlining a verification plan before editing.

What is change planning in software development?

Change planning is a structured workflow that defines goals, constraints, risks, and touchpoints for non-trivial tasks to ensure safe delivery before editing.

When do I need a change map and risk assessment for my project?

You need a change map and risk assessment for non-trivial tasks like new features, refactors, or bug fixes with uncertain causes to verify touchpoints and ensure safe delivery.

How do I create a verification plan for a bug fix with uncertain causes?

Create a verification plan by restating the fix goal, listing constraints, scoring risk, mapping touched files and tests, and specifying the test plan before editing.

Does change planning work for small codebase edits?

Change planning targets non-trivial tasks like refactors and new features, so small codebase edits with clear causes may not require this structured workflow.