Writing a Role
A Role is a responsibility, not a task. Write it like the first two lines of a job description.
Say what it owns, for whom, and to what standard. One or two sentences, true for months.
| Reads like a Role | Reads like a Project |
|---|---|
| You keep our competitive landscape current and flag any pricing change within a day. | Write a report on competitor pricing. |
| You own the weekly newsletter: draft Thursday, sourced, in our tone, ready for my edit. | Draft this week’s newsletter. |
| You maintain our internal tools’ Rust codebase, tests green, dependencies pinned. | Fix the failing build. |
One responsibility per Teammate: two Roles in one Teammate means two Teammates stepping on each other’s files, with one Brain.
Revisit a Role when you keep repeating the same instruction in briefs. Put it in the Role and stop repeating it.