check-taskslisted

Read-only task lister that always projects `fields=lite` with a default `limit=20`, renders a compact priority-ordered table, and (on explicit user request) chains to `dispatch-task-start` on the highest-priority unblocked todo. **Canonical source**: VantageRegistry (`get_skill_content name=check-tasks`). The local `.claude/skills/check-tasks/SKILL.md` in each workspace MUST be a byte-exact mirror of the VR canonical content. End of hand-copy — fetch from VR, do not edit locally. V2 PRINCIPLE — ENVELOPE-FRIENDLY BY DEFAULT: Day 89 introduced `capListResponseBytes` (60 KB) on bulk list tools. Calling `list_tasks` without a projection or limit will silently truncate or trip the envelope. This skill pins `fields=lite` and `limit=20` on every call, so the response always fits. Drill-down on a specific task uses `get_task` (single-row, no cap risk), not a bigger list. V2 PRINCIPLE — READ-ONLY UNLESS ASKED: this skill READS and DISPLAYS tasks only. It does NOT call `start_task`, `complete_task`, or `update_task`. The auto-pick chain only fires when the user explicitly says "pick next", "start next", "auto-pick", or "take the next one" — and even then it delegates to the `dispatch-task-start` skill, which owns the IRP / evidence-bound writes. ## WORKFLOW **Step 1 — Detect orchestrator role + instance** 1. Read the first 20 lines of `CLAUDE.md` in the current workspace. 2. Extract role (e.g., `pi`, `sigma`, `eta`, `alpha`, `lambda`, `tau`, `phi`, `omega`, `zeta`) from the heade