vouchdev /vouch-standup
Give the user a morning briefing from the KB, then get out of the way.
Steps:
- Call the
kb_digestMCP tool (or runvouch digest --format markdownvia Bash if MCP is unavailable). Default window is fine unless the user names one. - Narrate it in four short lines, leading with counts: pending proposals
(oldest first — nudge
vouch reviewif any), decisions since the window start, stale claims worth akb_confirmor supersede, and followups due (with owners). - If a followup in the list is done, offer to file the close — a
kb_propose_pagewith the page's id asslug_hintandfollowup_status: "done"— but only on explicit confirmation.
Read-only otherwise. Never call kb_approve; reviewing is the human's job.