- Neuer Modus `ich` (Wochenselbstreview) über alle Projekte statt nur 🔒 Meins: Zusagen aus Sally, Termine, Abgeben, Fokus und Kennzahlen mit Verlauf
- `references/meins.md` entfällt, ersetzt durch `references/ich.md`; Trigger und Invocation in SKILL.md angepasst
- `tag`: neuer Block „Du heute“ mit eigenen fälligen und mehrfach verschobenen To-dos
- `execute.md`: To-do anlegen nur im Modus `ich`, nur für eigene Zusagen
- `lead-meeting-prep`: Meins-Items über `--projects` statt `--scope meins` laden
106 lines
6.3 KiB
Markdown
106 lines
6.3 KiB
Markdown
# Mode `ich`: weekly self-review
|
||
|
||
When: weekly, ideally Friday after the close or Monday morning. Lens: Sascha's own commitments across **all** projects, not only 🔒 Meins. Four sections answer four weaknesses (spec `docs/2026-11-05-lead-radar-ich.md` §1): A commitments kept (Termintreue), B too much held personally, C open loops from meetings, D focus. Then a look back at the numbers.
|
||
|
||
## Boundary (spec §2.3)
|
||
|
||
The self-lens is the mirror image of the person lens: scores, trends and a persisted trail are allowed, because they are about Sascha only. The output never contains numbers about colleagues; delegation proposals name role and skills from the profile, not workload or comparisons. The only effect on others is the comment on a delegated to-do.
|
||
|
||
## Input (`--scope ich`)
|
||
|
||
```bash
|
||
python3 tools/it-cockpit/cockpit.py --json --scope ich --dry-run
|
||
```
|
||
|
||
Run the review on `--dry-run`; the state is written at the very end (see Document). Keys under `ich`:
|
||
|
||
- `kennzahlen`: `offen`, `je_projekt`, `ohne_termin`, `ohne_termin_anteil`, `ueberfaellig`, `still_30d`, `verschoben` (ids whose date moved later since the last run), `mehrfach_verschoben` (`verschiebungen ≥ 3`), `erledigt`, `puenktlich`, `termintreue`, `delegiert`, `sonstig_weg`, `neu`, `vorheriger_lauf`. `vorheriger_lauf == null` is the first run: comparison fields are `null`, say "Vergleich ab dem zweiten Lauf".
|
||
- `klassifikation`: `ueberfaellig`, `heute`, `diese_woche`, `still_30d`, `ohne_termin` (Daily Quests excluded).
|
||
- `listen_je_projekt`: every open to-do, grouped project → list.
|
||
- `erledigt`: completed since the last run, each with `completed_at` (null when Basecamp gave no event).
|
||
- `verlauf`: the last four metric rows, oldest first.
|
||
- Top level: `abwesenheiten` (next 10 days), `drift`, `errors`.
|
||
|
||
Read the OKF profiles in `/home/sascha.koenig/p/PM/.okf/organization/` before section 3, and `processes/meeting-runden.md` before section 1.
|
||
|
||
## 1. Zusagen (C): commitments without a to-do
|
||
|
||
1. Sally `search_appointments`: the last 7 days (back to `vorheriger_lauf` when that is longer ago), Sascha as participant. Keep recordings with `sallyStatus = transcriptionAndSummarizationCompleted`; list the others in one line as "noch nicht ausgewertet".
|
||
2. Per recording: `list_tasks` filtered to tasks assigned to Sascha, plus follow-ups from `get_summary` that name Sascha.
|
||
3. Match each commitment against `listen_je_projekt` and `erledigt` by title similarity and the round's project (round profile in `meeting-runden.md`). Match → nothing. No match → proposal **To-do anlegen**: project from the round profile (default 🔒 Meins → `02 Nächste Schritte`), owner Sascha, date from the meeting or marked `Vorschlag`, description = one context sentence + link to the Sally recording.
|
||
4. Commitments Sally assigns to other people are not this mode's business (`lead-meeting-followup`).
|
||
|
||
## 2. Termine (A): overdue and repeatedly moved
|
||
|
||
For every item in `klassifikation.ueberfaellig` and `kennzahlen.mehrfach_verschoben` exactly one recommendation:
|
||
|
||
- **do**: date within this week, comment names the next step
|
||
- **defer**: a new honest date with the reason in the comment. With `verschiebungen ≥ 3` only when Sascha states a reason; otherwise propose **close** or **delegate** instead. The skill never proposes a fourth move without a reason.
|
||
- **close**: complete with a comment saying why it is no longer needed
|
||
|
||
## 3. Abgeben (B): delegation candidates
|
||
|
||
Candidates: open to-dos whose title or description matches role, responsibilities or skills in a profile, and the person is not absent in the next 10 days (`abwesenheiten`). Proposal: owner change + comment with context, definition of done and the mention `[@Vorname Nachname](person:<id>)`. Topics with no matching profile: `Für dich: wem gibst du X?`.
|
||
|
||
At most **five** delegation proposals per run; mention the rest as "weitere Kandidaten: N".
|
||
|
||
## 4. Fokus (D): the five for this week
|
||
|
||
Top 5 with reason (date, weight, blocks others, GF/compliance). Valid items with no room in the next two weeks → park (🔒 Meins → `05 Backlog / Später`, or the project's backlog per `execute.md`). Silent, unclear or duplicate → clarify (comment with the next step) or close.
|
||
|
||
## Rückblick
|
||
|
||
Table of this run's `kennzahlen` next to `verlauf` (up to four earlier runs), then two sentences: what improved, what did not. First run: current state only.
|
||
|
||
## Template (chat and document)
|
||
|
||
```md
|
||
# Wochenreview – YYYY-MM-DD
|
||
|
||
## Kurzfazit
|
||
[2–4 Sätze]
|
||
|
||
## Deine 5 für diese Woche
|
||
1. [To-do](link) · Projekt — warum jetzt / nächster Schritt
|
||
|
||
## Zusagen ohne To-do
|
||
- Zusage · Meeting (Datum) → Vorschlag Nr. N
|
||
|
||
## Termine
|
||
- [To-do](link) · N× verschoben — do / defer / close
|
||
|
||
## Abgeben
|
||
- [To-do](link) → Vorname (Rolle) — Vorschlag Nr. N
|
||
|
||
## Aufräumen
|
||
- [To-do](link) — parken / clarify / close
|
||
|
||
## Erledigt seit letztem Review
|
||
- [To-do](link) · pünktlich / zu spät
|
||
|
||
## Kennzahlen
|
||
| | heute | −1 | −2 | −3 | −4 |
|
||
|---|---|---|---|---|---|
|
||
| offen | | | | | |
|
||
| ohne Termin | | | | | |
|
||
| überfällig | | | | | |
|
||
| Termintreue | | | | | |
|
||
| verschoben / ≥3× | | | | | |
|
||
| delegiert | | | | | |
|
||
| neu | | | | | |
|
||
|
||
[zwei Sätze Trend]
|
||
|
||
## Vorgeschlagene Änderungen
|
||
1. [nummeriert wie in der Freigabeliste; Status ✅ umgesetzt / ❌ abgewählt / ⚠️ fehlgeschlagen]
|
||
```
|
||
|
||
## Document and state
|
||
|
||
After execution (step 4 of `SKILL.md`):
|
||
|
||
1. Save the review as document `YYYY-MM-DD – Wochenreview` in 🔒 Meins → folder `Wochenreviews` with the change list showing what was actually done: `basecamp files documents create "<Titel>" "$(cat <scratchpad-file>)" --in <meins-id> --vault <folder-id> --no-subscribe --json`. Read it back and keep its URL. A user who asks for a chat-only review gets no document.
|
||
2. Run the cockpit once more **without** `--dry-run`: `python3 tools/it-cockpit/cockpit.py --json --scope ich > /dev/null`. This writes `state/ich/snapshot.json` and the day's row in `verlauf.jsonl` with the state after execution, so next week's comparison starts from what was actually done.
|
||
|
||
**First run:** the folder `Wochenreviews` does not exist yet (`systems/basecamp.md` says so). Add one numbered proposal "Ordner `Wochenreviews` in 🔒 Meins anlegen und ID in `systems/basecamp.md` eintragen"; after approval create it with `basecamp files folders create Wochenreviews --in <meins-id> --json` and replace the placeholder in the ID table with the new ID.
|