celesteops-reviewlisted

# CelesteOps Review Use this skill when CelesteOps is the source of truth for review state. The goal is to help the user understand what is waiting in CelesteOps, what each item is asking for, and what should happen next. ## Quick start 1. Confirm the session exposes CelesteOps MCP tools. Tool names may be namespaced; match by suffixes such as `documents_pending_review`, `documents_pending_decisions`, `document_get`, `document_set_review_status`, `document_decision_resolve`, `documents_search`, `documents_for_entity`, `document_backlinks`, `tasks_search`, `tasks_list`, `projects_list`, and `pipeline_list`. 2. If CelesteOps tools are not available, inspect `../../README.md` for the MCP connection shape and tell the user the skill cannot operate the review queue until the MCP is attached. Do not mutate SQLite directly as a substitute. 3. For document review, start with `documents_pending_review` **and** `documents_pending_decisions` — a doc can wait on a user choice (an agent-authored decision) without being in the review-status queue. 4. For repo-scoped review, also call `projects_list` and then the relevant task or document search tools. 5. For content-pipeline review rather than document approval, start with `pipeline_list`. ## Review rules - Read the full document with `document_get` before recommending approval or modification. `document_get` returns `{document, comments, decisions}` — read the embedded reasoning chain (agent comments + any open/resolved decisions) so