134 lines
4.9 KiB
Markdown
134 lines
4.9 KiB
Markdown
---
|
||
name: basecamp-weekly-meeting-prep
|
||
description: 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.
|
||
compatibility: opencode
|
||
---
|
||
|
||
# Basecamp Weekly Meeting Prep
|
||
|
||
## Core rules
|
||
|
||
- Always load/use the `basecamp` skill before Basecamp CLI actions.
|
||
- Also use `basecamp-meins-meetings` when 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 name `Meins`.
|
||
- Default prep document location: Docs & Files → `Meetings` or `Wochenreviews` if 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`/`--jq` for reads and `--no-subscribe` for 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
|
||
|
||
1. All todolists in `Meins`, especially:
|
||
- `02 Nächste Schritte`
|
||
- `03 Wartet auf Rückmeldung`
|
||
- `04 CEO Meeting Follow-ups`
|
||
- `05 Backlog / Später`
|
||
2. Recent documents in:
|
||
- `Meetings`
|
||
- `Wochenreviews` if present
|
||
- `01 Entscheidungen & Leitplanken` if relevant
|
||
3. Recent completed todos if available.
|
||
4. Any user-supplied meeting context, transcript, rough notes, or agenda request.
|
||
|
||
## Preparation workflow
|
||
|
||
1. Inspect Basecamp structure and resolve folder/list IDs.
|
||
2. Fetch open todos per relevant list; include due dates, descriptions, assignees, and URLs.
|
||
3. Identify recent completions or changes since the last weekly if detectable.
|
||
4. Read the latest meeting notes / weekly review documents when relevant.
|
||
5. Classify topics:
|
||
- `Entscheidung nötig` — needs CEO/leadership decision
|
||
- `Blockiert` — waiting on a person, external input, unclear mandate
|
||
- `Überfällig` — due date passed or urgency high
|
||
- `Update reicht` — progress information only
|
||
- `Nicht besprechen` — valid but no airtime this week
|
||
6. Build a meeting agenda with a recommended order:
|
||
- urgent blockers first
|
||
- decisions second
|
||
- short updates third
|
||
- backlog/strategic topics last
|
||
7. Draft exact talking points in Sascha's voice: direct, pragmatic, internally usable, no inflated wording.
|
||
8. If requested, create a Basecamp prep document and verify its link.
|
||
|
||
## Weekly prep output template
|
||
|
||
```md
|
||
# 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:
|
||
|
||
1. Create or reuse a folder:
|
||
- preferred: `Meetings` for agenda/prep docs
|
||
- alternative: `Wochenreviews` for recurring review docs
|
||
2. Title: `YYYY-MM-DD – Weekly Vorbereitung`.
|
||
3. Use `--no-subscribe` unless notifications are explicitly requested.
|
||
4. Re-read the document with `basecamp files show <id> --in 43475695 --json` and report the link.
|
||
|
||
## After-meeting workflow
|
||
|
||
When the user provides meeting notes after the weekly:
|
||
|
||
1. Summarize decisions separately from discussion.
|
||
2. Convert only concrete commitments into todos.
|
||
3. 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`
|
||
4. Create/update the meeting document only after checking for duplicates.
|
||
5. 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.
|