skills.rest
EvanPluchart
EvanPluchartCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

refactor-planner

Plan incremental refactoring by scanning technical debt and prioritizing findings.

2|Updated Mar 19, 2026
Search Tags:#code quality#refactoring#coding conventions#maintenance#technical debt#prioritization#impact effort matrix
One-click install
npx skills add https://github.com/EvanPluchart/kyomu --skill refactor-planner-evanpluchart
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: refactor-planner
Source: https://github.com/EvanPluchart/kyomu/tree/main/.claude/skills/refactor-planner
Command: npx skills add https://github.com/EvanPluchart/kyomu --skill refactor-planner-evanpluchart

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you identify technical debt and code quality issues and turn them into an actionable, prioritized refactoring plan without risking a disruptive big-bang rewrite.

Core Features & Use Cases

  • Technical debt scan: Detects duplication, high cyclomatic complexity, naming inconsistencies, dead code, strong coupling, and evan-workflow pattern violations.
  • Priority-driven planning: Converts findings into refactoring stories using an impact/effort matrix and produces a non-cassant, testable sequence.
  • Convention comparison: Compares code against evan-workflow conventions and lists gaps.

Quick Start

Run a technical debt scan on your repository by asking the skill to analyze the code at the path you provide, then use the generated priorities to plan your first incremental refactoring stories.

Frequently Asked Questions about refactor-planner

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

FAQPage Schema
How do I plan an incremental code refactor without a big-bang rewrite?▼

An incremental code refactor analyzes technical debt, duplication, and complexity to generate a non-cassant, testable sequence of refactoring stories. This approach uses an impact/effort matrix to prioritize safe, progressive improvements over a disruptive rewrite.

What is the best way to prioritize technical debt into actionable refactoring stories?▼

Prioritizing technical debt uses an impact/effort matrix to convert code quality findings into actionable refactoring stories. This method generates a safe, testable sequence that includes validation criteria and affected files for progressive improvement.

Does refactoring planning work for comparing code against specific coding conventions?▼

Yes, refactoring planning supports a compare mode that analyzes your codebase against evan-workflow coding conventions. It identifies convention violations and lists gaps to help align your code with established standards during maintenance cycles.

When should I avoid aggressive refactoring and use a progressive maintenance cycle instead?▼

You should avoid aggressive refactoring when facing high cyclomatic complexity, strong coupling, and significant technical debt that risks a disruptive big-bang rewrite. A progressive maintenance cycle applies an impact/effort matrix to sequence safe, testable refactoring stories with validation criteria.

Related Skills

Explore More Software Engineering Skills→
jankneumannjankneumann
4

tech-debt-analysis

Analyze codebase complexity, coupling, duplication, and import issues to generate markdown and JSON reports.

Community
Advanced
paimlpaiml
161

Automated Refactoring with PMAT

Automate refactoring of multi-language codebases with PMAT and impact metrics.

Official
Advanced
ashtonianashtonian
2

refactor

Analyze codebases to plan incremental refactors that preserve behavior.

Community
Advanced
davekilleendavekilleen
461

tech-debt

Scan projects and meeting notes to categorize technical debt by impact and effort.

Community
Intermediate