본문으로 건너뛰기
cccskills
무료GitHub에 공개

cto-advisor

Plan technology strategy and engineering team growth with frameworks for technical debt, hiring, architecture decisions, and vendor evaluation. Use Python tools and decision templates to prioritize improvements, structure teams, and track engineering performance.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Technical leadership guidance for engineering teams, architecture decisions, and technology strategy. Includes tech debt analyzer, team scaling calculator, engineering metrics frameworks, technology evaluation tools, and ADR templates. Use when assessing technical debt, scaling engineering teams, evaluating technologies, making architecture decisions, establishing engineering metrics, or when user mentions CTO, tech debt, technical debt, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, or technology strategy.

연동 도구Slack
설치 방법 보기

이럴 때 유용합니다

  • Prioritizing technical debt reduction
  • Planning hiring and engineering team structure
  • Comparing technologies and vendors
  • Documenting architecture decisions
  • Defining engineering performance metrics

포함된 파일(6)

  • SKILL.md9.3 KB
  • references/architecture_decision_records.md8.5 KB
  • references/engineering_metrics.md12.1 KB
  • references/technology_evaluation_framework.md9.6 KB
  • scripts/team_scaling_calculator.py19.5 KB
  • scripts/tech_debt_analyzer.py16.9 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

CTO Advisor

Strategic frameworks and tools for technology leadership, team scaling, and engineering excellence.

Keywords

CTO, chief technology officer, technical leadership, tech debt, technical debt, engineering team, team scaling, architecture decisions, technology evaluation, engineering metrics, DORA metrics, ADR, architecture decision records, technology strategy, engineering leadership, engineering organization, team structure, hiring plan, technical strategy, vendor evaluation, technology selection

Quick Start

For Technical Debt Assessment

python scripts/tech_debt_analyzer.py

Analyzes system architecture and provides prioritized debt reduction plan.

For Team Scaling Planning

python scripts/team_scaling_calculator.py

Calculates optimal hiring plan and team structure for growth.

For Architecture Decisions

Review references/architecture_decision_records.md for ADR templates and examples.

For Technology Evaluation

Use framework in references/technology_evaluation_framework.md for vendor selection.

For Engineering Metrics

Implement KPIs from references/engineering_metrics.md for team performance tracking.

Core Responsibilities

1. Technology Strategy

Vision & Roadmap

  • Define 3-5 year technology vision
  • Create quarterly roadmaps
  • Align with business strategy
  • Communicate to stakeholders

Innovation Management

  • Allocate 20% time for innovation
  • Run hackathons quarterly
  • Evaluate emerging technologies
  • Build proof of concepts

Technical Debt Strategy

# Assess current debt
python scripts/tech_debt_analyzer.py

# Allocate capacity
- Critical debt: 40% capacity
- High debt: 25% capacity  
- Medium debt: 15% capacity
- Low debt: Ongoing maintenance

2. Team Leadership

Scaling Engineering

# Calculate scaling needs
python scripts/team_scaling_calculator.py

# Key ratios to maintain:
- Manager:Engineer = 1:8
- Senior:Mid:Junior = 3:4:2
- Product:Engineering = 1:10
- QA:Engineering = 1.5:10

Performance Management

  • Set clear OKRs quarterly
  • Conduct 1:1s weekly
  • Review performance quarterly
  • Provide growth opportunities

Culture Building

  • Define engineering values
  • Establish coding standards
  • Create learning programs
  • Foster collaboration

3. Architecture Governance

Decision Making

Use ADR template from references/architecture_decision_records.md:

  1. Document context and problem
  2. List all options considered
  3. Record decision and rationale
  4. Track consequences

Technology Standards

  • Language choices
  • Framework selection
  • Database standards
  • Security requirements
  • API design guidelines

System Design Review

  • Weekly architecture reviews
  • Design documentation standards
  • Prototype requirements
  • Performance criteria

4. Vendor Management

Evaluation Process

Follow framework in references/technology_evaluation_framework.md:

  1. Gather requirements (Week 1)
  2. Market research (Week 1-2)
  3. Deep evaluation (Week 2-4)
  4. Decision and documentation (Week 4)

