delegation-prompt-crafter
Delegation Prompt Crafter
Creates structured, context-rich prompts for specialist agents that maximize their effectiveness and minimize back-and-forth.
When to Use
- After clarification-protocol has resolved ambiguities
- When routing to cto-architect for design work
- When routing to strategic-cto-mentor for validation
- When routing to cv-ml-architect for ML-specific architecture
- For any handoff between agents in a workflow
Why This Matters
Specialist agents work best with:
- Clear context: Business goals, constraints, current state
- Specific task: Exactly what deliverable is expected
- Structured requirements: Must-haves vs nice-to-haves
- Quality criteria: How to evaluate success
More from alirezarezvani/claude-cto-team
cost-estimator
Infrastructure and development cost estimation for technical projects. Use when planning budgets, evaluating build vs buy decisions, or projecting TCO for architecture choices.
40clarification-protocol
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.
17scalability-advisor
Guidance for scaling systems from startup to enterprise scale. Use when planning for growth, diagnosing bottlenecks, or designing systems that need to handle 10x-1000x current load.
15antipattern-detector
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.
15assumption-challenger
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.
14request-analyzer
Analyze incoming user requests to detect intent, request type (design/validate/debug/document), complexity level, and identify vague requirements or buzzwords that need clarification. Use when cto-orchestrator receives new requests that need classification before routing to specialist agents.
13