You are tasked with refactoring [Project Name] from its current implementation to [target implementation]. This refactor should maintain essential functionality while implementing the desired improvements and changes.
*Please provide specific technical references throughout (file paths, module names, class names, function signatures, API endpoints, etc.)*
**CORE OBJECTIVES**
*Define the business and technical goals driving this refactoring initiative.*
- **What are the primary goals of this refactoring initiative?**
- **What defines success for this refactor?**
**TARGET STATE DESCRIPTION**
*Provide a high-level description of what the refactored system should look like architecturally and functionally.*
- **Describe the target state of the refactored system**:
- Technology stack (languages, frameworks, libraries, databases)
- Overall architecture and design patterns
- Key modules, components, and their relationships
- External integrations and dependencies
- Configuration and deployment approach
- Any other architectural or technical considerations
**TECHNICAL IMPLEMENTATION DETAILS**
*Specify the detailed technical preferences, specific modules, APIs, and implementation approaches for achieving the target state.*
- **Which existing modules, classes, or components need to be modified, and how should they be changed?**
- **What external service integrations need to be implemented or updated?**
- **Are there any internal packages, libraries, or frameworks that the target state system depends on?**
- **What are the key interfaces, APIs, or contracts that need to be implemented?**
- **What are the most technically complex or challenging aspects of this refactor?**
**SYSTEM BOUNDARIES & CONSTRAINTS**
*Define what should remain unchanged and what functionality must be preserved during the refactor.*
- **What specific components, files, modules, or systems should not be touched during this refactor?**
- **What existing functionality must be preserved exactly as-is?**
**NON-FUNCTIONAL REQUIREMENTS**
*Specify quality attributes, operational requirements, and testing approaches for the refactored system.*
- **What performance, security, or compliance requirements must be maintained?**
- **What testing approach will ensure quality throughout the refactor?**
- **Are there specific operational requirements that must be considered?**
- **What areas of the plan would you like increased visibility into from the Agent Action Plan?**
**PRIVATE DEPENDENCIES + RUNNING THE CODE**
- **When building this project, do we need access to any internal dependencies, packages, or libraries?** *If yes, provide those within the repo(s) and reference these in the prompt.*
- **Are there any secrets, environment variables, or configurations required to compile and run the project successfully?** *List all non-sensitive configurations in the repository and reference where these are. For sensitive configurations, reach out to your AI Solutions Consultant directly to share securely.*
- **Do you have a complete, step-by-step set of build instructions that takes a developer from a clean machine to running the project?** *Provide build instructions directly here in the prompt. Additionally, if these instructions exist in documentation within your repo, indicate where this documentation lives. If submodules are used, confirm that their setup is documented in the parent repository.*
**MINIMAL CHANGE CLAUSE & REFACTOR DISCIPLINE GUIDELINES** *(Recommended for most Refactors)*
- IMPORTANT: Make only the changes that are absolutely necessary to implement this refactor.
- Maintain existing functionality exactly as-is and do not modify code beyond what is directly required for the technology transition. Your goal is to preserve current behavior while updating the underlying technology with minimal risk and disruption.
- IMPORTANT: Follow these Refactor Discipline Guidelines to ensure safe technology transition:
- Make only the minimal necessary changes to implement the refactor
- Preserve existing functionality and behavior exactly as-is
- Do not modify code that is not directly impacted by the technology transition
- Do not enhance or optimize code beyond the requirements of the migration
- Isolate new implementations in dedicated files/modules when possible
- Document all technology-specific changes with clear comments.
If your refactor targets a new repository (e.g., monolith decomposition), you must create the destination repository on your Git provider before starting the run. Blitzy cannot create repositories — it pushes to existing ones only. See GitHub Integration for details.
Rule Available — Add the Enforce Code Style Patterns rule to your project on the platform to ensure refactored code maintains existing architectural patterns and coding standards.