Files
agent-prod/skills/lead-radar/references/ich.md
T
m3ta-chironandClaude Fable 5.1 06acee80c2 feat(lead): lead-radar ich an Cockpit-Datenschicht angepasst, Pfade ap/PM
- ich.md: Input-Keys des neuen Scope ich, Sally über attendanceStatus und tasks-Sections, Abwesenheitsregel nur bei Terminkollision, Häufungs-Check je Tag, Eingang IT, Persist-Schritt mit State-Lauf und OKF-Pflege
- execute.md: Umzug in anderes Projekt, --todoset, Mitgliedschaftsprüfung
- SKILL.md: Personen-ID-Tabelle als Quelle, Laufzeit, Drift-Pflicht für neue IDs
- person.md: „Nicht delegierbar“, Stub-Hinweis
- alle lead-*-Skills: veraltete Pfade p/PM → ap/PM

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
2026-11-10 09:41:12 +01:00

118 lines
9.0 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# 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-10-28-lead-skill-familie.md`, Modus-Tabelle; the mode replaced `meins` on 06.11.2026): 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 --dry-run`)
```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 and state). Daily Quests (routine to-dos in 🔒 Meins) are excluded everywhere. 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`, counted across runs), `erledigt`, `puenktlich`, `termintreue`, `delegiert`, `sonstig_weg`, `neu`, `vorheriger_lauf`. `vorheriger_lauf == null` is the first run after a state reset: comparison fields are empty, say "Vergleich ab dem zweiten Lauf".
- `klassifikation`: `ueberfaellig`, `heute`, `diese_woche`, `still_30d`, `ohne_termin`.
- `listen_je_projekt`: every open to-do, grouped project → list; each to-do carries `verschiebungen`.
- `erledigt`: completed since the last run, each with `completed_at` and `puenktlich`. `completed_at` comes from Sascha's own timeline events; a to-do someone else checked off has `null` and counts neither as punctual nor as late.
- `delegiert`: open since the last run but no longer assigned to Sascha. `sonstig_weg`: archived or unassigned.
- `verschoben`, `mehrfach_verschoben`, `neu`: the to-dos behind the counters.
- `eingang_it`: Sascha's to-dos in the triage list 📥 Eingang IT of 🔁 Übergaben & Koordination. Each is a request from a department, usually without a date: it needs a date, a handover to the project where the work lives (see `execute.md`, project move) or a comment with a decision.
- `faelligkeiten_je_tag`: open to-dos per due date for the next 14 days.
- `verlauf`: the last four metric rows, oldest first. `state_geschrieben`: false on `--dry-run`.
- Top level: `abwesenheiten` (next 10 days, incl. Sascha's own), `drift`, `errors`.
Read `processes/meeting-runden.md` before section 1, the OKF profiles in `/home/sascha.koenig/ap/PM/.okf/organization/` before section 3, including the list **Nicht delegierbar** in `sascha-koenig.md`.
## 1. Zusagen (C): commitments without a to-do
1. Sally `search_appointments` with `participant` = Sascha for the last 7 days (back to `vorheriger_lauf` when that is longer ago). Keep only appointments where Sascha's `attendanceStatus` is `attended` or the appointment has no attendance data and Sascha accepted; drop meetings he did not attend. Keep recordings with a summary; list appointments without recording or with a pending summary in one line as "nicht ausgewertet".
2. Per recording: `get_summary` with `includeDetails=true`. Commitments live in `sections` with `sectionType: "tasks"` (`responsibleUserName` = Sascha) and in the `decisions`/`summary` sections that name him. Sally's own task list (`list_tasks`) is empty in this setup; do not rely on it.
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`; something Sascha waits for from others → `03 Wartet auf Rückmeldung`; a wish without capacity → `05 Backlog / Später` without date), owner Sascha, date from the meeting or marked `Vorschlag`, description = one context sentence + the Sally recording id.
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 `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
Items the morning run (`tag`) moved today with a reason need nothing more; say so in one line.
## 3. Abgeben (B): delegation candidates
Candidates: open to-dos whose title or description matches role, responsibilities or skills in a profile, and that are not on the **Nicht delegierbar** list in Sascha's profile. A profile that is still a minimal stub (no skills section) supports only role-level matches; say "nach Rolle, Profil ohne Skills" in the proposal. Absence rule: a person is excluded only when the to-do's due date (or the proposed one) falls into an absence in `abwesenheiten`, or the absence covers more than 5 of the next 10 working days; otherwise mention the absence in the comment and pick a date after it. The person must be a member of the to-do's project (`basecamp people list --in <project-id>`); otherwise `Für dich: <Name> ins Projekt aufnehmen`.
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). Then the load check from `faelligkeiten_je_tag`: more than 6 to-dos on one day, or more than 12 in one week, is a cluster; name the day and propose which ones move, as numbered defer proposals or a `Für dich:` line. Sascha's own absences count as zero-capacity days.
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. `eingang_it` items get a date, a project move or a decision comment each.
## 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, inkl. Datenlage: blinde Quellen, nicht ausgewertete Meetings]
## Deine 5 für diese Woche
1. [To-do](link) · Projekt — warum jetzt / nächster Schritt
Fälligkeiten: [Tag: N, Tag: N …] → Häufung am …
## 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 / Umzug nach Projekt X
## Erledigt seit letztem Review
- [To-do](link) · pünktlich / zu spät / ohne Zeitstempel
## Kennzahlen
| | heute | −1 | −2 | −3 | −4 |
|---|---|---|---|---|---|
| offen | | | | | |
| ohne Termin | | | | | |
| überfällig | | | | | |
| still ≥ 30 d | | | | | |
| 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` (ID in `systems/basecamp.md`) 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 from the create response and keep its URL (`files documents show` cannot fetch a single document, see the CLI gotchas in `systems/basecamp.md`). 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 `tools/it-cockpit/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. Report both files as changed paths; git stays with Sascha.
3. Every ID or fact the run created or discovered (a new folder, a person ID, a renamed list) goes into the OKF in the same run, as a numbered proposal under ⚠️ Drift, not only into the document.