--- 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 `basecamp` skill before Basecamp CLI actions. - Target project: `🔒 Meins` (known ID: `43475695`). If the ID fails, resolve by project name `Meins`. - 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`/`--jq` for Basecamp reads; use `--no-subscribe` for 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 & Notizen` - `01 Entscheidungen & Leitplanken` - `02 Projekte & Initiativen` - `03 Prozesse & Automatisierung` - `04 Wissen & Referenzen` - `Wochenreviews` (create when running the first weekly review) **To-do lists** - `01 Inbox` — unsorted capture - `02 Nächste Schritte` — active next actions - `03 Wartet auf Rückmeldung` — blocked/delegated items - `04 CEO Meeting Follow-ups` — meeting follow-ups - `05 Backlog / Später` — parked topics ## Meeting-to-Basecamp workflow 1. Inspect project structure: `basecamp files list --in 43475695 --json` and `basecamp todolists list --in 43475695 --json`. 2. Summarize the transcript in German with these sections: - Executive Summary - Entscheidungen / Leitplanken - Themenblöcke - Offene Fragen - Risiken & unklare Begriffe - Angelegte To-dos 3. Create the document in `Meetings` with title: `YYYY-MM-DD – `. 4. 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 5. 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` 6. 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?”. 1. Read all todolists in `Meins`, then fetch incomplete todos per list. Also fetch completed todos to identify last-week wins when available. 2. 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 3. 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 4. 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 5. Before mutating existing todos in bulk, ask for approval. After approval, apply changes in small batches and verify. 6. Save a weekly review document in `Wochenreviews` titled `YYYY-MM-DD – Wochenreview To-dos`, unless the user only wants a chat summary. ## Weekly review output template ```md # 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.