Vendor Relationships

  • Quarterly business reviews
  • SLA monitoring
  • Cost optimization
  • Strategic partnerships

5. Engineering Excellence

Metrics Implementation

From references/engineering_metrics.md:

DORA Metrics (Deploy to production targets):

  • Deployment Frequency: >1/day
  • Lead Time: <1 day
  • MTTR: <1 hour
  • Change Failure Rate: <15%

Quality Metrics:

  • Test Coverage: >80%
  • Code Review: 100%
  • Technical Debt: <10%

Team Health:

  • Sprint Velocity: ±10% variance
  • Unplanned Work: <20%
  • On-call Incidents: <5/week

Weekly Cadence

Monday

  • Leadership team sync
  • Review metrics dashboard
  • Address escalations

Tuesday

  • Architecture review
  • Technical interviews
  • 1:1s with directs

Wednesday

  • Cross-functional meetings
  • Vendor meetings
  • Strategy work

Thursday

  • Team all-hands (monthly)
  • Sprint reviews (bi-weekly)
  • Technical deep dives

Friday

  • Strategic planning
  • Innovation time
  • Week recap and planning

Quarterly Planning

Q1 Focus: Foundation

  • Annual planning
  • Budget allocation
  • Team goal setting
  • Technology assessment

Q2 Focus: Execution

  • Major initiatives launch
  • Mid-year hiring push
  • Performance reviews
  • Architecture evolution

Q3 Focus: Innovation

  • Hackathon
  • Technology exploration
  • Team development
  • Process optimization

Q4 Focus: Planning

  • Next year strategy
  • Budget planning
  • Promotion cycles
  • Debt reduction sprint

Crisis Management

Incident Response

  1. Immediate (0-15 min):

    • Assess severity
    • Activate incident team
    • Begin communication
  2. Short-term (15-60 min):

    • Implement fixes
    • Update stakeholders
    • Monitor systems
  3. Resolution (1-24 hours):

    • Verify fix
    • Document timeline
    • Customer communication
  4. Post-mortem (48-72 hours):

    • Root cause analysis
    • Action items
    • Process improvements

Types of Crises

Security Breach

  • Isolate affected systems
  • Engage security team
  • Legal/compliance notification
  • Customer communication plan

Major Outage

  • All-hands response
  • Status page updates
  • Executive briefings
  • Customer outreach

Data Loss

  • Stop writes immediately
  • Assess recovery options
  • Begin restoration
  • Impact analysis

Stakeholder Management

Board/Executive Reporting

Monthly:

  • KPI dashboard
  • Risk register
  • Major initiatives status

Quarterly:

  • Technology strategy update
  • Team growth and health
  • Innovation highlights
  • Budget review

Cross-functional Partners

Product Team

  • Weekly roadmap sync
  • Sprint planning participation
  • Technical feasibility reviews
  • Feature estimation

Sales/Marketing

  • Technical sales support
  • Product capability briefings
  • Customer reference calls
  • Competitive analysis

Finance

  • Budget management
  • Cost optimization
  • Vendor negotiations
  • Capex planning

Strategic Initiatives

Digital Transformation

  1. Assess current state
  2. Define target architecture
  3. Create migration plan
  4. Execute in phases
  5. Measure and adjust

Cloud Migration

  1. Application assessment
  2. Migration strategy (7Rs)
  3. Pilot applications
  4. Full migration
  5. Optimization

Platform Engineering

  1. Define platform vision
  2. Build core services
  3. Create self-service tools
  4. Enable team adoption
  5. Measure efficiency

AI/ML Integration

  1. Identify use cases
  2. Build data infrastructure
  3. Develop models
  4. Deploy and monitor
  5. Scale adoption

Communication Templates

Technology Strategy Presentation

1. Executive Summary (1 slide)
2. Current State Assessment (2 slides)
3. Vision & Strategy (2 slides)
4. Roadmap & Milestones (3 slides)
5. Investment Required (1 slide)
6. Risks & Mitigation (1 slide)
7. Success Metrics (1 slide)

Team All-hands

1. Wins & Recognition (5 min)
2. Metrics Review (5 min)
3. Strategic Updates (10 min)
4. Demo/Deep Dive (15 min)
5. Q&A (10 min)

Board Update Email

Subject: Engineering Update - [Month]

Highlights:
• [Major achievement]
• [Key metric improvement]
• [Strategic progress]

Challenges:
• [Issue and mitigation]

Next Month:
• [Priority 1]
• [Priority 2]

Detailed metrics attached.

Tools & Resources

Essential Tools

  • Architecture: Draw.io, Lucidchart, C4 Model
  • Metrics: DataDog, Grafana, LinearB
  • Planning: Jira, Confluence, Notion
  • Communication: Slack, Zoom, Loom
  • Development: GitHub, GitLab, Bitbucket

Key Resources

  • Books:

    • "The Manager's Path" - Camille Fournier
    • "Accelerate" - Nicole Forsgren
    • "Team Topologies" - Skelton & Pais
  • Frameworks:

    • DORA metrics
    • SPACE framework
    • Team Topologies
  • Communities:

    • CTO Craft
    • Engineering Leadership Slack
    • LeadDev community

Success Indicators

✅ Technical Excellence

  • System uptime >99.9%
  • Deploy multiple times daily
  • Technical debt <10% capacity
  • Security incidents = 0

✅ Team Success

  • Team satisfaction >8/10
  • Attrition <10%
  • Filled positions >90%
  • Diversity improving

✅ Business Impact

  • Features on-time >80%
  • Engineering enables revenue
  • Cost per transaction decreasing
  • Innovation driving growth

Red Flags to Watch

⚠️ Increasing technical debt
⚠️ Rising attrition rate
⚠️ Slowing velocity
⚠️ Growing incidents
⚠️ Team morale declining
⚠️ Budget overruns
⚠️ Vendor dependencies
⚠️ Security vulnerabilities

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Create interactive 3D scenes for websites, including product views and scroll-driven animations. Covers choosing Three.js, React Three Fiber, or Spline, preparing lightweight models, showing loading progress, and adapting experiences for mobile devices.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Building an interactive 3D product configurator
  • Adding 3D scenes to a portfolio
  • Animating models and cameras as visitors scroll
davila7/claude-code-templates3.3만2026년 10월 18일 업데이트

Plan A/B tests that compare page or product changes, with clear hypotheses, sample sizes, success metrics, and traffic allocation. Get a structured test plan and guidance for interpreting results and deciding what to try next.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Comparing signup button copy
  • Planning a pricing page experiment
  • Estimating sample size and test duration
davila7/claude-code-templates3.3만2026년 10월 18일 업데이트

Prepare an academic CV for faculty, postdoctoral, or research applications. Organize publications, grants, teaching, and research experience, with section order and formatting adapted to the role and academic field.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Preparing a CV for faculty applications
  • Updating a CV for postdoctoral applications
  • Organizing publications and research funding
davila7/claude-code-templates3.3만2026년 10월 18일 업데이트

Audit and improve web accessibility using WCAG 2.1 guidelines. Covers image descriptions, color contrast, keyboard controls, forms, and screen reader support, with code examples and automated and manual checks to guide fixes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Auditing accessibility before a website launch
  • Improving keyboard navigation
  • Fixing form labels and error announcements
davila7/claude-code-templates3.3만2026년 10월 18일 업데이트

Audit websites for accessibility barriers and improve image descriptions, color contrast, forms, keyboard navigation, and screen reader support. Provides code examples and automated and manual testing guidance for work toward WCAG 2.1 AA or AAA accessibility standards.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Auditing a website for accessibility issues
  • Fixing form labels and error announcements
  • Checking keyboard navigation and dialog focus
davila7/claude-code-templates3.3만2026년 10월 18일 업데이트

Design autonomous agents for Claude Code plugins, including when they should run, what tools they may use, and how they should respond. Provides configuration templates, prompt guidance, and validation steps for creating agent files.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Create a code review agent
  • Refine examples that trigger an agent
  • Limit the tools an agent can use
davila7/claude-code-templates3.3만2026년 10월 18일 업데이트

davila7의 스킬 모두 보기

이 스킬의 문제 신고