cto-advisor
Audited by Runlayer on Feb 21, 2026
Malicious tool definition detected
Tool: SKILL.md [1/2] Description: --- name: cto-advisor description: 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.
Tool: SKILL.md [2/2] Description: slide) 2.
Malicious tool definition detected
Tool: references/architecture_decision_records.md [1/2] Description: # Architecture Decision Records (ADR) Framework ## What is an ADR? Architecture Decision Records capture important architectural decisions made along with their context and consequences.
Tool: references/architecture_decision_records.md [2/2] Description: relevance ## Decision Evaluation Framework ### Technical Factors (40%) - Performance impact - Scalability potential - Security implications - Maintainability - Technical debt ### Business Factors (30%) - Time to market - Cost (initial and ongoing) - Revenue impact - Competitive advantage - Regulatory compliance ### Team Factors (30%) - Current expertise - Learning curve - Hiring availability - Team preference - Training require
Malicious tool definition detected
Tool: references/engineering_metrics.md [1/2] Description: # Engineering Metrics & KPIs Guide ## Metrics Framework ### DORA Metrics (DevOps Research and Assessment) #### 1.
Tool: references/engineering_metrics.md [2/2] Description: **Bug Count Without Context**: Discourages risk-taking ❌ **Commit Count**: Encourages tiny commits ### Goodhart's Law "When a measure becomes a target, it ceases to be a good measure" **Examples**: - Optimizing test coverage → Writing meaningless tests - Reducing bug count → Not reporting bugs - Increasing velocity → Inflating estimates - Reducing meeting time → Skipping important discussions ### How to Avoid Gaming 1.
Malicious tool definition detected
Tool: references/technology_evaluation_framework.md [1/2] Description: # Technology Evaluation Framework ## Evaluation Process ### Phase 1: Requirements Gathering (Week 1) #### Functional Requirements - Core features needed - Integration requirements - Performance requirements - Scalability needs - Security requirements #### Non-Functional Requirements - Usability/Developer experience - Documentation quality - Community support - Vendor stability - Compliance needs #### Constraints - Budget limi
Tool: references/technology_evaluation_framework.md [2/2] Description: ] Integration points tested - [ ] Security requirements validated - [ ] Team feedback positive ### PoC Checklist - [ ] Environment setup documented - [ ] Test scenarios defined - [ ] Metrics collection automated - [ ] Team training completed - [ ] Results documented ### PoC Report Template ```markdown # PoC Report: [Technology Name] ## Executive Summary - **Recommendation**: [Proceed/Stop/Investigate Further] - **Confidence L
Malicious tool definition detected
Tool: scripts/team_scaling_calculator.py [1/2]
Tool: scripts/team_scaling_calculator.py [2/2]
Malicious tool definition detected
Tool: scripts/tech_debt_analyzer.py [1/2]
Tool: scripts/tech_debt_analyzer.py [2/2] Description: recommendations.append('Create dedicated debt reduction team') recommendations.append('Implement weekly debt reduction reviews') recommendations.append('Consider temporary feature freeze') elif results['debt_level'] in ['Medium-High', 'High']: recommendations.append('Allocate 25-30% of sprints to debt reduction') recommendations.append('Establish technical debt budget') recommendations.append('Implement debt prevention practices') else: reco