skills.rest
ClyptAI
ClyptAIOFFICIAL
Explore all skills by this author →
GitHub

request-refactor-plan

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

Updated Apr 4, 2026
Search Tags:#planning#interview#refactor#rfc#stakeholders#github-issue#incremental-commits
One-click install
npx skills add https://github.com/ClyptAI/Clypt-Frontend --skill request-refactor-plan-clyptai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: request-refactor-plan
Source: https://github.com/ClyptAI/Clypt-Frontend/tree/main/.agents/skills/mattpocock-skills/request-refactor-plan
Command: npx skills add https://github.com/ClyptAI/Clypt-Frontend --skill request-refactor-plan-clyptai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Planning and executing large-scale refactors can be error-prone and slow without a structured approach. This Skill helps teams gather requirements through interviews, define a precise refactor scope, and convert it into a safe, incremental plan delivered as tiny commits and tracked as a GitHub issue.

Core Features & Use Cases

  • Interview-driven scoping and requirement consolidation for refactors.
  • Tiny-commit RFC generation that breaks changes into atomic steps.
  • GitHub issue drafting and tracking to ensure visibility and accountability.
  • Risk assessment, testing considerations, and rollback guidance for safe iteration.

Quick Start

Interview the user to elicit the problem, then generate a plan of tiny commits as an RFC and file it as 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 plan a large-scale code refactor safely?▼

Plan a code refactor safely by interviewing stakeholders to consolidate requirements, scoping the desired outcomes, and breaking the work into incremental commits with risk assessment and rollback guidance.

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

Breaking a software refactor into tiny commits involves creating an RFC that outlines atomic steps, validating impact, and generating a commit-by-commit plan tracked through a GitHub issue for visibility and accountability.

How do I write an RFC for a code refactoring project?▼

Write an RFC for a code refactoring project by consolidating interview-driven requirements, defining a precise scope, and outlining task scenarios that yield incremental commits, including decision logs and testing considerations.

How do I draft a GitHub issue for tracking a refactoring plan?▼

Draft a GitHub issue for tracking a refactoring plan by generating a detailed commit-by-commit breakdown, attaching the RFC, and including testing considerations and rollback guidance to ensure safe iteration and visibility.

Does this refactor planning approach work without any external dependencies?▼

Yes, this refactor planning approach works without external dependencies, relying entirely on interviewing stakeholders to gather requirements and producing a textual RFC and GitHub issue ready for submission.

When should I not use an interview-driven approach for refactoring?▼

Avoid an interview-driven approach for refactoring when stakeholder availability is limited or the required changes are trivial, as the structured scoping and RFC generation process is designed for large-scale, error-prone refactors.

Related Skills

Explore More Software Engineering Skills→
raphaelmansraphaelmans

request-refactor-plan

Plan structured refactor work into a GitHub issue template.

Community
Intermediate
ThalfmanThalfman

request-refactor-plan

Create a commit-by-commit refactor plan and GitHub issue from codebase analysis.

Community
Intermediate
Jonathan0823Jonathan0823
7

refactoring-safely

Guide test-driven refactoring with incremental changes and rollback plans.

Community
Basic
CarGDevCarGDev

Code Auditor

Audit code quality by detecting dead code, complexity, duplication, and architectural smells.

Community
Intermediate