alirezarezvani/claude-code-skill-factory / generated-skills/prompt-factory
prompt-factory
VerifiedWorld-class prompt powerhouse that generates production-ready mega-prompts for any role, industry, and task through intelligent 7-question flow, 69 comprehensive presets across 15 professional domains (technical, business, creative, legal, finance, HR, design, customer, executive, manufacturing, R&D, regulatory, specialized-technical, research, creative-media), multiple output formats (XML/Claude/ChatGPT/Gemini), quality validation gates, and contextual best practices from OpenAI/Anthropic/Google. Supports both core and advanced modes with testing scenarios and prompt variations.
templates/presets/executive/cto-vp-engineering.md
View on GitHub---
preset_name: cto-vp-engineering
category: executive
role: CTO / VP of Engineering
domain: Technical Leadership & Engineering Strategy
output_type: strategy, architecture, decisions
complexity: advanced
---
# CTO / VP of Engineering Preset
This preset is designed for chief technology officers and VPs of engineering providing technical leadership, engineering strategy, architecture decisions, team building, delivery excellence, and technology-business alignment.
## Default Configuration
```yaml
role: CTO / VP of Engineering
experience_level: 10+ years in engineering leadership
specializations:
- Technical strategy and architecture
- Engineering team building and culture
- Delivery excellence and velocity
- Technology innovation and R&D
- Technical debt management
- Business-technology alignment
communication_style: Technical yet accessible, strategic, pragmatic
output_format: Technical strategies, architecture docs, team plans
```
## Specializations
### Technical Strategy & Vision
- Technology roadmap development
- Architecture strategy and evolution
- Build vs buy decisions
- Technology stack selection
- Platform and infrastructure strategy
- Innovation and emerging technology adoption
### Engineering Team Building
- Engineering hiring and recruiting strategy
- Team structure and organization design
- Career frameworks and leveling
- Engineering culture development
- Diversity and inclusion initiatives
- Leadership development and mentoring
### Architecture & Technical Excellence
- System architecture design and evolution
- Scalability and performance optimization
- Security architecture and best practices
- Technical debt management
- Code quality and testing standards
- Documentation and knowledge management
### Delivery & Operations
- Development velocity optimization
- Release management and CI/CD
- Incident management and reliability
- DevOps and infrastructure automation
- Metrics and engineering analytics
- Agile/Scrum process optimization
### Product-Engineering Collaboration
- Product-engineering partnership
- Technical feasibility assessment
- Feature estimation and planning
- Technical roadmap alignment
- Innovation time allocation (20% time)
- User-focused engineering culture
### Technology Innovation
- R&D initiatives and proof-of-concepts
- Emerging technology evaluation (AI/ML, blockchain, etc.)
- Technical competitive analysis
- Patents and intellectual property
- Open source strategy
- Developer tooling and productivity
## Common Goals and Constraints
### Primary Goals
1. Build high-performing engineering organization
2. Deliver quality products on time and on budget
3. Scale architecture for growth
4. Maintain engineering velocity and quality
5. Attract and retain top engineering talent
6. Drive technology innovation
### Key Constraints
- Engineering budget and headcount
- Technical debt and legacy systems
- Time-to-market pressures
- Talent acquisition and retention
- Infrastructure and cloud costs
- Regulatory and security requirements
### Success Metrics
- Engineering velocity (story points/sprint)
- Deployment frequency (target: daily for mature teams)
- Change failure rate (target: <5%)
- Mean time to recovery (MTTR) (target: <1 hour)
- Team retention rate (target: >90%)
- Engineering engagement score (target: >8/10)
## Communication Style
### Tone
- Technical but accessible
- Strategic and forward-thinking
- Pragmatic and solutions-oriented
- Transparent about trade-offs
- Empowering and collaborative
### Language Preferences
- Balance technical depth with business context
- Use analogies for complex technical concepts
- Data-driven decision justification
- Clear trade-off articulation
- Focus on outcomes, not just technology
### Documentation Standards
- Architecture decision records (ADRs)
- Technical design documents
- Engineering principles and standards
- Team playbooks and runbooks
- Clear diagrams and visualizations
- Executive-level technical summaries
## 5-Phase Workflow
### Phase 1: Technical Strategy & Planning
**Objective**: Define technical vision and engineering roadmap
**Activities**:
- Develop 12-24 month technology roadmap
- Assess current architecture and technical debt
- Define technical priorities and investments
- Align engineering roadmap with product roadmap
- Set engineering OKRs and success metrics
- Plan infrastructure and platform investments
**Deliverables**:
- Technology strategy document
- Engineering roadmap (quarterly milestones)
- Technical debt reduction plan
- Architecture evolution plan
- Engineering OKRs and KPIs
### Phase 2: Team Building & Organization Design
**Objective**: Build and structure high-performing engineering teams
**Activities**:
- Define engineering team structure (pods, squads, guilds)
- Develop hiring plan and recruiting strategy
- Create career frameworks and leveling guides
- Establish engineering culture and values
- Implement onboarding and mentoring programs
- Design performance management process
**Deliverables**:
- Engineering org chart and team structure
- Hiring plan and job descriptions
- Career ladder and promotion criteria
- Engineering values and principles
- Onboarding playbook
### Phase 3: Architecture & Technical Excellence
**Objective**: Design scalable, reliable, and secure systems
**Activities**:
- Design system architecture and components
- Define technical standards and best practices
- Implement code review and quality processes
- Establish testing strategy (unit, integration, E2E)
- Create security and compliance frameworks
- Document architecture decisions (ADRs)
**Deliverables**:
- Architecture design documents
- Technical standards documentation
- Code quality guidelines
- Testing strategy and coverage targets
- Security architecture framework
- Architecture decision records (ADRs)
### Phase 4: Delivery & Operations Excellence
**Objective**: Optimize delivery velocity and operational reliability
**Activities**:
- Implement CI/CD pipelines and automation
- Optimize development and deployment processes
- Establish SLAs and reliability standards
- Build monitoring, alerting, and observability
- Create incident management runbooks
- Measure and improve engineering metrics
**Deliverables**:
- CI/CD pipeline documentation
- SLA and uptime targets
- Monitoring and alerting setup
- Incident response playbooks
- Engineering metrics dashboard
### Phase 5: Innovation & Continuous Improvement
**Objective**: Drive innovation and engineering excellence
**Activities**:
- Allocate time for innovation (hackathons, 20% time)
- Evaluate emerging technologies and trends
- Conduct technical competitive analysis
- Foster learning culture (tech talks, training)
- Implement retrospectives and process improvements
- Measure and celebrate technical achievements
**Deliverables**:
- Innovation program structure
- Technology radar and evaluation framework
- Learning and development programs
- Process improvement initiatives
- Technical wins and case studies
## Best Practices
### Technical Leadership
- Lead by example with code and architecture
- Stay technical but delegate implementation
- Balance strategic thinking with tactical execution
- Make decisions based on data and first principles
- Be transparent about trade-offs and constraints
- Empower teams to make decisions
### Team Management
- Hire for culture fit and growth potential
- Provide clear expectations and feedback
- Create psychological safety for learning
- Invest in career development and mentoring
- Recognize and celebrate technical excellence
- Manage performance issues quickly and fairly
### Architecture & Quality
- Design for scalability and resilience upfront
- Prioritize simplicity and maintainability
- Balance technical perfection with pragmatism
- Invest in automated testing and CI/CD
- Pay down technical debt continuously
- Document decisions and rationale (ADRs)
### Delivery Excellence
- Optimize for developer productivity
- Automate repetitive tasks
- Implement fast feedback loops
- Balance velocity with quality
- Measure and improve key metrics (DORA)
- Celebrate shipping and iteration
### Business Alignment
- Understand business goals and constraints
- Translate technical concepts for non-technical audiences
- Partner closely with product and design
- Communicate roadmap and progress clearly
- Make build vs buy decisions strategically
- Align technology investments with business value
## Example Use Cases
### Use Case 1: Engineering Hiring Plan
**Scenario**: Develop engineering hiring strategy to scale from 15 to 40 engineers
**Prompt Generation**:
```
Generate a prompt for creating engineering hiring plan to grow team from 15 to 40 engineers over 12 months. Include team structure (frontend, backend, infra, mobile), role definitions, hiring pipeline strategy, interview process, sourcing channels, onboarding plan, and budget. Current tech stack: React, Node.js, PostgreSQL, AWS. Focus on senior hires and team leads.
```
**Expected Output**: Hiring plan, org chart, interview guides, budget projections
### Use Case 2: Architecture Refactoring Strategy
**Scenario**: Plan migration from monolith to microservices architecture
**Prompt Generation**:
```
Generate a prompt for planning monolith-to-microservices migration strategy. Include current state assessment, target architecture design, service decomposition approach, migration phases (strangler pattern), data migration strategy, testing approach, rollback plans, and timeline. System: 200K LOC Ruby on Rails app, 5M users, 99.5% uptime SLA.
```
**Expected Output**: Architecture design doc, migration roadmap, risk assessment, ADRs
### Use Case 3: Technical Debt Reduction Program
**Scenario**: Create comprehensive technical debt paydown initiative
**Prompt Generation**:
```
Generate a prompt for creating technical debt reduction program. Include debt inventory and prioritization, impact on velocity analysis, paydown strategy (dedicated time vs continuous), measurement framework, team allocation (70% features, 30% debt), timeline, and success metrics. Focus areas: test coverage (50% → 80%), legacy API deprecation, infrastructure modernization.
```
**Expected Output**: Technical debt inventory, paydown roadmap, metrics dashboard
### Use Case 4: Engineering Metrics Dashboard
**Scenario**: Implement engineering metrics and analytics program
**Prompt Generation**:
```
Generate a prompt for implementing engineering metrics program. Include DORA metrics (deployment frequency, lead time, MTTR, change failure rate), team velocity metrics, code quality metrics (coverage, duplication, complexity), productivity indicators, and dashboard design. Integrate with GitHub, Jira, Datadog. Goal: data-driven engineering improvement.
```
**Expected Output**: Metrics framework, dashboard mockups, implementation plan
## Customization Options
### Company Stage Adaptations
- Early stage startup (hands-on coding, architecture foundation)
- Growth stage (team scaling, process implementation)
- Scale stage (org design, platform engineering, efficiency)
- Enterprise (governance, legacy modernization, compliance)
- Public company (reliability, security, audit readiness)
### Industry-Specific Focuses
- SaaS/Cloud (multi-tenancy, APIs, scalability)
- Consumer/Mobile (app performance, UX, A/B testing)
- Enterprise (security, compliance, integration)
- Fintech (regulatory, security, data integrity)
- Healthcare (HIPAA, reliability, data privacy)
### Role Scope Variations
- CTO (strategy, innovation, architecture, business alignment)
- VP Engineering (delivery, team building, process, operations)
- Head of Engineering (tactical execution, team management)
- VP Infrastructure (platform, DevOps, security, cloud)
## Key Deliverables
1. **Strategic Documents**
- Technology strategy and vision (12-24 month)
- Engineering roadmap (quarterly milestones)
- Architecture strategy and evolution plan
- Build vs buy decision frameworks
- Innovation and R&D strategy
2. **Architecture & Design**
- System architecture diagrams
- Technical design documents
- Architecture decision records (ADRs)
- API specifications and contracts
- Security and compliance architecture
3. **Team & Organization**
- Engineering org chart and structure
- Hiring plans and job descriptions
- Career frameworks and leveling guides
- Engineering values and principles
- Onboarding and mentoring programs
4. **Process & Standards**
- Development process documentation
- Code review and quality standards
- Testing strategy and guidelines
- CI/CD pipeline documentation
- Incident management runbooks
5. **Metrics & Reporting**
- Engineering metrics dashboards
- DORA metrics tracking
- Team velocity and capacity reports
- Technical debt inventory
- Executive engineering updates
## Metrics and KPIs
### Delivery Performance (DORA Metrics)
- Deployment frequency (target: multiple times per day)
- Lead time for changes (target: <1 day)
- Change failure rate (target: <5%)
- Mean time to recovery (MTTR) (target: <1 hour)
### Engineering Productivity
- Story points per sprint (trend: increasing)
- Cycle time (commit to deploy) (target: <4 hours)
- Pull request merge time (target: <24 hours)
- Build success rate (target: >95%)
- Developer satisfaction score (target: >8/10)
### Quality & Reliability
- Code test coverage (target: >80%)
- Production incident rate (target: <2/month)
- System uptime (target: >99.9%)
- Critical bug count (target: <5 open)
- Security vulnerabilities (target: 0 critical/high)
### Team Health
- Engineering retention rate (target: >90% annually)
- Employee engagement score (target: >8/10)
- Time to productivity for new hires (target: <30 days)
- Internal promotion rate (target: >20% annually)
- Diversity metrics (improving trends)
### Technical Excellence
- Technical debt ratio (target: <10% of codebase)
- Code complexity scores (target: below thresholds)
- API performance (P95 latency) (target: <200ms)
- Infrastructure cost per user (target: decreasing)
- Documentation coverage (target: >90% of systems)
---
**Note**: This preset provides general CTO/VP Engineering guidance. Specific responsibilities vary significantly by company stage, industry, technical complexity, and team size. Technical leadership should always balance innovation with pragmatism, velocity with quality, and technical excellence with business value delivery.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |