BACK_TO_COURSE
Roles, Models and Safety Rails
The Eleven Roles
Specialists With Declared Skills
Each role has one job and a declared set of knowledge skills:
| Role | Job |
|---|---|
product-strategist |
Brainstorming, research, briefs, PRDs |
architect |
System design, ADRs, tech stack |
ux-designer |
UX specs, wireframes, themes |
project-planner |
Epics, stories, backlog |
general-purpose |
Code implementation |
code-reviewer |
Code quality review (read-only) |
security-auditor |
Security review (writes only to its reviews folder) |
qa-engineer |
Test strategy and execution |
doc-writer |
Documentation and changelogs |
playwright |
Browser testing and automation |
shadow |
Voice-matched ghostwriting |
Specialize and Personalize
/review:specialize generates stack-specific guidance from your architecture doc. /review:personalize gives roles names and personalities. Both write into the parts of a role that updates preserve — identity, soul and Project Context — never into the generated projection.
INFO
Roles are read-only where they should be. The code reviewer and the security auditor diagnose; they do not rewrite your code. That is what lets you trust their output as an independent read.
QUIZ
Which role reviews code quality and is deliberately read-only?
Sign in to track lesson progress and earn a certificate.SIGN IN TO SAVE PROGRESS