change-plan

Name: change-plan
Availability: InStock
Author: ashwnn

Analyze change requests to produce structured code change plans.

Updated Aug 27, 2026

Search Tags:#planning #rollback #risk-assessment #software-engineering #code-change #change-plan

Ready to run

npx skills add https://github.com/ashwnn/agent-config --skill change-plan

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: change-plan
Source: https://github.com/ashwnn/agent-config/tree/main/skills/change-plan
Command: npx skills add https://github.com/ashwnn/agent-config --skill change-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams and developers plan code changes by producing a structured plan that captures objectives, affected files, dependencies, risks, and a rollback strategy before edits.

Core Features & Use Cases

Analyze the change request to identify affected files, packages, and dependencies.
Generate a numbered, time-estimated plan with dependencies between steps.
Identify risks, edge cases, and potential regressions, with suggested mitigations.
Produce a rollback plan detailing steps to revert changes.

Quick Start

Provide a feature request and I will generate a structured plan with objectives, affected files, steps, risks, rollback, and questions.

Frequently Asked Questions about change-plan

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

FAQPage Schema

How do I create a structured code change plan before modifying files?▼

A structured code change plan analyzes your request to identify affected files and dependencies, then generates a numbered step-by-step plan with rationales, risk mitigations, and a rollback strategy before you edit code.

What is a rollback strategy and when do I need one for refactoring?▼

A rollback strategy details the steps to revert code changes safely. You need one for refactoring and multi-file changes to document how to restore the previous state if risks or regressions occur.

How do I identify risks and edge cases when planning a feature development?▼

Planning feature development involves analyzing the change request to identify potential risks, edge cases, and regressions. The plan provides suggested mitigations to address these issues before implementation begins.

Can I use a change plan for multi-file changes across software projects?▼

Yes, a change plan applies to multi-file changes across software projects. It analyzes the request to identify affected packages and dependencies, producing an ordered plan with time estimates and open questions.

What's the best way to document dependencies between steps in a code change plan?▼

The best way to document dependencies between steps is generating a numbered, time-estimated plan. This captures the objective, file-change list with rationales, risks, and rollback strategy in an ordered sequence.

Why does my code change plan need to include open questions?▼

Your code change plan includes open questions to highlight unresolved issues before implementation begins. This ensures that objectives, affected files, risks, and rollback strategies are fully understood before edits.