work-summary

Work Summary — Current (v3)

Attention-first project dashboard. The default (lean) mode answers four questions — what's moving, what's stuck, what's next, what's queued — in a bounded view (~45 lines) regardless of workspace size. The exhaustive inventory is available as an explicit mode, not the default: mature workspaces accumulate hundreds of terminal items, and rendering them all buries the actionable content.

Supplement the data with brief observations only when there is a genuine anomaly or actionable insight.

---

Step 0 — Mode Selection

$ARGUMENTS	Mode
empty	Lean (default)
the literal word full	Full Inventory
the literal word all	Multi-Project — one condensed section per known project root
anything else	Scoped — resolve to a UUID via query_items(operation="search", query=$ARGUMENTS, limit=5); prefer the best-matching root or container item; if ambiguous, present matches via AskUserQuestion

---

Step 0.5 — Project Scope Resolution

Before running Lean, Full, or Multi-Project mode, resolve the scope:

• Check session context from the SessionStart hook. A ## Project Scope section carries a project rootId, which scopes reads (ancestorId/anchorId) and anchors. A ## Personal Scope section carries a personal root, which only anchors new items: in personal scope every call below runs unscoped (whole database) and the header says personal scope — whole database.
• Otherwise, read .taskorchestrator/config.yaml's top-level project.rootId field (a file read, not an MCP call).
• If no rootId is found by either path, behavior is exactly as before this feature existed — every call below runs unscoped (whole-DB), and no ancestorId/anchorId param is passed. This is the common case for single-project workspaces.

When a project rootId is known, Lean and Full mode calls pass it as ancestorId="<rootId>" — except the overview calls, which use anchorId="<rootId>" (all noted inline below). Scoped mode is unaffected — it already resolves its own scope UUID per invocation via FTS.