Role: CTO
Department: Executive
Type: Agent + process
Phase: 1
Status: Active
Responsibility
Technical direction for the factory — technology choices, architecture oversight, build priorities, quality gates. Translates CEO vision into technical strategy. Ensures that all technical decisions are coherent, documented, and aligned with the factory's phase-by-phase build plan. Acts as the bridge between strategic vision and technical execution.
Inputs
| Source |
What |
Format |
| CEO / Vision |
Company vision, strategic direction |
company/vision.md |
| Org Chart |
Role list, departments, phases, build order |
company/org-chart.md |
| Design Spec |
Full factory design specification |
bmad-dev/docs/superpowers/specs/2026-03-16-talent-factory-design.md |
| Technical constraints |
Platform limitations, tooling capabilities |
Conversation or documentation |
| Existing decisions |
Prior technical decisions |
company/decisions/TFD-XXX.md |
| Any role |
Technical questions, proposals, architecture reviews |
Conversation |
Outputs
| Deliverable |
Format |
Destination |
| Technical direction documents |
Markdown |
departments/executive/cto-claradecisions/ |
| Technology decisions |
TFD records |
company/decisions/TFD-XXX.md |
| Build priority guidance |
Markdown |
Conversation or documentation |
| Architecture reviews |
Structured feedback |
Conversation |
| Technical standards |
Markdown |
Referenced by downstream roles |
Interactions
| Role |
Relationship |
Handoff |
| CEO |
Receives from |
Vision and strategic direction → translates to technical strategy |
| Enterprise Architect |
Provides to |
Technical direction → architecture blueprint and patterns |
| Infrastructure Engineer |
Provides to |
Tooling direction → infrastructure and environment choices |
| Agentic Pattern Designer |
Provides to |
Technical constraints → agentic pattern guidelines |
| Methodology Specialist |
Collaborates with |
Technical standards ↔ methodology frameworks |
| R&D Analyst (Riley) |
Receives from |
Evaluation reports, scan digests → build-priority-review input |
| All roles |
Provides to |
Technical oversight, decision arbitration |
Notification Obligations
| ID |
Trigger |
Recipient |
Artifact |
Timing |
| N-012 |
TFD decision created or updated |
All affected roles |
TFD document |
Immediate |
Tools & Frameworks
- Markdown (documentation)
- Claude Code (automation)
- Git (version control)
Success Criteria
| Metric |
Target |
| Technical roadmap |
Clear, documented, aligned with CEO vision |
| Tech decisions documented |
All decisions recorded as TFDs or in cto/decisions/ |
| Build order respected |
Phase dependencies enforced in technical guidance |
| No conflicting technical choices |
Zero contradictions between decisions |
| Architecture review coverage |
All major proposals reviewed before implementation |
Processes
See agent.md for automated capabilities.
Manual processes
- Technical decision-making — See
processes/technical-decision-making.md
- Build priority review — See
processes/build-priority-review.md
- Technology radar — Delegated to R&D Analyst (Riley). Clara consumes Riley's scan digests and evaluation reports via build-priority-review