Your Role, Your Path

Find your role in 10 seconds. ADLC solves different problems for each persona — cost for finance, governance for security, speed for architecture, delivery for operations. Pick yours below.

How to use this page

Each tab shows the commands and workflows your role depends on. Start with the linked quickstart guide for your persona.

CFO / Finance

Cost dashboards, monthly FinOps reports, persona-based analysis.

Key commands: /finops:aws-monthly, /finops:azure-monthly, /finops:analyze

Get started with FinOps

CTO / Architecture

IaC governance, multi-cloud deployment, architecture decisions.

Key commands: /terraform:test, /cdk:test, /speckit.plan

Get started with workflows

CloudOps Engineer

Inventory, cross-validation, incident triage, DORA metrics.

Key commands: /inventory:lz-cross-validate, /aws:incident-triage, /metrics:update-dora

Get started with commands

Security / Compliance

SAST scanning, cert inventory, SOC2 automation, posture assessment.

Key commands: /security:sast, /security:cert-inventory, /aws:security-posture

Get started with enterprise deployment

All roles benefit from ADLC Workflow coordination

All roles benefit from the ADLC Workflow coordination pattern — the mandatory product-owner + cloud-architect gate applies to every persona.

---

Additional Personas

Product Manager

Sprint planning, user stories, JIRA sync, Confluence templates, roadmaps.

Key commands: /product:sprint, /product:write-stories, /metrics:sync-jira, /product:pr-faq

Get started with product management

Platform Engineer

Terraform modules, CDK stacks, K8s clusters, DevContainer profiles.

Key commands: /terraform:test, /cdk:test, /devcontainer:validate-registry

Get started with workflows

---

MCP profiles

A profile is a least-privilege boundary, not a job title. It answers "how little access does this session need?", which is a different question from "who am I?". Any role can use any profile; pick the smallest one that still lets you finish the task.

There are 4 profiles, generated from .claude/mcps/.mcp-enterprise.json (27 servers) and never hand-edited:

Profile	Servers	Included
executive	6	aws-knowledge, awslabs-billing-cost-management, azure, brave-search, context7, vizro-analytics
minimal	1	context7
reviewer	10	aws-knowledge, awslabs-api, awslabs-billing-cost-management, awslabs-cloudformation, awslabs-cloudtrail, awslabs-cloudwatch, awslabs-ecs, awslabs-iam, awslabs-network, context7
security-engineer	4	awslabs-cloudtrail, awslabs-iam, azure, context7

Start a session with one, without changing any file on disk:

claude --mcp-config .claude/mcps/profiles/executive.json --strict-mcp-config

--strict-mcp-config is what makes the boundary real: it ignores every other MCP source, so the session gets exactly the servers listed above and nothing else.

Never copy a profile over .mcp.json

Each project's .mcp.json is a generated artifact of .claude/mcps/scripts/derive-mcp-profile.py. Overwriting it drops the servers that project needs, and the next task mcp:profile:regenerate silently reverts your change. Use --mcp-config instead — it is per-session and touches nothing.

Which profile suits which role is a starting point, not a rule:

If you are…	Start with	Because
Finance / FinOps	executive	AWS and Azure cost, plus Vizro for charts
Security / compliance	security-engineer	CloudTrail and IAM, no write-capable tooling
Architecture / review	reviewer	The read-only AWS surface needed to assess a design
Anything else	minimal	Documentation lookup only — widen when you hit a wall

Full server-by-server detail, including which product gets which server: MCP Servers reference.

See Installation for first-time setup.