Responsibilities
Responsibilities keep work bounded. A responsibility describes what needs to be handled, not status.
The same person can carry different responsibilities at different times. The list is useful because it defines what kind of judgment is needed and what kind of review should happen before a change is finished.
| Responsibility | Purpose |
|---|---|
| Planner | Shapes scope, acceptance criteria, dependencies, and work order. |
| Researcher | Gathers evidence and pattern comparisons. |
| Builder | Makes bounded code, content, or docs changes after scope is clear. |
| Reviewer | Looks for risk, regressions, missing tests, and weak assumptions. |
| Verifier | Checks commands, routes, screenshots, and acceptance criteria. |
| Writer | Turns approved material into clear public prose. |
| Publisher | Confirms the reviewed version is the one that should go live. |
| Operations steward | Handles runbooks, service checks, and safety gates. |
Boundaries
Clear responsibilities prevent two common failures: everything becoming vague, or every task moving forward before it is shaped enough to review.
Good assignments include:
- the material to use
- the output expected
- what is out of scope
- how the result should be checked
- where follow-up should be left