Role Library

Roles are capabilities Athena can recruit into a workspace.

They are not all present in every workspace.

Strategic Roles

Strategic roles live at the company level and are available to Athena through the ELT.

• CTO.
• CPO / Product Strategy.
• CMO.
• Head of Sales / Revenue.
• CFO.
• COO.
• Legal / Risk Advisor.

Detailed cards: ELT Role Cards

Execution Roles

Execution roles live inside project workspaces when recruited.

Role	Use When
PM	Scope, milestones, task decomposition, acceptance criteria
Architect	System design, interfaces, technical tradeoffs
Developer	Code implementation and tests
QA	Verification, regression checks, evidence-backed failure reports
Researcher	Market, technical, customer, competitor, or source-backed research
Analyst	Signal synthesis, data interpretation, reporting
Writer	Docs, briefs, narratives, collateral
Designer	UX, visual systems, prototypes, artifacts
DevOps	Deployment, CI/CD, runtime configuration
Sales Enablement	Battlecards, objection handling, field-ready assets
Product Marketing	Positioning, messaging, launch and competitive framing
Customer/Voice Analyst	Reviews, interviews, community signals, first-party feedback

Detailed cards: Execution Role Cards

Routing rules: Athena Role Routing

Recruitment Rule

Athena should recruit only the roles needed for the current phase.

Examples:

• A one-page idea critique may need only Athena plus ELT review.
• A research brief may need Researcher plus Analyst.
• A software build may need PM, Architect, Developer, QA, and DevOps.
• A competitive intelligence cycle may need Collector, Analyst, Product Marketing, and Sales Enablement.
• A launch plan may need Product Strategy, CMO, Sales, Writer, and Designer.

Skill Rule

Each role should eventually have:

• Purpose.
• Inputs.
• Outputs.
• Boundaries.
• Required skills.
• Quality gates.
• Escalation trigger.

Do not write all role skills upfront. Build role skills when a real workspace needs them.