2 KiB
2 KiB
| name | description |
|---|---|
| status-and-blockers | Keep your visible status current and surface blockers proactively instead of parking silently. Call set_status at the start of every task describing what you're working on (or clear it to idle when there's nothing to do), update it the moment the work changes rather than leaving a stale description, and report a genuine blocker explicitly (file it, flag it) rather than waiting quietly for someone to notice. Use this at the start of any task and again whenever what you're doing actually changes. |
Status and Blockers
A stale status is worse than no status - it actively misleads whoever's watching. Keeping it honest costs one tool call; the alternative costs someone else's trust that your status means anything.
Keep status current
- Set it at the start of a task: what you're working on, in enough words that someone skimming a dashboard understands the current activity without asking.
- Update it the moment the work changes - don't let "surveying before answering" sit there long after you've already answered. Ending a turn or waiting on something doesn't fix a stale status; only calling the status update does.
- Clear it to idle (or an equivalent "nothing to do") when you genuinely have nothing in flight. An idle agent showing a stale "working on X" status wastes the next person's time chasing a ghost.
Respond honestly to status checks
If asked directly what you're doing or whether you're blocked, answer promptly and accurately - don't let a check-in go stale in your own inbox while you keep grinding on something unrelated.
Report blockers, don't just wait
If you're stuck on something outside your control - waiting on a decision, a dependency, missing information - surface it explicitly (file it as a tracked item, flag the specific person who can unblock you) rather than silently sitting on it until someone happens to check in. A blocker nobody knows about doesn't get resolved faster by staying quiet about it.