request-refactor-plan

Convert vague refactor requests into structured GitHub issues with tiny-commit plans.

13|3|Updated May 12, 2026
One-click install
npx skills add https://github.com/kevinnft/ai-agent-skills --skill request-refactor-plan-kevinnft
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/kevinnft/ai-agent-skills/tree/main/skills/mattpocock/deprecated/request-refactor-plan
Command: npx skills add https://github.com/kevinnft/ai-agent-skills --skill request-refactor-plan-kevinnft

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The skill helps engineers turn vague refactor requests into a detailed, actionable plan and a GitHub issue containing tiny, testable commits.

Core Features & Use Cases

  • Interview the user to elicit a long, detailed description of the problem and potential solutions.
  • Explore the repository to verify the current state and understand the codebase.
  • Break the implementation into tiny, incremental commits and generate a structured GitHub issue using a standard template.

Use case: Planning a safe incremental refactor for a legacy module.

Quick Start

Describe the refactor goal and the codebase context, and the Skill will generate a tiny-commit plan and a GitHub issue.

Frequently Asked Questions about request-refactor-plan

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

FAQPage Schema
How do I break a vague refactor request into tiny, verifiable commits?

Break vague refactor requests into tiny commits by interviewing stakeholders to scope the problem, exploring the codebase, and generating a structured GitHub issue with an incremental implementation plan.

What is the best way to plan a safe incremental refactor for a legacy module?

Planning a safe incremental refactor involves eliciting detailed problem descriptions through interviews, verifying the current repository state, and structuring the work into tiny, testable commit steps.

How do I convert an architecture change proposal into a GitHub issue template?

Convert architecture changes into a GitHub issue template by gathering stakeholder requirements, analyzing the codebase context, and outputting a standard issue structure with a tiny-commit plan.

Does this refactor planning workflow require specific codebase analysis tools?

No specific codebase analysis tools are required as dependencies. The workflow explores the repository directly to verify the current state and understand the codebase before generating a refactor plan.

When should I use a structured interview process for project management refactoring?

Use a structured interview process for refactoring when you have vague project management requests that need detailed problem elicitation, repository verification, and a structured GitHub issue with tiny commits.