Field report from 2026-08-28 (Allen + the uber-TL session): on a multi-agent day the worklog Stop hook fired ten times — once per opened PR — each interrupting a live conversation to make a marginal edit to the same session note. Outcome per Allen: the long-form session notes are read by nobody (human or agent); the artifact that IS read is the one-line-per-project bullet in the daily note. Per-event firing turns a synthesis ritual into a notification stream, and dilutes exactly the why/dead-ends value the note exists for.
Changes wanted in the journal plugin:
-
Retire the per-PR Stop/arm hook pattern as the default. Replace with a daily sweep mode: one scheduled run (local — needs vault access) that gathers the day's merged PRs across all configured repos and writes/rewrites ONLY the daily-note bullets (one per project, rewrite-in-place, per the skill's existing rules). No session notes. (Allen's interim: hooks removed from settings; a LaunchAgent running headless Claude with a sweep prompt at 17:53 daily.)
-
Guidance-steered /worklog: accept a free-text directive as the argument, e.g. /worklog Outage caused by doppler drift, summarize work there and next steps — a focused session-note capture steered by the statement (what to emphasize, which project, what next-steps to record), instead of the full-day narrative. This is the opt-in path for days when session context is worth keeping.
-
Keep the three-artifact structure available but make the session note opt-in rather than hook-driven.
Design principle worth recording in the skill: the digest is the product; per-event firing kills synthesis value. (Independently confirmed by the foreman design's morning-digest/escalation-batching principle, Vycari/foreman docs/design/factory.md.)
🤖 Filed via Claude Code
Field report from 2026-08-28 (Allen + the uber-TL session): on a multi-agent day the worklog Stop hook fired ten times — once per opened PR — each interrupting a live conversation to make a marginal edit to the same session note. Outcome per Allen: the long-form session notes are read by nobody (human or agent); the artifact that IS read is the one-line-per-project bullet in the daily note. Per-event firing turns a synthesis ritual into a notification stream, and dilutes exactly the why/dead-ends value the note exists for.
Changes wanted in the journal plugin:
Retire the per-PR Stop/arm hook pattern as the default. Replace with a daily sweep mode: one scheduled run (local — needs vault access) that gathers the day's merged PRs across all configured repos and writes/rewrites ONLY the daily-note bullets (one per project, rewrite-in-place, per the skill's existing rules). No session notes. (Allen's interim: hooks removed from settings; a LaunchAgent running headless Claude with a sweep prompt at 17:53 daily.)
Guidance-steered /worklog: accept a free-text directive as the argument, e.g.
/worklog Outage caused by doppler drift, summarize work there and next steps— a focused session-note capture steered by the statement (what to emphasize, which project, what next-steps to record), instead of the full-day narrative. This is the opt-in path for days when session context is worth keeping.Keep the three-artifact structure available but make the session note opt-in rather than hook-driven.
Design principle worth recording in the skill: the digest is the product; per-event firing kills synthesis value. (Independently confirmed by the foreman design's morning-digest/escalation-batching principle, Vycari/foreman docs/design/factory.md.)
🤖 Filed via Claude Code