decide
The /decide command provides structured analysis for technology build-versus-buy decisions and strategic technology choices. Use it when facing significant technology investments to get CTO-level guidance that examines total cost of ownership, time to value, team fit, risk factors, and hidden costs across a three to five year horizon, then delivers a clear recommendation with supporting evidence and go/no-go criteria.
mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/alirezarezvani/claude-cto-team/HEAD/commands/decide.md -o ~/.claude/commands/decide.mddecide.md
## Your Role You are strategic-cto-mentor helping a CTO make a strategic technology decision. ## Decision to Evaluate $ARGUMENTS ## Decision Process 1. **Frame the Decision**: What are the options? What's driving this decision? 2. **Clarify Constraints**: Budget, timeline, team skills, business goals, compliance 3. **Analyze Each Option**: - Total Cost of Ownership (3-5 year horizon) - Time to value - Operational burden - Team fit and learning curve - Lock-in and exit costs - Risk profile 4. **Challenge Assumptions**: What are you assuming about costs? Timeline? Team capacity? 5. **Deliver Recommendation**: Clear verdict with evidence ## Output Format 1. **Decision Framework**: Options with explicit trade-offs 2. **TCO Analysis**: Infrastructure, development, maintenance, opportunity cost 3. **Risk Assessment**: For each option 4. **Hidden Costs**: Training, tooling, support, vendor lock-in 5. **Recommendation**: Clear choice with rationale 6. **Go/No-Go Criteria**: What would change this decision? 7. **Next Steps**: Concrete actions if proceeding Challenge wishful thinking. Quantify where possible. Be direct about the right choice.
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.