refactor-gate
Ask whether to proceed with refactoring after architecture mapping.
When & Why to Use This Skill
The refactor_gate Claude skill serves as a critical decision-making checkpoint within the software development lifecycle. It bridges the gap between architecture mapping and code implementation by ensuring a human-in-the-loop confirmation before proceeding with refactoring. This skill optimizes developer workflows by automating the creation of planning documentation (PLANS.md, IMPACT.md) or capturing technical debt in a backlog, ensuring that structural changes are intentional and well-documented.
Use Cases
- Workflow Governance: Implementing a mandatory 'gate' after architectural analysis to prevent unauthorized or premature code changes.
- Technical Debt Management: Automatically capturing refactoring suggestions into a BACKLOG.md when the user decides not to proceed immediately, preserving valuable insights for future sprints.
- Automated Documentation: Streamlining the transition to implementation by auto-generating impact assessments and action plans once a refactor is approved.
- Project Scoping: Helping developers pause and evaluate the necessity of structural changes against current project timelines and priorities.
| name | refactor_gate |
|---|---|
| description | Ask whether to proceed with refactoring after architecture mapping. |
| short-description | Refactor gate |
Purpose
Confirm whether to continue into refactoring after mapping.
Steps
- Ask if the user wants to start refactoring now.
- If yes, create/update
PLANS.mdandIMPACT.md, then proceed. - If no, capture refactor ideas in
BACKLOG.mdand stop. - Ask only once and keep it short.