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>
This commit is contained in:
m3ta-chironandClaude Fable 5.1 committed 2026-11-10 09:41:12 +01:00
1 parent 16dac49044
commit 06acee80c2
11 files changed
+75 -60

No files matched your search

+5 -5
View File
@@ -18,10 +18,10 @@ The single path for meeting follow-up in the `lead-*` family. One run = one reco
Read before acting; these hold the facts, this skill holds only behaviour:
- `/home/sascha.koenig/p/PM/.okf/processes/meeting-runden.md`: round profiles (filing project, Sally search term, participants)
- `/home/sascha.koenig/p/PM/.okf/processes/it-basecamp-regeln.md`: to-do rules, the six 👥 IT lists, approval protocol
- `/home/sascha.koenig/p/PM/.okf/systems/basecamp.md`: project, list and folder IDs
- `/home/sascha.koenig/p/PM/.okf/organization/*.md`: people and their Basecamp person IDs
- `/home/sascha.koenig/ap/PM/.okf/processes/meeting-runden.md`: round profiles (filing project, Sally search term, participants)
- `/home/sascha.koenig/ap/PM/.okf/processes/it-basecamp-regeln.md`: to-do rules, the six 👥 IT lists, approval protocol
- `/home/sascha.koenig/ap/PM/.okf/systems/basecamp.md`: project, list and folder IDs
- `/home/sascha.koenig/ap/PM/.okf/organization/*.md`: people and their Basecamp person IDs
An ID that fails: resolve by name, carry on, and mention the mismatch in the final report.
@@ -97,7 +97,7 @@ Add, under the same approval, a proposal "als OKF-Decision anlegen?" for each de
Present everything as one numbered list (title, owner, due date, list, description). The user approves as a batch, drops items by number, or edits single items. Act on an explicit answer only.
Create the approved to-dos (`basecamp todos create … --assignee <id> --due <date> --list <id> --in <project> --json`). Write approved decisions as `type: Decision` concepts in `/home/sascha.koenig/p/PM/.okf/decisions/` with `status: draft`, source `sally://recording/<id>`, and a link to the summary document; validate the bundle with the `validate` skill.
Create the approved to-dos (`basecamp todos create … --assignee <id> --due <date> --list <id> --in <project> --json`). Write approved decisions as `type: Decision` concepts in `/home/sascha.koenig/ap/PM/.okf/decisions/` with `status: draft`, source `sally://recording/<id>`, and a link to the summary document; validate the bundle with the `validate` skill.
**Done when** every approved item exists and you report: document URL, to-do URLs, OKF files, and any ID mismatches from the sources-of-truth check.