workflow-refactoring

Enforce behavior-preserving refactoring workflows with test-guided RED→GREEN→REFACTOR cycles.

Updated Mar 2, 2026
One-click install
npx skills add https://github.com/akourmaz/translate2 --skill workflow-refactoring
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: workflow-refactoring
Source: https://github.com/akourmaz/translate2/tree/main/.agents/skills/workflow-refactoring
Command: npx skills add https://github.com/akourmaz/translate2 --skill workflow-refactoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Protocol for safe refactoring without changing system behavior, emphasizing safety analysis, test coverage, and phased execution to reduce risk. We focus on improving structure, readability, and technical debt while preserving functionality.

Core Features & Use Cases

  • Safety analysis and risk assessment
  • Test coverage checks and incremental validation
  • Phased RED→GREEN→REFACTOR workflow with scoped changes
  • Documentation artifacts and traceability (scope, Plan.md, Research.md)
  • Clear acceptance criteria and rollback guidance

Quick Start

Follow the steps to initiate a safe refactor and begin with an assessment of scope and tests.

Frequently Asked Questions about workflow-refactoring

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I refactor code safely without changing system behavior?

To refactor code safely, enforce a phased RED→GREEN→REFACTOR workflow with incremental steps, predefined scope, test coverage validation, and documented checkpoints to preserve functionality.

What is the best way to reduce technical debt through architectural refactoring?

The best way to reduce technical debt is performing a safety analysis, assessing risks, and executing phased module improvements guided by test coverage to ensure behavior preservation.

How do I use test-guided progress to plan phased code improvements?

You use test-guided progress by running incremental validation through RED→GREEN→REFACTOR cycles, ensuring test coverage checks pass at each documented checkpoint before advancing.

Do I need full test coverage before starting a safe refactoring workflow?

You need sufficient test coverage to validate behavior preservation, as the workflow requires test checks and incremental validation to guide each refactoring step safely.

When should I not use incremental refactoring for code cleanup?

You should avoid incremental refactoring without a predefined scope, test coverage, or rollback guidance, as safe execution depends on documented checkpoints and traceability artifacts.

Can I execute architectural debt reduction across multiple modules at once?

Architectural debt reduction requires scoped changes and incremental steps rather than simultaneous execution, using phased workflows with clear acceptance criteria to minimize risk.