sum-rundown

Reconcile saved task records with bounded Herdr observations and surface unresolved questions.

Updated Sep 5, 2026
One-click install
npx skills add https://github.com/douglasjarquin/sum --skill sum-rundown-douglasjarquin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sum-rundown
Source: https://github.com/douglasjarquin/sum/tree/main/skills/sum-rundown
Command: npx skills add https://github.com/douglasjarquin/sum --skill sum-rundown-douglasjarquin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating multiple worker agents across Herdr sessions makes it hard to know which tasks need decisions, which reports are ready, and which workers stalled, without polling each pane individually. ## Core Features & Use Cases - Bounded inbox reconciliation: Run ./bin/sumctl inbox --live to read every active task's state from one snapshot per Herdr session instead of sequential per-worker waits. - Pending returns tracking: Surface unanswered questions, unverified reports, unapplied answers, and cleanup states (pending, blocked, removing) in priority order. - Attention and recovery handling: Inspect native attention records, reconcile interrupted cleanups, record user answers with sumctl answer, and reclaim coordination after a restart with init --role coordinator --reclaim. - Use Case: After a night of delegated work, run a rundown to see which workers finished, which are blocked on decisions, answer their questions, and retry stalled notifications without launching duplicate workers. ## Quick Start Ask the coordinator to run a rundown of all active tasks and summarize what needs your decisions, reviews, or cleanup.

Frequently Asked Questions about sum-rundown

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check the status of all delegated agent tasks at once?

Run `./bin/sumctl inbox --live`, which takes one bounded agent list snapshot per Herdr session and reads every active task's state from it. Twelve workers cost one observation call instead of twelve sequential waits.

How do I answer a worker agent's question during coordination?

Record the answer with `./bin/sumctl answer TASK_ID QUESTION_ID --text 'The authorized answer'`. The answer stays visible until the worker marks it applied, and unanswered decisions surface first in the rundown.

Does the rundown monitor workers continuously in the background?

No, the rundown is not a background monitor or daemon. It reconciles missed events once from one snapshot per session and runs only when invoked, so it does not promise instant unattended detection.

Why does a task show cleanup pending or blocked?

A `cleanup: pending` row means the exact PR was observed merged but cleanup remains unfinished; offer `sumctl cleanup TASK_ID`. A `blocked` row names blocker codes that should be relayed, never cleared by force.

How do I recover coordination after the coordinator pane restarts?

Run `./bin/sumctl init` in the new pane; only after confirming the old coordinator is gone, use `init --role coordinator --reclaim`, which proceeds only when Herdr reports the old pane as `pane_not_found`. Then bind existing tasks with `sumctl bind TASK_ID --parent-only`.

What are the limitations of the sum rundown approach?

It reads saved records and Herdr only, never GitHub, so CI rows reflect the last observation rather than the current state. It has no automatic retry, process fencing, or merge polling, and idle workers are not assumed done without inspection.