$npx -y skills add vouchdev/vouch --skill vouch-followupPropose a dated followup the vouch digest will surface until closed
| 1 | # /vouch-followup |
| 2 | |
| 3 | File "$ARGUMENTS" as a `followup` page proposal — a commitment with a due |
| 4 | date that `vouch digest` lists until it's closed. Requires the company-brain |
| 5 | page kinds (`vouch init --template company-brain`). |
| 6 | |
| 7 | Steps: |
| 8 | |
| 9 | 1. Extract what's owed, by whom, and when. If no due date is stated, ask — |
| 10 | an undated followup never surfaces. |
| 11 | 2. Call `kb_propose_page` with `page_type: "followup"`, a short imperative |
| 12 | title, and `metadata`: `due_at` (ISO date), `followup_status: "open"`, |
| 13 | `owner` when known. Put context in the body; cite a source id if the |
| 14 | commitment came from a registered conversation or document. |
| 15 | 3. To close or move one later: re-propose the same page (`slug_hint: <page |
| 16 | id>`) with `followup_status: "done"` (or a new `due_at`) — status changes |
| 17 | go through the gate like any other edit. |
| 18 | 4. Report the proposal id and the due date filed. |
| 19 | |
| 20 | Never call `kb_approve`. |