modernize

Command /architect:modernize

Analyze legacy codebase and create a phased modernization plan using Strangler Fig pattern.

Instructions

Step 1: Discover Project Structure

# Find all Python files
find {{ path | default: "." }} -name "*.py" -type f | head -50

# Check for common patterns
ls -la {{ path | default: "." }}

Use Glob and Grep to understand the codebase:

• Find entry points (main.py, app.py, wsgi.py)
• Identify frameworks (Flask, Django, FastAPI)
• Locate models, views/routes, services

Step 2: Analyze Current Architecture

Check for architectural patterns:

# Look for layered architecture
Glob: **/models.py, **/views.py, **/services.py, **/repositories.py

# Look for module structure
Glob: **/modules/*/__init__.py, **/apps/*/__init__.py

# Find configuration
Glob: **/config.py, **/settings.py, **/.env.example

Identify anti-patterns:

Anti-Pattern	Detection
God Objects	Classes > 500 lines, > 20 methods
Circular Dependencies	Imports inside functions
No Separation	Business logic in views/routes
Global State	Module-level mutable variables

Step 3: Map Dependencies

Internal dependencies:

# Find imports between modules
Grep: "from src\." or "from app\."

External dependencies:

# Check requirements
cat requirements.txt 2>/dev/null || cat pyproject.toml 2>/dev/null

Database dependencies:

• Find all models and their relationships
• Identify shared tables between modules
• Check for raw SQL queries

Step 4: Assess Test Coverage

# Check for existing tests
find {{ path | default: "." }} -name "test_*.py" -o -name "*_test.py" | wc -l

# Check pytest configuration
cat pytest.ini 2>/dev/null || cat pyproject.toml | grep -A 20 "\[tool.pytest"

Step 5: Identify Critical Paths

Analyze which code paths are:

1. High traffic — frequently executed
2. High risk — complex, poorly tested
3. High value — core business logic