feat(workflows): promote meeting-prep to a general template

Meeting-prep was project-only. I generalized its project-specific references (transcript-home path, issue tracker, knowledge file, worked-example doc) to neutral terms and moved it into claude-templates so any project's .ai/ picks it up. The pre-wire supporting doc travels beside it as meeting-prep.pre-wire.org.

I added the workflow entry and trigger phrases to INDEX.org. I flipped daily-prep's two conditional meeting-prep references, and its trailing changelog claim, to direct links now that the workflow ships as a template.

1 files changed, 3 insertions, 3 deletions

diff --git a/.ai/workflows/daily-prep.org b/.ai/workflows/daily-prep.org
index fcc983d..327e519 100644
--- a/.ai/workflows/daily-prep.org
+++ b/.ai/workflows/daily-prep.org
@@ -194,11 +194,11 @@ Capture the meeting list with what's known about each (time, owner, official age
 
 Beyond today, scan the next 5 days from the Phase A forward window — read the calendar today *and the next five days*, reading it rather than glancing. For each meeting in that window, do a quick read (who's invited and who accepted, why it's being held, the timing, the objective) and surface three buckets at the final review:
 
-1. *Meetings that need prep.* A substantive upcoming meeting — an external partner, a negotiation, a review of specific work or data, a first call with someone — that has no =working/<slug>-call-prep/= doc yet. Offer to run the meeting-prep workflow where the project has one, or add a prep task. Some meetings take more than five minutes to prepare; catching them several days out is the whole point of looking ahead.
+1. *Meetings that need prep.* A substantive upcoming meeting — an external partner, a negotiation, a review of specific work or data, a first call with someone — that has no =working/<slug>-call-prep/= doc yet. Offer to run the [[file:meeting-prep.org][meeting-prep workflow]], or add a prep task. Some meetings take more than five minutes to prepare; catching them several days out is the whole point of looking ahead.
 2. *Traps.* A time-zone mismatch on a travel day, a double-booking, a talk-heavy meeting that will overrun into the next, a recurring meeting that isn't needed this cycle.
 3. *Focus blocks to protect.* Open mornings or afternoons in the window worth blocking now for big work, before they get booked over.
 
-This is a scan-and-flag pass, not a full prep — the deep prep for any one meeting is the meeting-prep workflow's job where one exists. Keep it to the three buckets and surface them in =* Heads-up= (Phase 7) or as forward tasks / Anchor Tasks; don't add a new prep-doc section.
+This is a scan-and-flag pass, not a full prep — the deep prep for any one meeting is the [[file:meeting-prep.org][meeting-prep workflow]]'s job. Keep it to the three buckets and surface them in =* Heads-up= (Phase 7) or as forward tasks / Anchor Tasks; don't add a new prep-doc section.
 
 ** Phase 2: Planned vs. Actual Review
 
@@ -612,4 +612,4 @@ Phase 3's inline source scans — sub-steps 3b (email), 3c (mark-read), 3d (Slac
 Craig's call. The prep doc is now *born* in =daily-prep/YYYY-MM-DD-daily-prep.org= and never moves; the dated files accumulate there as both working location and archive. A single stable symlink at the project root — =daily-prep.org= — points at the current day's file, repointed each prep run with =ln -sf=. Replaces the prior model where the doc was born in =inbox/YYYY-MM-DD-daily-prep.org=, yesterday's stayed in =inbox/=, and older docs were =mv='d into the =daily-prep/= archive (old Phase 8). Consumers resolve the root symlink instead of computing a dated filename or searching =inbox/=: the Emacs opener =C-c p d= (=cj/open-project-daily-prep=, repointed from =inbox/today-prep.org= to =daily-prep.org= — handoff filed to the =.emacs.d= project 2026-06-01), next-day Phase 2, and the standup lookback (Phase A step 5, which now globs =daily-prep/= and takes the file before the symlink's target). Touchpoints updated: Phase A step 5 + slim-Phase-A step 2 (lookback), standup-only "Where the brief lands," Phase 8 (rewritten as "Repoint the Current-Day Symlink"). Cross-workflow: =triage-intake.org='s sentinel-anchor fallback dropped its =inbox/= prep-doc path. (=wrap-it-up.org= was left as-is — its =inbox/= references are about =lint-followups.org= routing, not the prep doc, so they stay correct.) Migration is one-time per project: move existing =inbox/*-daily-prep.org= into =daily-prep/= and create the root symlink at the most recent.
 
 *** 2026-06-10: Manager Tools prep additions — 5-day look-ahead, daily big-ball, decline gate
-Three additions folded in from the Manager Tools / Career Tools casts on preparing-for-your-day and meeting prep. None adds a new prep-doc section (the fixed-section rule holds — the look-ahead feeds Heads-up / Anchor Tasks). (1) *5-Day Look-Ahead* — Phase A widens the calendar fetch from the prep day to the prep day plus the next 5 days, and a new Phase 1 sub-section scans that forward window for three buckets: meetings that need prep, traps (time-zone mismatch, double-booking, overrun, an unneeded recurring meeting), and focus blocks to protect. A scan-and-flag pass, not full prep. (2) *Daily big-ball* — Phase 3 sub-step 3a item 5 pulls one important-but-not-urgent (Quadrant-2) task per day and slates a ~15-minute chunk, since strategic work only lands when broken into small daily pieces. (3) *Decline gate* — Phase 1 item 5 reframes "what Craig needs" from attending to contributing, and adds a send-regrets gate: a meeting with no objective and no contribution is a decline candidate for Craig's call at review. The look-ahead's meeting-prep references are conditional ("where the project has one") because meeting-prep is currently a project-only workflow, not a template.
+Three additions folded in from the Manager Tools / Career Tools casts on preparing-for-your-day and meeting prep. None adds a new prep-doc section (the fixed-section rule holds — the look-ahead feeds Heads-up / Anchor Tasks). (1) *5-Day Look-Ahead* — Phase A widens the calendar fetch from the prep day to the prep day plus the next 5 days, and a new Phase 1 sub-section scans that forward window for three buckets: meetings that need prep, traps (time-zone mismatch, double-booking, overrun, an unneeded recurring meeting), and focus blocks to protect. A scan-and-flag pass, not full prep. (2) *Daily big-ball* — Phase 3 sub-step 3a item 5 pulls one important-but-not-urgent (Quadrant-2) task per day and slates a ~15-minute chunk, since strategic work only lands when broken into small daily pieces. (3) *Decline gate* — Phase 1 item 5 reframes "what Craig needs" from attending to contributing, and adds a send-regrets gate: a meeting with no objective and no contribution is a decline candidate for Craig's call at review. The look-ahead's meeting-prep references link directly to =meeting-prep.org= (promoted to a template 2026-06-10).