plan-change
Work out what a change touches before you commit to the design.
A useful plan makes the next edit easier. This skill finds the nearest existing pattern, maps the affected code and consumers, and turns the request into small slices with checks attached.
When I’d use it
Use it before a change that crosses modules, alters a contract, or needs an explicit risk assessment. Skip a separate planning session for an obvious, contained change.
Before you start
Bring the request and any acceptance criteria you already know. You don’t need a design document. If there are existing checks or an impact map, share them so the agent can build on that work.
Install it. Then give it a task.
Run this in your project’s terminal. Choose your coding agent in the installer, then start a new agent session if it needs one to discover the skill.
$ npx skills add akdevsaha-dev/factory-skills --skill plan-changeOnce installed, send a prompt like the ones below to your agent. These are example requests to adapt to your own project, not terminal commands or recorded results.
If slash commands aren’t available in your agent, write “Use the plan-change skill to…” and describe the same task.
New to skills? Start with the installation walkthroughWhat happens next
- Turns the request into observable acceptance criteria.
- Traces an existing analog and affected contracts, consumers, and data.
- Assesses risk and chooses a design that fits the project.
- Orders implementation slices and gives each criterion a verification check.
A few ways to ask
5 examplesCopy the one closest to your task. Replace names, paths, dates, and refs with ones that exist in your project.
Scope a background job
› /plan-change move report generation out of the request handler into a background job. Keep the report format and existing permissions.The plan should cover the worker, status storage, API response, and any UI that consumes it.
Check contract impact
› /plan-change add cursor pagination to the projects API. Find every consumer and propose a rollout that keeps existing clients working.Ask for consumer impact when a response contract changes.
Plan a migration
› /plan-change split customer names into first and last name fields. Account for existing records, ambiguous names, and rollback.A migration plan should explain how current data survives, not just describe the new schema.
Define a risky workflow
› /plan-change add partial refunds. Identify the amount, idempotency, permission, and webhook invariants before choosing the implementation slices.This produces a plan. It does not execute a real refund.
Keep planning bounded
› Use plan-change to scope organization invites. Give me the affected modules, unresolved permission decisions, ordered slices, and a check for each acceptance criterion.Useful outputs are decisions and checks you can act on.
What to look for in the result
A grounded goal, acceptance criteria, an impact map, risk, a recommended design, ordered slices, and a verification plan. High-risk plans go to you for approval before implementation.
A thing worth watching
A long list of files isn’t a plan. Ask what each slice changes and how you’ll know it worked. Hand an approved plan to hungry-jack or implement-feature when you’re ready to build.
Use it with
Build a workflow you can repeat.
Follow the step-by-step guide to working with agents.