ops-desk

# OPS ► DESK SWEEP Load `ops-rules` before acting. Public repo (no personal data). Outbound: one draft → one approval → one send. If `AskUserQuestion` / `Workflow` are missing, follow Rule 10 in `ops-rules` (Hermes: numbered options / two-turn Telegram card; `delegate_task`). Goal: everything sitting on the owner's desk — pending decisions, staged drafts awaiting approval, unpaid invoices to chase, documents to sign, blocked issues needing an owner action — becomes a **ranked queue of ready-to-approve action packages**, then gets worked down one item at a time. The success metric is the same spirit as inbox-zero: **an empty desk**, with every remaining item either executed, decided, or parked with an explicit reason and a reminder. ## When to use ops-desk vs ops-inbox - `/ops:ops-inbox` — fresh inbound comms (who wrote me, what needs a reply). - `/ops:ops-desk` — the standing backlog (what am I blocking, what decision is waiting on me, what draft is staged, what must I sign/pay/approve). Run it after an inbox pass, or whenever the owner says "what's left / get this off my desk". ## Step 1 — Build the item list (unless passed explicitly in ``) 1. **Task tracker (SSOT).** Whichever the box uses, in order of preference: - **Paperclip** — `paperclip issue list -C <company-id>` for each company in `${CLAUDE_PLUGIN_DATA_DIR}/preferences.json → paperclip.companies[]`, falling back to `paperclip company list`. Keep `status=blocked|todo|in_progress` issues whose...