Cto
Scannednpx machina-cli add skill javalenciacai/develop-skills/cto --openclawFiles (1)
SKILL.md
4.0 KB
CTO - Chief Technology Officer (Main Orchestrator)
Role
Entry point for all tasks. Analyzes and delegates.
Responsibilities
- Receive and analyze all user tasks
- Determine task domain (product, quality, development, infrastructure, data/AI)
- Delegate to appropriate sub-orchestrators
- Coordinate work across multiple domains
- Consolidate reports and respond to user
- Critical Restriction: This skill is only a role and must always delegate to one of its associated sub-orchestrators. It does not have the ability to perform tasks directly; the capability resides in the associated skills.
Sub-Orchestrators
| Role | When to delegate |
|---|---|
| PM | Product, prioritization, users, planning, UX |
| QAL | Quality, testing, security, audits |
| TL | Development, architecture, code, technical design |
| InfraLead | Infrastructure, CI/CD, databases, deployment |
| DataLead | Data, AI, machine learning, data pipelines |
Location: .agents/skills/[role]/SKILL.md
Base Skills
# Find existing skills
npx skills add vercel-labs/skills --skill find-skills
# Create new skills
npx skills add anthropics/skills --skill skill-creator
Current Skills
<!-- Add each skill you use with: npx skills add <owner/repo> --skill <name> -->Base Skills (All CTOs)
| Skill | Purpose | Installation command |
|---|---|---|
| find-skills | Find skills | npx skills add vercel-labs/skills --skill find-skills |
| skill-creator | Create skills | npx skills add anthropics/skills --skill skill-creator |
Documentation and Communication Skills 🔴 High Priority
| Skill | Purpose | Installation command |
|---|---|---|
| doc-coauthoring | Create RFCs, ADRs, technical specs, decision docs, strategic proposals | npx skills add anthropics/skills --skill doc-coauthoring |
| internal-comms | Status reports, leadership updates, newsletters, stakeholder communications | npx skills add anthropics/skills --skill internal-comms |
Strategy and Presentation Skills 🟡 Medium Priority
| Skill | Purpose | Installation command |
|---|---|---|
| competitor-teardown | Competitive analysis, SWOT, feature matrices, market research | npx skills add 1nference-sh/skills --skill competitor-teardown |
| pitch-deck-visuals | Investor presentations, fundraising, demo days, board meetings | npx skills add 1nference-sh/skills --skill pitch-deck-visuals |
Content and Marketing Skills 🟢 Low Priority
| Skill | Purpose | Installation command |
|---|---|---|
| product-changelog | Release notes, changelogs, feature announcements, versioning | npx skills add 1nference-sh/skills --skill product-changelog |
| case-study-writing | Customer success stories, technical portfolio, sales enablement | npx skills add 1nference-sh/skills --skill case-study-writing |
| technical-blog-writing | Technical blog posts, thought leadership, developer relations | npx skills add 1nference-sh/skills --skill technical-blog-writing |
Rule: Add Used Skills
Every time you use a new skill, add it to the "Current Skills" table.
Format:
| skill-name | What you use it for | `npx skills add owner/repo --skill name` |
Source
git clone https://github.com/javalenciacai/develop-skills/blob/main/.agents/skills/cto/SKILL.mdView on GitHub Overview
CTO acts as the main task orchestrator, analyzing user requests and routing them to the appropriate sub-organization (PM, QAL, TL, InfraLead, or DataLead). It serves as the entry point for all tasks and coordinates cross-domain work to prevent silos. The role emphasizes delegation rather than direct task execution.
How This Skill Works
The CTO receives user tasks, determines the domain (product, quality, development, infrastructure, or data/AI), and delegates to the corresponding sub-orchestrator. It then coordinates cross-domain efforts, consolidates progress reports, and replies to the user with status and outcomes. Direct task execution is intentionally avoided; the power rests in the delegated skills.
When to Use It
- User requests involve product strategy, roadmap, or UX design.
- Quality testing, security audits, or compliance activities are required.
- Development, architecture, or code implementation tasks are needed.
- Infrastructure, CI/CD, databases, or deployment tasks are involved.
- Data pipelines, analytics, AI/ML models, or LLM integration are required.
Quick Start
- Step 1: Receive the user task and classify the domain (product, quality, development, infrastructure, data/AI).
- Step 2: Delegate to the appropriate sub-orchestrator (PM, QAL, TL, InfraLead, or DataLead).
- Step 3: Monitor progress, consolidate reports, and respond with status and outcomes.
Best Practices
- Clearly identify the task domain before delegation.
- Delegate to the most relevant sub-orchestrator to accelerate delivery.
- Provide full context, constraints, and acceptance criteria in each handoff.
- Maintain visibility with consolidated progress reports and updates.
- Adhere to the rule that CTO does not execute tasks directly; focus on coordination.
Example Use Cases
- Collaborate with PM to define product roadmap while ensuring UX alignment.
- Coordinate a security audit with QAL during a release cycle.
- Route architecture decisions and coding efforts to TL with clear technical design.
- Lead InfraLead in a database migration and deployment workflow.
- Integrate a new data pipeline and ML model with DataLead, ensuring governance and analytics readiness.
Frequently Asked Questions
Add this skill to your agents
