Skip to Content
NodesRoles

Roles

A role is the identity a node carries. It shapes what the agent considers its domain, which skills it reaches for first, and how it communicates with peers.

Built-in role library

Direktor ships with a catalog of roles across several categories:

Executive Office

RoleTypical responsibilities
CEOVision, strategy, fundraising, stakeholder management
CTOTechnical architecture, platform decisions, team building
CFOFinance planning, budget, runway, reporting
COOOperations, processes, scaling, cross-functional coordination
CMOBrand, go-to-market, demand gen, positioning
CPOProduct vision, roadmap, research, product-market fit
CISOSecurity strategy, risk management, compliance, incident response

Engineering

RoleTypical responsibilities
Software ArchitectHigh-level design, patterns, technical vision
Backend ArchitectAPIs, databases, distributed systems
Frontend DeveloperUI, accessibility, responsive design
DevOps AutomatorCI/CD, Docker, Kubernetes, monitoring
Security EngineerHardening, pentesting, OWASP, threat modeling
Code ReviewerReview patterns, correctness, performance

Sales & Marketing

RoleTypical responsibilities
VP SalesRevenue targets, team performance, forecasting
Account StrategistAccount planning, expansion revenue, QBRs
Discovery CoachDiscovery calls, needs analysis, pain identification
Deal StrategistDeal qualification, negotiation, pricing
Content CreatorBlog posts, social content, editorial calendar
SEO SpecialistTechnical SEO, keyword research, content optimization

Design

RoleTypical responsibilities
UI DesignerVisual design, component libraries, design tokens
UX ResearcherUser interviews, usability testing, personas
UX ArchitectInformation architecture, user flows, wireframes
Brand GuardianBrand consistency, style guides, tone of voice

Personal / Household

RoleTypical responsibilities
Personal AssistantScheduling, inbox triage, life admin
Finance CoachBudgets, bills, goals, financial planning
Job SeekerFull job-search pipeline (see find-job)
Insurance ShopperQuote comparison (see insurance-quote)

Custom roles

Direktor doesn’t restrict you to the built-in list. When you add a node, type any role name — the agent adopts it and uses the label as part of its identity. The default skill library is always available regardless of role.

How a role shapes the agent

The role is combined with the workspace context, any starting context you provided, and the available skills to form the agent’s system prompt. It doesn’t change which APIs the agent has access to — just how the agent prioritizes, phrases, and decides.

Two nodes with the same role can behave very differently if you give them different starting contexts. Two nodes with different roles often behave identically for generic tasks — the role pulls weight on ambiguous or role-specific decisions.

Next

Last updated on