vouch-standup

スター156

フォーク60

更新日2026年7月4日 04:17

Narrate the vouch digest — pending reviews, decisions, stale claims, due followups

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

vouchdev

vouchdev/vouch

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

/vouch-standup

Give the user a morning briefing from the KB, then get out of the way.

Steps:

Call the kb_digest MCP tool (or run vouch digest --format markdown via 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 review if any), decisions since the window start, stale claims worth a kb_confirm or supersede, and followups due (with owners).
If a followup in the list is done, offer to file the close — a kb_propose_page with the page's id as slug_hint and followup_status: "done" — but only on explicit confirmation.

Read-only otherwise. Never call kb_approve; reviewing is the human's job.

このリポジトリの他の Skills

同じリポジトリ

vouch-ask

vouchdev/vouch

Answer a question from the vouch KB with citations, or say what's missing

2026-07-04156

vouch-followup

vouchdev/vouch

Propose a dated followup the vouch digest will surface until closed

2026-07-04156

vouch-record

vouchdev/vouch

Propose a typed record (contact, org, project) into the vouch KB

2026-07-04156

vouch-remember

vouchdev/vouch

File something the user wants remembered as a cited, review-gated proposal

2026-07-04156

vouch-propose-from-pr

vouchdev/vouch

Distill a merged PR into vouch claim proposals

2026-07-02156

vouch-recall

vouchdev/vouch

Recall what the project's vouch KB knows about a topic

2026-07-02156

name	vouch-standup
description	Narrate the vouch digest — pending reviews, decisions, stale claims, due followups

/vouch-standup

Give the user a morning briefing from the KB, then get out of the way.

Steps:

Call the kb_digest MCP tool (or run vouch digest --format markdown via 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 review if any), decisions since the window start, stale claims worth a kb_confirm or supersede, and followups due (with owners).
If a followup in the list is done, offer to file the close — a kb_propose_page with the page's id as slug_hint and followup_status: "done" — but only on explicit confirmation.

Read-only otherwise. Never call kb_approve; reviewing is the human's job.