request-refactor-plan
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. The user may also provide links to Linear issues, Figma designs, or Notion documents.
-
Gather external context. If the user provided references to external tools, use the available MCP tools to pull in context:
- Linear: The user may provide a ticket code (e.g.,
EO-1234) or a URL. Fetch issue details, comments, and project context to understand the motivation, constraints, and prior discussion around the refactor. - Figma: The user may provide a Figma URL. Fetch design context if the refactor involves UI changes, to understand the target design.
- Notion: The user may provide a page title or a URL. Search Notion by title if no URL is given. Fetch documents for architectural decision records, tech debt inventories, or related specs.
Use this context to inform your understanding of the refactor scope. If no external references are provided, skip this step.
- Linear: The user may provide a ticket code (e.g.,
-
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. Refer back to any external context gathered in step 2 to avoid re-asking questions already answered in external sources.
-
Hammer out the exact scope of the implementation. Work out what you plan to change and what you plan not to change.
More from evans-sam/skills
grill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
15git-guardrails-claude-code
Set up Claude Code hooks to block dangerous git and gh CLI commands before they execute. Use when user wants to prevent destructive git operations, block dangerous GitHub CLI actions (repo delete, pr merge, secret management, API mutations), or add git/gh safety hooks to Claude Code.
14write-a-prd
Create a PRD through user interview, codebase exploration, and module design, then save as a local markdown document. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.
13prd-to-issues
Turn a PRD into independent ticket artifacts — GitHub issues, Linear tickets, local files, or Notion pages — with HITL/AFK tags and dependency links. Each ticket is a tracer-bullet vertical slice. Use when user wants to produce standalone work items from a PRD. Not for a live feature-building workflow.
12design-an-interface
Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
12ubiquitous-language
Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions "domain model" or "DDD".
11