Skip to content

Personas Cheatsheet

Quick reference for all SNIPER persona layers. Personas are composed in three layers -- process + technical + cognitive -- to create specialized agent identities.

Process Layer

Process personas define the agent's role and methodology.

analyst

Business analyst who researches markets, competitors, and user needs.

Teamsdiscover (analyst, risk-researcher, user-researcher)
PhasesDiscover
ReferenceFull persona reference

architect

System architect who designs technical architecture and component boundaries.

Teamsplan (architect, security-analyst) · feature-plan (feature-architect)
PhasesPlan · Feature
ReferenceFull persona reference

architecture-cartographer

Reverse-engineers system architecture from existing code.

Teamsingest
PhasesIngest
ReferenceFull persona reference

code-archaeologist

Reverse-engineers project purpose and scope from source code.

Teamsingest
PhasesIngest
ReferenceFull persona reference

code-investigator

Traces code execution paths and identifies failure points.

Teamsdebug
PhasesDebug
ReferenceFull persona reference

code-reviewer

Senior developer conducting thorough code review.

Teamsreview-pr (code-reviewer, security-reviewer) · review-release (breaking-change-analyst)
PhasesPR Review · Release Review
ReferenceFull persona reference

contract-designer

Designs cross-repo interface contracts (API, types, events).

Teamsworkspace-feature
PhasesWorkspace
ReferenceFull persona reference

convention-miner

Extracts coding patterns and conventions from codebases.

Teamsingest
PhasesIngest
ReferenceFull persona reference

coverage-analyst

Identifies risk-weighted test coverage gaps.

Teamstest
PhasesTest Audit
ReferenceFull persona reference

developer

Implements stories with production-quality code and tests.

Teamssprint (backend-dev, frontend-dev, infra-dev, ai-dev)
PhasesSprint
ReferenceFull persona reference

doc-analyst

Scans project structure to produce a documentation index.

Teamsdoc
PhasesDocumentation
ReferenceFull persona reference

doc-reviewer

Validates documentation for accuracy and completeness.

Teamsdoc
PhasesDocumentation
ReferenceFull persona reference

doc-writer

Generates clear project documentation from artifacts and code.

Teamsdoc · review-release (doc-reviewer member)
PhasesDocumentation · Release Review
ReferenceFull persona reference

flake-hunter

Diagnoses and fixes intermittent test failures.

Teamstest
PhasesTest Audit
ReferenceFull persona reference

impact-analyst

Assesses blast radius of proposed code changes.

TeamsRefactor (single-agent phase)
PhasesRefactor Audit
ReferenceFull persona reference

integration-validator

Validates repo implementations match interface contracts.

Teamsworkspace-validation
PhasesWorkspace
ReferenceFull persona reference

log-analyst

Finds signal in error logs, traces, and observability data.

Teamsdebug
PhasesDebug
ReferenceFull persona reference

migration-architect

Designs safe, incremental migration paths for large changes.

TeamsRefactor (single-agent phase)
PhasesRefactor Audit
ReferenceFull persona reference

perf-profiler

Identifies bottlenecks through systematic code analysis.

TeamsPerformance (single-agent phase)
PhasesPerformance Audit
ReferenceFull persona reference

product-manager

Synthesizes discovery artifacts into a product requirements document.

Teamsplan · feature-plan
PhasesPlan · Feature
ReferenceFull persona reference

qa-engineer

Validates implementations through comprehensive testing.

Teamssprint · review-pr (test-reviewer)
PhasesSprint · PR Review
ReferenceFull persona reference

release-manager

Assesses release readiness and produces changelogs.

Teamsreview-release
PhasesRelease Review
ReferenceFull persona reference

retro-analyst

Post-sprint analysis to extract learnings and update memory.

Teamsretro
PhasesRetrospective
ReferenceFull persona reference

scrum-master

Breaks requirements into epics and self-contained stories.

TeamsSolve (single-agent phase)
PhasesSolve
ReferenceFull persona reference

threat-modeler

Maps attack surfaces using STRIDE methodology.

Teamssecurity
PhasesSecurity Audit
ReferenceFull persona reference

triage-lead

Rapidly assesses production incidents.

TeamsReferenced by debug (not a team member)
PhasesDebug
ReferenceFull persona reference

ux-designer

Translates requirements into UX specification with information architecture and user flows.

Teamsplan
PhasesPlan
ReferenceFull persona reference

vuln-scanner

Finds application-level vulnerabilities via code review.

Teamssecurity
PhasesSecurity Audit
ReferenceFull persona reference

workspace-orchestrator

