refactoring-plan
Refactoring Plan
Guide the user from a messy codebase problem to a fully-formed refactor plan, broken into the smallest safe commits possible, then submit it to their preferred destination.
Skill workflow — these skills chain naturally:
pre-mortem (optional — stress-test the plan before committing) → refactoring-plan → prd-slice (push slices to a tracker)
Process
1. Gather the problem statement
Ask the user for a detailed description of:
- The problem they are trying to solve
- Any ideas or constraints they already have in mind
Understanding the pain before proposing solutions matters — jumping straight to answers often misses what's really broken.
More from yldgio/vibe-grimoire
pre-mortem
>-
13create-prd
Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue, Azure DevOps work item, or local file. Use when the user wants to create or write a PRD, create a product requirements document, design a new feature, or capture requirements.
11setup-repo
>-
11prd-slice
Break a PRD into independently-deliverable work items (vertical slices / tracer bullets) and create them in Azure DevOps, GitHub Issues, or Jira. Use when a user wants to convert a PRD into implementation tickets, decompose a product spec into trackable slices, create work items from requirements, or break down a PRD for any issue tracker — even if they don't say "vertical slice" or "tracer bullet".
11plan-from-prd
Turn a PRD into a multi-phase, local Markdown implementation plan using tracer-bullet vertical slices, saved to ./plans/. Use when the user wants to create an implementation plan from a PRD, plan phases from a PRD, break a PRD into development phases, or mentions "tracer bullets" or "implementation phases". For creating tracker work items (GitHub Issues, Azure DevOps, Jira) use the prd-slice skill instead.
11tdd
>-
9