super-ralph-refactor

To preserve behavior during an architecture migration, you can use a structured reverse bead-pack workflow augmented with a dedicated refactor question bank. This guides end-to-end tracing from initial analysis through consolidation, ensuring systematic review of existing logic before structural changes.

The reverse bead-pack approach is a structured workflow that guides architecture migration tasks through sequential analysis, design, and consolidation phases. It uses a bead graph and stamping procedure to inject specific question banks, ensuring thorough tracing and modular reuse during refactoring.

You inject refactor-specific questions by replacing the standard Question Bank section in the first bead's study instructions with a specialized refactor question bank. This modifies the base reverse workflow to target architecture migration while maintaining the original dependency wiring and stamping procedure.

Yes, you can use prompt templates to guide architecture migration by injecting a refactor-focused question bank into a structured workflow. This provides reusable, modular prompts that trace dependencies and deliver consistent analysis through a standardized stamping procedure.

Yes, this refactor workflow inherits the base reverse bead graph, dependency wiring, and stamping procedure. You must follow the base cadence exactly, only replacing the first bead's question bank with the provided refactor questions to execute architecture migration tasks.

You should avoid the reverse bead workflow for code refactoring if your task does not require end-to-end tracing from analysis through consolidation, or if your architecture migration lacks the need for a dedicated refactor question bank and strict behavior preservation constraints.