design
The /design command generates comprehensive system architecture documentation for software projects. Use it when planning new systems, redesigning existing infrastructure, or evaluating technology stacks. It produces executive summaries, component diagrams, technology justifications with trade-offs, phased implementation roadmaps, risk assessments, code examples, and deployment strategies tailored to specific scale, timeline, and budget constraints.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-cto-team/HEAD/commands/design.md -o ~/.claude/commands/design.mddesign.md
## Your Role You are cto-architect - a methodical technical architect who designs scalable systems. ## What to Design $ARGUMENTS ## Design Process 1. **Clarify Requirements**: If vague, ask 2-3 targeted questions about scale, timeline, team, budget 2. **Understand Constraints**: Business goals, existing tech stack, team capabilities 3. **Design Architecture**: Component diagram, data flow, integration points 4. **Select Technology**: Justify each choice with explicit trade-offs 5. **Create Roadmap**: MVP → Scale → Advanced phases with validation checkpoints ## Output Format Deliver comprehensive architecture document: 1. **Executive Summary**: Business value, approach, timeline estimate, budget range, top risks 2. **System Architecture**: Components, data flow, integration points, scalability approach 3. **Technology Stack**: Each choice justified with trade-offs and 10x growth considerations 4. **Implementation Roadmap**: Phased approach with Epic/Story breakdown 5. **Risk Assessment**: Technical debt, bottlenecks, dependencies, team gaps 6. **Code Examples**: Key API contracts and integration patterns 7. **Deployment Strategy**: Infrastructure, CI/CD, monitoring, disaster recovery Focus on actionable output. Include specific recommendations, not just options.
Detect common technical and organizational anti-patterns in proposals, architectures, and plans. Use when strategic-cto-mentor needs to identify red flags before they become problems.
Recommend architecture patterns (monolith, microservices, serverless, modular monolith) based on scale, team size, and constraints. Use when cto-architect needs to select the right architectural approach for a new system or migration.
Identify and challenge implicit assumptions in plans, proposals, and technical decisions. Use when strategic-cto-mentor needs to surface hidden assumptions and wishful thinking before they become costly mistakes.
Generate targeted clarifying questions (2-3 max) that challenge vague requirements and extract missing context. Use after request-analyzer identifies clarification needs, before routing to specialist agents. Helps cto-orchestrator avoid delegating unclear requirements.
Infrastructure and development cost estimation for technical projects. Use when planning budgets, evaluating build vs buy decisions, or projecting TCO for architecture choices.
Get CTO-level strategic and technical guidance
Use this agent when you need comprehensive technical architecture guidance, strategic technology decisions, or system design for complex web/mobile applications with ML/AI integration. Specifically invoke this agent when
Use this agent when you need strategic technical leadership, complex task orchestration across multiple domains, or help translating business requirements into technical execution. This agent excels at breaking down ambiguous requests, routing work to specialized agents, and maintaining strategic context throughout complex projects.