3.6 KiB
Mode portfolio: monthly portfolio review
When: monthly (first run December). Lens: every project Sascha holds open to-dos in. Per project: is there an owner, a goal, a next milestone? Then: keep, hand over, park, or cut.
Input (--scope portfolio)
portfolio.projekte[]: project_id, project, saschas_offene, ueberfaellig, ohne_termin, still_30d, okf_konzepte (OKF project files linking to that Basecamp project), todos (Sascha's open to-dos there).
Sort the rows first:
- Initiatives (time-bounded projects): the review subject.
- Standing spaces (👥 team spaces, 🔒 Meins, 📥 Backlog, 🔁 coordination, templates; archetypes in
systems/basecamp.md): no owner/goal/milestone check; list them in one block with their counts only.
okf_konzepte is matched by link, so a concept may only mention the project. Open each one and keep it as the project's concept only if it is about that project.
Per initiative: three checks
| Check | Source | Missing → |
|---|---|---|
| Owner | OKF concept (owner/Verantwortlich); else Basecamp project description | Owner fehlt |
| Ziel | OKF concept (goal/purpose) | Ziel fehlt → OKF stub proposal or Für dich: |
| Nächster Meilenstein | Basecamp: next dated to-do or schedule entry in the project (basecamp todos list --in <id> --json, basecamp schedule …) |
Meilenstein fehlt |
Recommendation (one per initiative)
- weiterführen: all three present and Sascha's to-dos move; proposals only for overdue/undated items (date, comment).
- abgeben: Sascha is not the natural owner. Proposals: owner change of Sascha's to-dos to the named successor + comment with context. The project-level handover itself is a
Für dich:point. - parken: no momentum and no deadline. Proposals: Sascha's to-dos to the project's backlog or to 📥 Backlog (see
execute.md), each with comment. - streichen: goal obsolete. Proposals: complete Sascha's to-dos with a comment naming the decision. Archiving the project is a
Für dich:point.
OKF: task state out, links in (spec §3.2)
For every OKF concept of an initiative, find task state: to-do lists, "nächster Schritt bis …", status-of-work lines, dated action items. Propose one numbered OKF edit per file that replaces that state with a link to the Basecamp project or list, keeping goals, context and decisions. Show a short before/after excerpt in the proposal. Also propose missing owner/goal lines where the review established them.
Lagebild template (chat and document)
# Portfolio-Review – YYYY-MM-DD
## Kurzfazit
[2–4 Sätze: wie viele Initiativen, wo Sascha zu viel hält, was abgegeben/geparkt/gestrichen werden soll]
## Initiativen
| Projekt | Owner | Ziel | Nächster Meilenstein | Deine offenen | Empfehlung |
|---|---|---|---|---|---|
| [Name](link) | … / fehlt | ✅ / fehlt | TT.MM. / fehlt | N (davon M überfällig) | weiterführen / abgeben an X / parken / streichen |
## Begründungen
- **Projekt**: warum diese Empfehlung
## Ständige Bereiche
- <👥 IT, 🔒 Meins … mit Anzahl deiner offenen>
## OKF: Aufgabenstand durch Links ersetzt
- <Datei → was ersetzt wird>
## Vorgeschlagene Änderungen
1. [nummeriert wie in der Freigabeliste; im Dokument mit Status ✅ / ❌ / ⚠️]
Document
After execution, save the review as document YYYY-MM-DD – Portfolio-Review in 🔒 Meins → folder 02 Projekte & Initiativen (IDs in systems/basecamp.md) with basecamp files documents create "<Titel>" "$(cat <scratchpad-file>)" --in <meins-id> --vault <folder-id> --no-subscribe --json. Read it back and keep its URL.