5.0 KiB
5.0 KiB
name: basecamp-meins-meetings description: Use when maintaining Sascha Koenig's personal Basecamp project "Meins": saving meeting summaries, extracting follow-up todos, creating project structure, or running weekly todo reviews / week-to-week assessments. compatibility: opencode
Basecamp Meins Meetings
Core rules
- Always load/use the
basecampskill before Basecamp CLI actions. - Target project:
🔒 Meins(known ID:43475695). If the ID fails, resolve by project nameMeins. - Default meeting folder: Docs & Files →
Meetings(known folder ID:10028633782). If missing, create/find it before writing. - Avoid duplicates: inspect folders, todolists, documents, and todos before creating anything.
- Use
--json/--jqfor Basecamp reads; use--no-subscribefor documents unless the user asks for notifications. - Treat transcripts as imperfect. Mark uncertain names/terms explicitly instead of inventing certainty.
Default personal structure
Ensure these exist when the user asks to structure the project:
Docs & Files folders
00 Eingang & Notizen01 Entscheidungen & Leitplanken02 Projekte & Initiativen03 Prozesse & Automatisierung04 Wissen & ReferenzenWochenreviews(create when running the first weekly review)
To-do lists
01 Inbox— unsorted capture02 Nächste Schritte— active next actions03 Wartet auf Rückmeldung— blocked/delegated items04 CEO Meeting Follow-ups— meeting follow-ups05 Backlog / Später— parked topics
Meeting-to-Basecamp workflow
- Inspect project structure:
basecamp files list --in 43475695 --jsonandbasecamp todolists list --in 43475695 --json. - Summarize the transcript in German with these sections:
- Executive Summary
- Entscheidungen / Leitplanken
- Themenblöcke
- Offene Fragen
- Risiken & unklare Begriffe
- Angelegte To-dos
- Create the document in
Meetingswith title:YYYY-MM-DD – <kurzer Meetingtitel>. - Extract only actionable todos. Each todo needs:
- prefix by topic (
SAN/BDE:,AZ-Welt:,Buchhaltung:, etc.) - concrete next action
- description with context, definition of done, blocker/dependency if known
- assignee
me - due date only if explicit or reasonably inferable; otherwise leave undated or ask
- prefix by topic (
- Put todos into the best list:
- immediate work →
02 Nächste Schritte - blocked/delegated →
03 Wartet auf Rückmeldung - CEO transcript follow-ups →
04 CEO Meeting Follow-ups - vague/later →
05 Backlog / Später
- immediate work →
- Verify by re-reading the document/list and report links + counts.
Weekly todo review workflow
Use when the user asks for a weekly review, week-to-week assessment, todo evaluation, or “was ist diese Woche wichtig?”.
- Read all todolists in
Meins, then fetch incomplete todos per list. Also fetch completed todos to identify last-week wins when available. - Classify every open todo:
🔥 Diese Woche erledigen/entscheiden— due now, strategically important, or blocking others⚠️ Überfällig— due date passed⏳ Wartet auf Rückmeldung— delegated, blocked, or needs another person🧹 Aufräumen— unclear, duplicate, stale, or no longer relevant📦 Backlog— valid but not for this week
- Score each important todo on four dimensions:
- urgency: overdue / due this week / later / no date
- clarity: next action obvious? definition of done present?
- momentum: new / idle 7+ days / idle 30+ days
- ownership: Sascha / waiting on someone / unclear
- Produce a review with:
- top 5 priorities for the coming week
- overdue items and recommended action
- stale or unclear items to rewrite/delete/move
- waiting-on list with who/what is needed
- completed items since last review if detectable
- concrete recommendations: keep, do, defer, delegate, delete, or clarify
- Before mutating existing todos in bulk, ask for approval. After approval, apply changes in small batches and verify.
- Save a weekly review document in
WochenreviewstitledYYYY-MM-DD – Wochenreview To-dos, unless the user only wants a chat summary.
Weekly review output template
# Wochenreview To-dos – YYYY-MM-DD
## Kurzfazit
[2–4 Sätze]
## Top 5 für diese Woche
1. [Todo] — Warum jetzt / nächster Schritt
## Überfällig
- [Todo] — Empfehlung: do / defer / delete / clarify
## Wartet auf Rückmeldung
- [Todo] — wartet auf [Person/Sache], nächster Nachfasspunkt
## Aufräumen
- [Todo] — Grund und empfohlene Aktion
## Erledigt seit letztem Review
- [Todo]
## Vorgeschlagene Änderungen
- [konkrete Basecamp-Änderungen, erst nach Freigabe ausführen]
Common mistakes
- Do not create final-looking todos from unclear transcript fragments; mark them as clarification tasks.
- Do not silently notify people from the personal project.
- Do not treat the weekly review as just a list dump; it must include judgment and recommendations.
- Do not close, delete, or move many todos without explicit approval.