⚡ EXECUTION INSTRUCTIONS FOR CLAUDE

When this command is invoked, YOU (Claude) must execute these steps immediately: This is NOT documentation - these are COMMANDS to execute right now. Use TodoWrite to track progress through multi-phase workflows.

🚨 EXECUTION WORKFLOW

Phase 1: Execute Documented Workflow

Action Steps:

1. Review the reference documentation below and execute the detailed steps sequentially.

📋 REFERENCE DOCUMENTATION

Principal Engineer Command

Purpose: Technical leadership, architecture decisions, and engineering excellence from senior engineering perspective

Usage: /principalengineer [scope]

Action: Provide technical leadership analysis covering architecture, scalability, maintainability, and engineering best practices

🎯 Engineering Leadership Focus Areas

Technical Architecture

• System Design: Scalability, reliability, and performance
• Technology Choices: Framework, library, and tool selection
• Design Patterns: Appropriate patterns for the problem domain
• Code Quality: Maintainability, readability, and robustness

Engineering Excellence

• Best Practices: Industry standards and proven approaches
• Testing Strategy: Coverage, reliability, and automation
• Performance: Optimization and resource efficiency
• Security: Threat modeling and secure coding practices

🔍 Analysis Framework

Technical Evaluation

1. Architecture Assessment: System boundaries, coupling, cohesion
2. Scalability Analysis: Growth handling and resource scaling
3. Maintainability Review: Code organization and development velocity
4. Performance Evaluation: Bottlenecks and optimization opportunities

Engineering Process Review

1. Development Workflow: CI/CD, testing, and deployment practices
2. Code Quality: Standards, reviews, and technical debt
3. Team Productivity: Tools, processes, and developer experience
4. Risk Management: Technical risks and mitigation strategies

Innovation and Growth

1. Technology Evolution: Keeping current with industry trends
2. Technical Debt: Identification and management strategies
3. Team Development: Knowledge sharing and skill building
4. Operational Excellence: Monitoring, logging, and incident response

📋 Typical Output

Technical Leadership Analysis:

• Architecture Review: System design strengths and improvements
• Technical Recommendations: Technology choices and patterns
• Engineering Standards: Code quality and best practices
• Scalability Assessment: Growth readiness and bottlenecks
• Risk Analysis: Technical risks and mitigation strategies
• Team Impact: Developer experience and productivity considerations
• Next Steps: Technical priorities and implementation guidance

🎯 Use Cases

Architecture Decision Review:

/principalengineer orchestration system design

# Evaluate technical architecture and patterns

Implementation Quality Assessment:

/principalengineer copilot workflow implementation

# Review code quality and engineering practices

Technology Choice Validation:

/principalengineer agent coordination approach

# Assess technology decisions and alternatives

Technical Debt Analysis:

/principalengineer codebase maintainability

# Identify technical debt and improvement opportunities

🔄 Integration

Works well with:

• /principalproductmanager: Business requirements → Technical feasibility
• /arch: System design → Implementation details
• /research: Technology options → Best practices
• /thinku: Technical assumptions → Engineering validation