Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.
80
75%
Does it follow best practices?
Impact
80%
3.20xAverage score across 3 eval scenarios
—
The risk profile of this skill
Fix and improve this skill with Tessl
tessl review fix ./.cursor/skills/request-refactor-plan/SKILL.mdTesting decisions and alternatives exploration
Alternatives discussed
100%
100%
Test coverage acknowledged
100%
100%
Testing Decisions section present
0%
100%
External behavior principle stated
0%
100%
Modules to test named
66%
100%
Prior art referenced
0%
0%
Problem Statement present
0%
100%
Out of Scope present
0%
100%
Commits section present
0%
100%
Tiny commits and scope definition
Commits section present
0%
100%
Granular commit count
50%
100%
Working state per commit
60%
100%
Plain English commits
0%
0%
Out of Scope section present
0%
100%
Out of Scope is substantive
25%
100%
Problem Statement present
0%
100%
Decision Document present
0%
100%
Testing Decisions present
0%
100%
Refactor plan template structure
Problem Statement section
0%
100%
Solution section
0%
100%
Commits section
0%
100%
Decision Document section
0%
100%
Testing Decisions section
0%
100%
Out of Scope section
0%
100%
No file paths in Decision Document
0%
0%
No code snippets in Decision Document
0%
0%
External behavior testing principle
0%
100%
Modules to be tested
0%
100%
Prior art for tests
0%
100%
d6882ad
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.