loop-briefing

loop-briefing

Self-Evolving Skill: This skill improves through use. If instructions are wrong, parameters drifted, or a workaround was needed — fix this file immediately, don't defer. Only update for real, reproducible issues.

The original goal skill: a contextually-invoked briefing for autonomous /loop runs. Built on the TS core pushover_core.ts loop-brief, which gathers context (project, cwd, branch, git status, recent commits, plus any details you pass), renders it (Satori → PNG), and sends it (emergency+receipt for blocked, high-priority for done).

# BLOCKED — needs a decision now (emergency, alarms until you ack):
env -u HTTPS_PROXY -u HTTP_PROXY bun "${CLAUDE_PLUGIN_ROOT}/skills/_lib/pushover_core.ts" loop-brief \
  --kind blocked --reason "must choose auth method" --body /tmp/decision_options.txt

# DONE — no meaningful work remains (high priority, no alarm):
env -u HTTPS_PROXY -u HTTP_PROXY bun "${CLAUDE_PLUGIN_ROOT}/skills/_lib/pushover_core.ts" loop-brief \
  --kind done --reason "all tasks complete, matrix exhausted"

When to fire (the two-situation rule)

1. Blocked — the loop cannot safely continue without a human: needs a decision, clarification, review, or a choice between options. Pair this with an AskUserQuestion call in the session so the options are presented in plain language with tradeoffs.
2. Done — no meaningful remaining work under the initial or updated directives; the loop should stop scheduling further wakeups (CronDelete).

Do not fire for routine progress. The --body - form reads details from stdin.

Post-Execution Reflection

After this skill completes, check before closing:

1. Did the block/done briefing fire at the right moment with the right git and session context? If it fired on routine progress or missed a real block, fix the trigger.
2. Was the emergency vs high-priority routing correct? Blocked = emergency+receipt, done = high-priority — fix if swapped.

Only update if the issue is real and reproducible — not speculative.