Guide iterative refactoring through clarifying questions and option-based design choices.
npx skills add https://github.com/Evan-acg/Evan-Skills --skill refactor-evan-acg
Please help me install this Agent Skill. Skill: refactor Source: https://github.com/Evan-acg/Evan-Skills/tree/main/refactor Command: npx skills add https://github.com/Evan-acg/Evan-Skills --skill refactor-evan-acg
Before refactoring, this process must be used to ensure that the intent, requirements, and design are explored in depth through collaborative dialogue.
Initiate by outlining the current refactor scope and proceed with a single clarifying question to begin the guided design.
High-intent search queries and answers about installing and using this skill.
Collaborative refactoring is a structured process to explore intent, requirements, and design direction before rewriting code. You need it for major software architecture changes, component rewrites, or cross-team codebase modifications to ensure design alignment.
To plan a codebase refactor, start by outlining the current scope and goals, then use a stepwise questioning loop to clarify intent. Evaluate 2-3 design options with trade-offs, segment the design into chapters, and generate an actionable task checklist with change documentation.
Yes, structured refactoring guidance is designed for software projects planning component rewrites across teams and codebases. It facilitates collaboration by verifying modular design content with stakeholders through an iterative, option-based planning process.
The best way to document architecture changes is through phased design and documentation. Present the design as segmented chapters, verify content iteratively with stakeholders, and maintain a task checklist with clear scope, milestones, and testing considerations.
Option-driven planning for software design refactoring proposes 2-3 design options with specific trade-offs to choose from. It enables iterative refinement by applying a step-by-step questioning loop to clarify requirements before finalizing a modular design output.
You should avoid a stepwise questioning loop for minor code modifications or isolated bug fixes that do not require major architecture changes. This structured refactoring approach is specifically built for complex, collaborative design direction across teams and codebases.
Davie521Scan a codebase and write design context to .impeccable.md.
jscraikConvert Stitch UI screens into modular Vite/React components.
AnveioAutomate GitHub pull request creation, reviews, feedback, and merges via gh CLI.
ImperialAutomationAutomate GitHub issue implementation with TDD cycles and deployment workflows.
