refactoring-plan

Synthesize code and architecture review findings into a prioritized refactoring roadmap.

Updated Feb 26, 2026
One-click install
npx skills add https://github.com/rockandrolla13/blueprint --skill refactoring-plan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: refactoring-plan
Source: https://github.com/rockandrolla13/blueprint/tree/main/refactoring-plan
Command: npx skills add https://github.com/rockandrolla13/blueprint --skill refactoring-plan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Synthesise findings from code reviews and architecture reviews into a prioritised, dependency-ordered refactoring roadmap with effort estimates and risk assessment. Use this skill when the user has review findings (from code-review or review-architecture) and wants a structured plan for addressing them. Trigger on "make a refactoring plan", "prioritise these findings", "what should I fix first", "create a roadmap", "plan the cleanup", or when the user has just received a review report and asks "what now" or shows multiple issues and needs them ordered. This skill produces a PLAN, not code changes — it feeds into the refactor skill for execution. Do NOT trigger for executing refactoring (use refactor), conducting reviews (use code-review or review-architecture), or designing new systems (use architect + design).

Core Features & Use Cases

  • Take a set of review findings (CR/AR) and produce a consolidated, prioritised roadmap with dependency ordering and effort estimates
  • Break the plan into safe, incremental phases that preserve deployability after each step
  • Integrate with plan-tracker workflows to generate PLAN-*.md files and track progress

Quick Start

Trigger phrases like "make a refactoring plan", "prioritise these findings", "what should I fix first", or "create a roadmap" to generate the roadmap and execution plan.

Frequently Asked Questions about refactoring-plan

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

FAQPage Schema
How do I create a refactoring plan from code review findings?

To create a refactoring plan, synthesize code review and architecture review findings into a prioritized, dependency-ordered roadmap with effort estimates and risk assessments. This structured approach breaks changes into safe, incremental phases that preserve deployability after each step.

What is the best way to prioritize refactoring tasks after an architecture review?

Prioritizing refactoring tasks involves mapping dependencies between issues and assessing their risk and effort. A structured roadmap orders findings so that foundational architecture problems are addressed first, ensuring subsequent fixes remain safe and incremental without breaking existing functionality.

How do I sequence code cleanup steps to keep the codebase deployable?

Sequencing code cleanup steps requires structuring the refactoring roadmap into incremental phases. By ordering tasks based on dependencies and risk assessment, each phase produces a deployable state, preventing partial updates from breaking the system while progressing through the plan.

Does a refactoring roadmap include effort estimates and risk assessment?

A refactoring roadmap includes both effort estimates and risk assessment. By consolidating code review and architecture review findings, the plan evaluates the required work and potential impact of each task, providing a clear, dependency-ordered execution sequence for the cleanup process.

When should I use a refactoring plan instead of executing code changes directly?

Use a refactoring plan when you have review findings and need a structured execution sequence rather than immediate code changes. The plan synthesizes issues into a prioritized roadmap, serving as a guide for a separate execution phase to ensure safe, incremental refactoring.

Can I integrate a refactoring roadmap with a plan-tracker workflow?

You can integrate a refactoring roadmap with a plan-tracker workflow by feeding the generated plan into it. This integration generates PLAN-*.md files to track progress, ensuring the dependency-ordered refactoring phases and effort estimates are monitored throughout the execution lifecycle.