Coordinates features spanning multiple repositories.

Teamsworkspace-feature
PhasesWorkspace
ReferenceFull persona reference

Technical Layer

Technical personas add domain-specific expertise. Applied as the second layer in composition.

api-design

RESTful and real-time API design -- OpenAPI, GraphQL, WebSocket contracts.

Teamsplan (product-manager) · workspace-feature (contract-designer)
ReferenceFull persona reference

ai-ml

LLM integration, speech-to-text, NLP, vector databases, ML serving.

Teamssprint (ai-dev)
ReferenceFull persona reference

backend

Node.js/TypeScript backend -- Express/Fastify, PostgreSQL, Redis, queues.

Teamsplan (architect) · sprint (backend-dev, qa-engineer) · ingest (architecture-cartographer) · feature-plan (feature-architect) · debug (code-investigator) · workspace-validation (validator) · refactor (migration) · perf (profiling)
ReferenceFull persona reference

database

Relational/non-relational design -- PostgreSQL, ORM, query optimization.

TeamsAvailable for composition (not assigned to a default team)
ReferenceFull persona reference

frontend

React/TypeScript -- Next.js/Vite, TanStack Query, Tailwind.

Teamsplan (ux-designer) · sprint (frontend-dev)
ReferenceFull persona reference

infrastructure

AWS, Docker, CI/CD, Terraform, Kubernetes, monitoring.

Teamsdiscover (risk-researcher) · sprint (infra-dev)
ReferenceFull persona reference

security

OWASP, OAuth/OIDC, encryption, RBAC, API security, compliance.

Teamsplan (security-analyst) · security (threat-modeler, vuln-scanner)
ReferenceFull persona reference

Cognitive Layer

Cognitive personas define the agent's thinking style and decision framework. Applied as the third layer.

devils-advocate

Challenges assumptions, stress-tests designs, finds failure modes.

Teamsdiscover (risk-researcher) · sprint (qa-engineer) · debug (log-analyst) · doc (doc-reviewer) · review-pr (code-reviewer) · review-release (breaking-change-analyst) · test (flake-hunter) · security (vuln-scanner) · workspace-validation (validator) · refactor (impact analysis)
ReferenceFull persona reference

mentor-explainer

Documents decisions so future readers understand the "why".

Teamsdoc (doc-writer)
ReferenceFull persona reference

performance-focused

Evaluates latency budgets, throughput, memory, scalability.

Teamssprint (ai-dev)
ReferenceFull persona reference

security-first

Evaluates every decision through a security lens first.

Teamsplan (architect, security-analyst) · review-pr (security-reviewer)
ReferenceFull persona reference

systems-thinker

Thinks in boundaries, interfaces, dependencies, and emergent behaviors.

Teamsdiscover (analyst) · plan (product-manager) · sprint (backend-dev, infra-dev) · ingest (all 3 members) · feature-plan (both members) · debug (code-investigator) · review-pr (test-reviewer) · review-release (release-manager) · test (coverage-analyst) · security (threat-modeler) · retro · workspace-feature (both members) · solve · refactor (migration) · perf
ReferenceFull persona reference

user-empathetic

Thinks from the user's perspective -- what they see, feel, need.

Teamsdiscover (user-researcher) · plan (ux-designer) · sprint (frontend-dev) · doc (doc-analyst) · review-release (doc-reviewer)
ReferenceFull persona reference

Composition Examples

Real compositions from team YAML files showing how the three layers combine.

Backend Architect (plan team)
  • Process: architect
  • Technical: backend
  • Cognitive: security-first
  • Result: Security-conscious backend architect who evaluates every design through a security lens. Produces docs/architecture.md.
  • Team: plan (architect member)
Risk Researcher (discover team)
  • Process: analyst
  • Technical: infrastructure
  • Cognitive: devils-advocate
  • Result: Infrastructure-aware analyst who challenges optimistic assumptions and finds failure modes. Produces docs/risks.md.
  • Team: discover (risk-researcher member)
AI Developer (sprint team)
Doc Writer (doc team)
  • Process: doc-writer
  • Technical: from-config (matches project stack)
  • Cognitive: mentor-explainer
  • Result: Documentation writer who explains decisions for future readers, with stack-specific technical knowledge.
  • Team: doc (doc-writer member)
Vulnerability Scanner (security audit team)
  • Process: vuln-scanner
  • Technical: security
  • Cognitive: devils-advocate
  • Result: Security researcher who challenges every assumption and hunts for non-obvious vulnerabilities. Produces vulnerability-report.md.
  • Team: security (vuln-scanner member)