See Every Active Plan - alexherrero/crickets GitHub Wiki
Note
Goal: List every active task of a project โ each one's name, its status from its tracker, and the most-recent line of its progress log โ in one read-only dashboard, so a coordinator can see the queue before deciding what to /work next.
Prereqs: the development-lifecycle plugin installed (Install crickets plugins); agentm installed, since it keeps the project's plans; at least one task in the project (see Named plans).
Use /queue-status-lite when several tasks are in flight at once and you want a single view of all of them. It is the read side of the multi-plan surface: the --name writers (Run a named plan) drive one task; this glance shows them all. It only reads: it shows you the queue and leaves every decision โ what to work, review, or merge โ to you.
-
Run the glance from the project's repo. Invoke
/queue-status-lite. It takes no arguments: agentm resolves the project from the working directory./queue-status-lite -
Read the dashboard. One entry per active task โ its name (
042-build-the-brief), its status from its tracker, and the last line of its progress log. Tasks whose tracker saysdoneordroppedare left out. In a repo with no vault, the rows are its repo-local plans, which agentm keeps in.harness/. The output is agentm's reader's render, passed through verbatim (see Named plans ยง Reading the queue). -
Decide, then act. The glance stops at showing. Choose the next move yourself โ
/work --name <task>to work a task,/review --name <task>to review one, or nothing at all.
- Running
/queue-status-liteprints one block, one entry per active task, and exits0. - No file changes: the working tree is identical before and after (
git statusshows nothing new) โ the command mutates no state.
-
No plan list: โฆ. No agentm checkout was found. development-lifecycle keeps its plans through agentm, so there is no queue to show; install agentm, or set$AGENTM_SCRIPTS_DIRto itsscripts/. -
A task is missing from the list. Check its tracker: a
doneordroppedtask is intentionally left out. A task directory needs aplan.mdto be listed.
- Named plans โ the lookup: the command's arguments and the read bridge's contract.
-
Run a named plan โ the write-side recipe: driving
/work --name <task>and friends against one task. - Open a project by name โ one project's brief and tasks, each with its tracker status.
- Development Lifecycle โ the phase-loop plugin this command belongs to.
- Why phase-gating โ why state lives on disk.