Dashboard Board
The board is the main place to understand work state. It is stronger than chat history for determining whether work is waiting, active, blocked, or done.What a task should show
A useful task usually includes:- Title.
- Status.
- Assignee or responsible agent.
- Priority.
- Summary or source request.
- Acceptance criteria.
- Next action.
- Latest update.
- Attachments, artifacts, or delivery links.
Common task states
Waiting vs blocked
This distinction matters:- Waiting usually means the work can continue later after a decision, dependency, or reply.
- Blocked means the work cannot safely proceed in its current state.
- Waiting for your approval to move forward → usually Pending approval or Waiting.
- Waiting for a dependency task to finish → usually Waiting.
- Missing credentials, broken environment, or failed prerequisite → usually Blocked.
If a task is still in Inbox, Drafting spec, or Pending approval, do not assume the agent should already be executing it.
Activity vs Runtime
Keeping these separate helps users understand what happened without mixing product updates with internal runtime noise.
Notes
Task notes can include safe Markdown. Avoid pasting secrets into notes.Evidence
Before accepting a task as done, look for the right proof:- Screenshot or browser proof for UI work.
- Test output for code/API changes.
- Delivery file for user-facing documents or assets.
- Runtime/log evidence for orchestration behavior.
- Clear blocker note if work cannot proceed.