Skip to main content

/status

A read-only snapshot of the developer's open work. No mutations.

Steps​

  1. ClickUp, through the MCP. ClickUp has no CLI, so this part stays with you. Fetch the developer's open tasks (clickup_filter_tasks scoped to the actor, open statuses) and write them to a temp file as a JSON array of { id, customId, name, status, priority, dueDate, url, blocked }. Raw MCP shapes are fine: status and priority may be objects, dueDate may be epoch ms. Set blocked: true when the task has an unresolved blocking dependency. If the MCP is unavailable, skip this step and pass --no-clickup.

  2. Run the script and follow its instructions.

    S="${CLAUDE_PLUGIN_ROOT}/scripts/work-status.mjs"; [ -f "$S" ] || S="scripts/work-status.mjs"
    node "$S" --clickup /tmp/status-clickup.json # or --no-clickup
    node "$S" --clickup /tmp/status-clickup.json --json

    The script (scripts/work-status.mjs) fetches the GitHub side itself with gh: my open PRs (CI, mergeability, human approvals, unresolved threads), PRs requesting my review, open issues assigned to me, and team PRs nobody has reviewed. It links ClickUp tasks to PRs and issues by CU-id so one work item is one row, groups everything into Needs me, Blocked, In progress, Drift, verify and Queued, and ends with == INSTRUCTIONS FOR THE AGENT (follow in order) ==. Present the groups as printed and follow the block. Do not re-bucket by hand. Defaults to the bewith-dev org, --org <org> or --all-orgs to change it. Exit codes: 0 nothing needs the developer, 3 something needs action or is waiting, 1 error.

  3. Check drift against content (judgement). The script flags drift it can see mechanically: an in-progress or finished status with no open PR carrying the CU-id. It cannot read linked decisions or task descriptions. For the items it lists, read the task content and linked decisions before suggesting anything. When a tag contradicts the content (tagged deployed but a linked decision defers it), report it as drift, verify, never as a directive like "run /done".

Boundaries​

  • Read-only. Never change a task status, merge, push, or nudge a reviewer. The script's instructions say "ask the developer" for those. To act on an item, the developer runs the matching command (/continue, /address-review, /pr-review, /done).
  • If ClickUp or GitHub is unreachable, report what was reachable and name what was skipped. Never fabricate a list.
  • For a ranked "what next" use /next-task.