request-refactor-plan

Interview users to create step-by-step refactor plans and GitHub issues.

4|Updated Nov 27, 2025
One-click install
npx skills add https://github.com/EstebanForge/AGENTS --skill request-refactor-plan-estebanforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/EstebanForge/AGENTS/tree/main/skills/request-refactor-plan
Command: npx skills add https://github.com/EstebanForge/AGENTS --skill request-refactor-plan-estebanforge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Developers often struggle to plan and communicate complex code refactors, risking misalignment and errors throughout the process.

Core Features & Use Cases

  • Refactor Planning: Guides users to generate precise, step-by-step refactor plans via interviews.
  • Issue Creation: Automates drafting comprehensive GitHub issues based on structured templates.
  • Use Case: When planning a large codebase change, create a detailed, tiny-commit breakdown and document decisions for team review.

Quick Start

Ask the AI to help create a detailed refactor plan and generate a GitHub issue describing the steps involved.

Frequently Asked Questions about request-refactor-plan

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

FAQPage Schema
How do I plan a code refactor and break it down into safe incremental steps?

To plan a code refactor, this Skill interviews you to break the process into tiny, safe incremental steps. It generates structured markdown templates to document procedures, ensuring systematic code improvements and team alignment.

How do I create a detailed GitHub issue for a software development refactor?

You create a detailed GitHub issue by providing your refactor goals during an interview. The Skill parses your input and automates drafting a comprehensive GitHub issue based on structured templates for project management.

What is the best way to document a large codebase change for an RFC?

The best way to document a large codebase change for an RFC is generating a tiny-commit breakdown. This Skill guides you through an interview to structure decisions and create precise, step-by-step refactor plans for review.

Can I use this planning process for systematic code improvements without external dependencies?

Yes, you can use this planning process for systematic code improvements without external dependencies. It operates independently to parse user input and generate structured markdown templates for your project management needs.

When should I not use an incremental refactor plan for my development issue?

You should not use an incremental refactor plan when a development issue requires a single, immediate code change rather than systematic improvements. This Skill is designed for detailed planning, RFCs, and breaking processes into tiny steps.