Interview-driven refactoring planner that breaks changes into tiny, safe commits and files a GitHub issue.
Works with
Conducts a detailed user interview to understand the problem, explore alternatives, and nail down exact scope before planning
Verifies assertions by exploring the repository and assesses existing test coverage in the affected codebase
Breaks implementation into the smallest possible commits, each leaving the codebase in a working state
Generates a structured GitHub issue with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionrequest-refactor-planExecute the skills CLI command in your project's root directory to begin installation:
Fetches request-refactor-plan from mattpocock/skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate request-refactor-plan. Access via /request-refactor-plan in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
12.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
12.7K
stars
This skill will be invoked when the user wants to create a refactor request. You should go through the steps below. You may skip steps if you don't consider them necessary.
Ask the user for a long, detailed description of the problem they want to solve and any potential ideas for solutions.
Explore the repo to verify their assertions and understand the current state of the codebase.
Ask whether they have considered other options, and present other options to them.
Interview the user about the implementation. Be extremely detailed and thorough.
Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change.
Look in the codebase to check for test coverage of this area of the codebase. If there is insufficient test coverage, ask the user what their plans for testing are.
Break the implementation into a plan of tiny commits. Remember Martin Fowler's advice to "make each refactoring step as small as possible, so that you can always see the program working."
Create a GitHub issue with the refactor plan. Use the following template for the issue description:
The problem that the developer is facing, from the developer's perspective.
The solution to the problem, from the developer's perspective.
A LONG, detailed implementation plan. Write the plan in plain English, breaking down the implementation into the tiniest commits possible. Each commit should leave the codebase in a working state.
A list of implementation decisions that were made. This can include:
Do NOT include specific file paths or code snippets. They may end up being outdated very quickly.
A list of testing decisions that were made. Include:
A description of the things that are out of scope for this refactor.
Any further notes about the refactor.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
mattpocock/skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
request-refactor-plan has been reliable in day-to-day use. Documentation quality is above average for community skills.
request-refactor-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: request-refactor-plan is the kind of skill you can hand to a new teammate without a long onboarding doc.
request-refactor-plan is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in request-refactor-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
request-refactor-plan reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for request-refactor-plan matched our evaluation — installs cleanly and behaves as described in the markdown.
Solid pick for teams standardizing on skills: request-refactor-plan is focused, and the summary matches what you get after install.
We added request-refactor-plan from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Useful defaults in request-refactor-plan — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 59