- A task boundary for each box
workflows guide
Assign primary and support roles
Use role controls as behavior, not decoration.
- The primary role owns one clear result
- The support role stays secondary
- The effort level matches the risk of the task
Complete the task
Choose the role that owns the deliverable
Add one support role only when it improves that owner’s work
Write a task that names inputs, action, output, and completion criteria
Choose Light, Medium, or Heavy based on review depth
Use specialization to narrow expertise without replacing the primary role
Review the visible assignment before running
- Invisible behavior headers are not shown or exported
- A label cannot repair a vague or contradictory task