documentation-update-architecture

Architecture Documentation Update Guide

This prompt systematically updates architecture documentation to reflect current system design, architectural decisions, and technical evolution while maintaining comprehensive technical documentation standards.

🎯 OBJECTIVES:

1. UPDATE system architecture to reflect current design and implementation
2. MAINTAIN architectural decision records with current context and rationale
3. SYNCHRONIZE technical diagrams with actual system implementation
4. ENSURE design consistency across architecture documentation
5. VALIDATE architectural alignment with current development practices

📋 ARCHITECTURE UPDATE PROCESS:

STEP 1: Current Architecture Assessment

System State Analysis:

echo "🏗️ Current Architecture Assessment"
echo "================================"

# Analyze current system structure
echo "Project Structure Analysis:"
find src/ -type d -maxdepth 3 | sort

# Check architecture-related files
echo "Architecture Documentation:"
find docs/ -name "*architecture*" -o -name "*design*" -o -name "*adr*"

# Verify technology stack
echo "Current Technology Stack:"
grep -E "(dependencies|devDependencies)" package.json -A 20

# Check for architectural patterns
echo "Architectural Patterns in Use:"
find src/ -name "*.ts" -o -name "*.tsx" | head -10 | xargs grep -l "interface\|class\|type"

Architecture Change Detection:

• New system components added since last documentation update
• Technology stack changes affecting architectural decisions
• Design patterns that have evolved or been introduced
• Integration points that have been added or modified
• Performance considerations that have changed system design

Documentation Gap Analysis:

• Missing architectural decisions not yet documented
• Outdated diagrams not reflecting current system design
• Incomplete component descriptions missing current functionality
• Broken architectural patterns no longer accurately described
• Integration documentation not reflecting current connections