parallel-ready-django

Django Parallel Readiness Assessment

Audit and prepare a Django codebase to support parallel development with multiple Claude Code agents.

Quick Start

Run the full assessment:

1. Analyze Django project structure and app organization
2. Score each readiness dimension
3. Identify blockers and risks
4. Generate remediation plan
5. Set up orchestration infrastructure

Automated Analysis

Run the analysis script from project root:

# From project root (default: analyzes 'apps/' directory)
python analyze-readiness.py

# Specify custom apps directory
python analyze-readiness.py src/apps

# Output saved to .claude/readiness-report.md

The script analyzes:

• App Boundaries: Cross-app imports, circular dependencies, god apps
• Shared State: Global variables, Django signals, mutable state
• Contracts: Mypy config, OpenAPI, serializer __all__ usage
• Tests: Test file count, pytest config, Factory Boy usage
• Documentation: CLAUDE.md, README, linting config
• Dependencies: Lock files, pinned versions, migration count

See references/analyze-readiness.py for the full script.

Assessment Dimensions

1. Django App Boundaries (Critical)

Check for:

• Clear app separation with single responsibility
• Minimal cross-app model imports
• No circular dependencies between apps
• Proper use of app namespacing

Red flags:

• God app that contains most models/views
• Heavy cross-app foreign keys
• Shared models across multiple apps
• Deeply nested cross-app imports

Scoring:

• ✅ Good: Each domain has dedicated app, <10% cross-app model imports
• ⚠️ Fair: Some separation exists, 10-30% cross-imports
• ❌ Poor: Single app structure, heavy coupling, >30% cross-imports

Detection commands:

# Count models per app
find . -name "models.py" -exec grep -l "class.*Model" {} \;

# Find cross-app imports
grep -r "from.*\.models import" --include="*.py" | grep -v "__pycache__"

# Check for circular imports
python -c "import sys; sys.setrecursionlimit(50); import myapp"