4.9 KiB
4.9 KiB
name, description, compatibility
| name | description | compatibility |
|---|---|---|
| basecamp-weekly-meeting-prep | Use when preparing Sascha Koenig's weekly meeting / weekly leadership sync from the personal Basecamp project "Meins", including agenda creation, todo review, blockers, decisions, follow-ups, and optional Basecamp prep documents. | opencode |
Basecamp Weekly Meeting Prep
Core rules
- Always load/use the
basecampskill before Basecamp CLI actions. - Also use
basecamp-meins-meetingswhen the task touches meeting notes, follow-up todos, or weekly todo assessment. - Target project:
🔒 Meins(known ID:43475695). If the ID fails, resolve by project nameMeins. - Default prep document location: Docs & Files →
MeetingsorWochenreviewsif the user wants a weekly-review-style document. - Do not create/move/close many todos without explicit approval. Preparation may read freely; mutation needs confirmation.
- Use
--json/--jqfor reads and--no-subscribefor personal prep documents unless the user asks otherwise.
Purpose
Prepare Sascha for a weekly meeting by turning Basecamp state into a sharp agenda:
- what happened since the last weekly
- what is overdue or stuck
- what needs a decision
- what should be escalated
- which topics deserve airtime
- what follow-ups should be captured after the meeting
Inputs to inspect
- All todolists in
Meins, especially:02 Nächste Schritte03 Wartet auf Rückmeldung04 CEO Meeting Follow-ups05 Backlog / Später
- Recent documents in:
MeetingsWochenreviewsif present01 Entscheidungen & Leitplankenif relevant
- Recent completed todos if available.
- Any user-supplied meeting context, transcript, rough notes, or agenda request.
Preparation workflow
- Inspect Basecamp structure and resolve folder/list IDs.
- Fetch open todos per relevant list; include due dates, descriptions, assignees, and URLs.
- Identify recent completions or changes since the last weekly if detectable.
- Read the latest meeting notes / weekly review documents when relevant.
- Classify topics:
Entscheidung nötig— needs CEO/leadership decisionBlockiert— waiting on a person, external input, unclear mandateÜberfällig— due date passed or urgency highUpdate reicht— progress information onlyNicht besprechen— valid but no airtime this week
- Build a meeting agenda with a recommended order:
- urgent blockers first
- decisions second
- short updates third
- backlog/strategic topics last
- Draft exact talking points in Sascha's voice: direct, pragmatic, internally usable, no inflated wording.
- If requested, create a Basecamp prep document and verify its link.
Weekly prep output template
# Weekly Vorbereitung – YYYY-MM-DD
## Kurzfazit
[2–4 Sätze: Lage, Fokus, größte Risiken]
## Agenda-Vorschlag
1. [Thema] — Ziel: Entscheidung / Klärung / Update
2. ...
## Entscheidungen nötig
- [Thema]
- Kontext:
- Optionen:
- Empfehlung:
- Konkrete Frage im Meeting:
## Blocker / Eskalationen
- [Thema] — blockiert durch [Person/Sache], gewünschte Entscheidung oder Hilfe
## Überfällige / kritische To-dos
- [Todo] — Empfehlung: erledigen / verschieben / delegieren / streichen
## Updates, die kurz reichen
- [Thema] — 1–2 Sätze Status
## Nicht diese Woche besprechen
- [Thema] — Grund
## Gesprächsnotizen / Formulierungen
- „[präzise Formulierung für schwierige Themen]“
## Nach dem Meeting erfassen
- potenzielle Follow-up-To-dos
- Entscheidungen, die dokumentiert werden müssen
Basecamp document workflow
When saving the prep:
- Create or reuse a folder:
- preferred:
Meetingsfor agenda/prep docs - alternative:
Wochenreviewsfor recurring review docs
- preferred:
- Title:
YYYY-MM-DD – Weekly Vorbereitung. - Use
--no-subscribeunless notifications are explicitly requested. - Re-read the document with
basecamp files show <id> --in 43475695 --jsonand report the link.
After-meeting workflow
When the user provides meeting notes after the weekly:
- Summarize decisions separately from discussion.
- Convert only concrete commitments into todos.
- Put follow-ups into the most appropriate list:
- immediate action →
02 Nächste Schritte - waiting/delegated →
03 Wartet auf Rückmeldung - leadership/CEO follow-up →
04 CEO Meeting Follow-ups - later →
05 Backlog / Später
- immediate action →
- Create/update the meeting document only after checking for duplicates.
- Verify created todos and document links.
Common mistakes
- Do not turn every todo into an agenda item; weekly airtime is limited.
- Do not hide uncomfortable topics. Surface blockers and overdue items clearly.
- Do not over-draft corporate language; use practical, direct internal wording.
- Do not make unsupported assumptions from unclear transcripts; mark uncertainty.
- Do not mutate Basecamp in bulk during preparation without explicit approval.