skills.rest
raphaelmans
raphaelmansCOMMUNITY
Explore all skills by this author →
GitHub

request-refactor-plan

Plan structured refactor work into a GitHub issue template.

Updated Feb 28, 2026
Search Tags:#git#planning#github#refactor#issue-template#stakeholder-interview#tiny-commits
One-click install
npx skills add https://github.com/raphaelmans/agent-skills --skill request-refactor-plan-raphaelmans
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/raphaelmans/agent-skills/tree/main/request-refactor-plan
Command: npx skills add https://github.com/raphaelmans/agent-skills --skill request-refactor-plan-raphaelmans

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning refactor work is often ad hoc; this skill provides a structured approach to gather the problem statement, goals, and constraints from stakeholders.

Core Features & Use Cases

  • Interview stakeholders to extract the problem and desired outcomes.
  • Explore the repository to validate scope, dependencies, and risk.
  • Break the work into tiny commits and generate a GitHub issue with a comprehensive plan.

Quick Start

Describe the refactor problem and desired outcome, then request a GitHub issue with a detailed, tiny-commit plan.

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 create a GitHub issue for the work?▼

To plan a code refactor, interview stakeholders to capture the problem and goals, explore the repository to validate scope, and generate a GitHub issue template with incremental commits, decisions, and tests for full traceability.

What is the best way to break a large refactor into tiny commits?▼

The best way to break a refactor into tiny commits is to scope the work by exploring the repository for dependencies and edge cases, then propose an incremental schedule of commits. This minimizes risk and ensures each change is traceable and reproducible.

How do I gather refactor requirements from stakeholders before changing code?▼

Gather refactor requirements by conducting stakeholder interviews to extract the core problem, desired outcomes, and design constraints. This structured approach ensures the refactor plan addresses actual needs before any repository changes are proposed.

Can I generate a GitHub issue template that includes a refactor plan and test schedule?▼

Yes, you can generate a GitHub issue template that includes the refactor plan, design goals, decisions, tests, and a commit schedule. This ensures the refactoring work is fully traceable and reproducible for all stakeholders.

Why scope a refactor by exploring the repository before writing an issue?▼

Scoping a refactor by exploring the repository validates dependencies, identifies edge cases, and minimizes deployment risk. This ensures the generated GitHub issue contains a realistic, incremental commit schedule rather than an ad hoc plan.

Related Skills

Explore More Software Engineering Skills→
shwilliamsonshwilliamson

requirements-gathering

Guide stakeholder interviews to document feature requirements and scope.

Community
Basic
ClyptAIClyptAI

request-refactor-plan

Interview stakeholders to plan refactors and generate commit-by-commit GitHub issues.

Official
Advanced
hgxszhjhgxszhj

request-refactor-plan

Interview users to create a tiny-commit refactor plan filed as a GitHub issue.

Community
Intermediate
safzanpiranisafzanpirani
1

request-refactor-plan

Guide users through an interview process to create a refactor plan as a GitHub issue.

Community
Advanced