/design-architecture

name: design-architecture
description: Complete architecture design and documentation workflow using simple-architect and simple-architecture-documenter agents in parallel
version: 1.0.0
author: Claude Code Tutorial Series
category: architecture

Design Architecture Command

Automates the complete architecture design and documentation process by coordinating both simple-architect and simple-architecture-documenter agents in parallel workflow.

Usage

# Basic usage
/project:design-architecture "todo app for small team"

# With specific requirements
/project:design-architecture "e-commerce platform for 5-person startup with mobile app requirements"

# With complexity hints  
/project:design-architecture "chat application with real-time features, 1000+ users, small development team"

What This Command Does

1. **Parallel Agent Execution**: Runs simple-architect and simple-architecture-documenter simultaneously 2. **Intelligent Coordination**: Coordinates both agents to work on the same project requirements 3. **Complete Output**: Generates both architecture design decisions and professional documentation 4. **Time Efficiency**: Reduces 4-7 hours of manual work to 30 seconds - 2 minutes

Output Generated

From Simple-Architect Agent:

• Architecture pattern recommendation (monolith vs microservices)
• Complete technology stack with reasoning
• Database and caching strategy
• Security implementation plan
• API design approach
• Growth planning roadmap
• Architecture Decision Records (ADRs)

From Simple-Architecture-Documenter Agent:

• System Context diagram (C4 Level 1)
• Container diagram (C4 Level 2)
• Visual Mermaid diagrams with styling
• Complete ADR documentation
• System overview document
• API documentation template
• Technical decision summaries

Command Implementation

#!/bin/bash

# /project:design-architecture command implementation
# Coordinates simple-architect and simple-architecture-documenter agents

PROJECT_DESCRIPTION="$1"
TIMESTAMP=$(date +%Y%m%d_%H%M%S)
WORKFLOW_ID="arch_design_$TIMESTAMP"

# Validate input
if [ -z "$PROJECT_DESCRIPTION" ]; then
    echo "❌ Error: Please provide a project description"
    echo "Usage: /project:design-architecture \"your project description\""
    echo "Example: /project:design-architecture \"todo app for small team\""
    exit 1
fi

# Extract project characteristics
extract_project_info() {
    local desc="$1"
    
    # Detect project type
    if echo "$desc" | grep -qi "todo\|task"; then
        echo "PROJECT_TYPE=todo_app"
    elif echo "$desc" | grep -qi "chat\|messaging\|real.time"; then
        echo "PROJECT_TYPE=chat_app"
    elif echo "$desc" | grep -qi "ecommerce\|e-commerce\|shop\|store"; then
        echo "PROJECT_TYPE=ecommerce"
    elif echo "$desc" | grep -qi "blog\|content\|cms"; then
        echo "PROJECT_TYPE=content_management"
    else
        echo "PROJECT_TYPE=web_application"
    fi
    
    # Detect team size
    if echo "$desc" | grep -qi "large team\|10+\|team of 10\|15+ developers"; then
        echo "TEAM_SIZE=large"
    elif echo "$desc" | grep -qi "medium team\|5-10\|team of [5-9]"; then
        echo "TEAM_SIZE=medium"
    else
        echo "TEAM_SIZE=small"
    fi
    
    # Detect complexity indicators
    if echo "$desc" | grep -qi "simple\|basic\|minimal"; then
        echo "COMPLEXITY=low"
    elif echo "$desc" | grep -qi "enterprise\|complex\|advanced\|scalable"; then
        echo "COMPLEXITY=high"
    else
        echo "COMPLEXITY=medium"
    fi
}

# Extract project characteristics
eval $(extract_project_info "$PROJECT_DESCRIPTION")

echo "🚀 Initiating complete architecture workflow..."
echo "📋 Project: $PROJECT_DESCRIPTION"
echo "🏗️  Type: $PROJECT_TYPE | Team: $TEAM_SIZE | Complexity: $COMPLEXITY"
echo "🔄 Workflow ID: $WORKFLOW_ID"
echo ""

# Create coordinated prompts for both agents
create_architect_prompt() {
    cat << EOF
Design a comprehensive architecture for: $PROJECT_DESCRIPTION

PROJECT CHARACTERISTICS:
- Type: $PROJECT_TYPE
- Team Size: $TEAM_SIZE 
- Complexity: $COMPLEXITY

Please provide:
1. Architecture pattern recommendation with clear reasoning
2. Complete technology stack selection with trade-offs
3. Database architecture and caching strategy
4. Security implementation approach
5. API design patterns and reasoning
6. Deployment and scaling considerations
7. Key architectural decisions with ADRs
8. Growth planning for next 12-18 months

Focus on practical, implementable solutions that match the team size and project requirements.

Note: Documentation is being created in parallel - focus on technical decisions and reasoning.
EOF
}

create_documenter_prompt() {
    cat << EOF
Create comprehensive architecture documentation for: $PROJECT_DESCRIPTION

PROJECT CHARACTERISTICS:
- Type: $PROJECT_TYPE
- Team Size: $TEAM_SIZE
- Complexity: $COMPLEXITY

Please provide:
1. System Context diagram (C4 Level 1) showing all stakeholders and external systems
2. Container diagram (C4 Level 2) showing main application components
3. Complete ADR documentation for all major decisions
4. System overview document suitable for new team members
5. API documentation template with example endpoints
6. Technical decision summary with implementation notes
7. Documentation maintenance guidelines

Use Mermaid syntax for all diagrams with clear styling and emojis for visual clarity.

Note: Architecture design is happening in parallel - create comprehensive documentation framework.
EOF
}

# Create working directory
WORK_DIR="architecture_design_$WORKFLOW_ID"
mkdir -p "$WORK_DIR"
cd "$WORK_DIR"

echo "📁 Created working directory: $WORK_DIR"
echo ""

# Execute both agents in parallel
echo "🎯 Executing parallel architecture workflow..."
echo ""

# Start architect agent
echo "🏗️  Starting Simple Architect Agent..."
ARCHITECT_PROMPT=$(create_architect_prompt)
echo "$ARCHITECT_PROMPT" > architect_prompt.txt

# Start documenter agent  
echo "📋 Starting Simple Archite