skills.rest
MyPrototypeWhat
MyPrototypeWhatCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

planning

Convert a change request into an actionable edit plan by reading code and listing affected files.

28|2|Updated Feb 21, 2026
Search Tags:#planning#codebase#impact analysis#change management#scratchpad#edit strategy
One-click install
npx skills add https://github.com/MyPrototypeWhat/context-chef --skill planning-myprototypewhat
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: planning
Source: https://github.com/MyPrototypeWhat/context-chef/tree/main/packages/core/src/modules/skill/__fixtures__/valid-minimal
Command: npx skills add https://github.com/MyPrototypeWhat/context-chef --skill planning-myprototypewhat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you reduce mistakes and rework by forcing a clear plan before making code edits, especially when requirements are unclear or the codebase is large.

Core Features & Use Cases

  • Change impact assessment: Reads the relevant code and identifies what will be affected.
  • Affected file discovery: Lists the files likely involved in the change.
  • Scratchpad planning: Writes a concise edit plan to align intent with execution.
  • Use Case: When you’re asked to implement a feature or fix a bug, it helps you map the scope first so you edit the right places and avoid unintended side effects.

Quick Start

Ask the AI to run the planning steps for your requested change by reading the code, listing affected files, and writing an edit plan to the scratchpad.

Frequently Asked Questions about planning

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

FAQPage Schema
How do I plan code changes before editing files in a large codebase?▼

Change impact analysis prevents errors by reading the codebase, identifying affected files, and writing a step-by-step edit plan to a scratchpad before modifying anything.

What is change impact analysis and when do I need it for software refactoring?▼

Change impact analysis reads relevant code to identify affected files before modifying anything, preventing unintended side effects during bug fixes, feature additions, and refactors.

How do I identify affected files for a bug fix in an existing codebase?▼

You identify affected files by reading the relevant codebase sections and listing the files likely involved in the change. This scope identification happens before you write the actual edit plan.

Can I use a scratchpad to map out an edit strategy for feature additions?▼

Yes, you can write a concise edit plan to a scratchpad to align intent with execution before making code edits, reducing mistakes and rework when requirements are unclear or the codebase is large.

What's the best way to avoid unintended side effects when modifying code?▼

The best way to avoid side effects is to perform change impact assessment by reading the code, listing affected files, and writing a step-by-step plan to a scratchpad before making modifications.

Does this planning approach work for unclear requirements in software engineering?▼

Yes, this planning approach forces a clear plan before editing code, specifically helping reduce mistakes and rework when requirements are unclear or the codebase is large.

Related Skills

Explore More Software Engineering Skills→
SantiagoisperSantiagoisper

health

Compute a weighted composite code health score from automated checks.

Community
Advanced
SimpleEveSimpleEve
30

eo-test

Validate code changes with automated unit and integration tests and generate a test.md report.

Community
Intermediate
smarmen86smarmen86

freeze

Restricts file edits and writes to a specified directory via bookmarking.

Community
Intermediate
AcosmiAcosmi
6

workspace-file-edit

Edit SOUL.md, USER.md, and BOOTSTRAP.md with whitelist enforcement and plan confirmation.

Community
Intermediate