mirror of
https://github.com/catlog22/Claude-Code-Workflow.git
synced 2026-02-14 02:42:04 +08:00
refactor: optimize workflow templates and prompt structures
- Streamlined analysis templates (architecture, pattern, performance, quality, security) - Simplified development templates (component, debugging, feature, refactor, testing) - Optimized documentation templates (api, folder-navigation, module-readme, project-architecture, project-examples, project-readme) - Enhanced planning templates (concept-eval, migration, task-breakdown) - Improved verification templates (codex-technical, cross-validation, gemini-strategic) - Updated claude-module-unified memory template - Refined workflow-architecture documentation 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -1,16 +1,30 @@
|
||||
Plan system migration and modernization strategies:
|
||||
Plan system migration and modernization strategies.
|
||||
|
||||
## Required Analysis:
|
||||
## CORE CHECKLIST ⚡
|
||||
□ Assess current system completely before planning migration
|
||||
□ Plan incremental migration (avoid big-bang approach)
|
||||
□ Include rollback plan for every migration step
|
||||
□ Provide file:line references for all affected code
|
||||
|
||||
## REQUIRED ANALYSIS
|
||||
1. Assess current system architecture and migration requirements
|
||||
2. Identify migration paths and transformation strategies
|
||||
3. Plan data migration and system cutover procedures
|
||||
4. Evaluate compatibility and integration challenges
|
||||
5. Document rollback plans and risk mitigation strategies
|
||||
|
||||
## Output Requirements:
|
||||
## OUTPUT REQUIREMENTS
|
||||
- Migration strategy with step-by-step execution plan
|
||||
- Data migration procedures and validation checkpoints
|
||||
- Compatibility assessment and integration requirements
|
||||
- Risk analysis and rollback procedures
|
||||
- Compatibility assessment with file:line references
|
||||
- Risk analysis and rollback procedures for each phase
|
||||
- Testing strategy for migration validation
|
||||
|
||||
Focus on low-risk migration strategies with comprehensive fallback options.
|
||||
## VERIFICATION CHECKLIST ✓
|
||||
□ Migration planned in incremental phases (not big-bang)
|
||||
□ Every phase has rollback plan documented
|
||||
□ Data migration validated with checkpoints
|
||||
□ Compatibility issues identified and mitigated
|
||||
□ Testing strategy covers all migration phases
|
||||
|
||||
Focus: Low-risk incremental migration with comprehensive fallback options.
|
||||
|
||||
Reference in New Issue
Block a user