feat(lead): lead-backlog löst projekt-ins-backlog ab

Eigener Skill für die Überführung ganzer Projekte ins Backlog;
lead-radar verweist per Für-dich-Punkt darauf.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
m3ta-chironandClaude Opus 5.5 committed 2026-11-01 16:23:37 +01:00
1 parent ac6208717c
commit 90e8791f5c
5 files changed
+180 -3

No files matched your search

+1 -1
View File
@@ -64,7 +64,7 @@ Open the mode's reference and follow it; it says which keys to read, how to judg
Answer in German, in this order:
1. **Lagebild**: the mode's template from its reference. Judgement first, lists second; every item with its link.
2. **Vorschläge**: one numbered list across the whole run. Each entry: number, object (title + link), action, new value (owner / date / list), and the comment text that will go on the object. Use only the actions the approval protocol allows; anything outside it (archive a project, create a list, ping someone) becomes a point for Sascha himself, marked `Für dich:` and left unnumbered.
2. **Vorschläge**: one numbered list across the whole run. Each entry: number, object (title + link), action, new value (owner / date / list), and the comment text that will go on the object. Use only the actions the approval protocol allows; anything outside it (archive a project, create a list, ping someone) becomes a point for Sascha himself, marked `Für dich:` and left unnumbered. A stalled project or one that is really just an idea becomes `Für dich: /lead-backlog <Projekt>`.
3. **⚠️ Drift** (only when `drift` is non-empty or step 1 hit an ID mismatch): one line per finding, followed by numbered proposals in the same list that fix the OKF side (e.g. update an ID row in `systems/basecamp.md`, add a minimal profile via `lead-profile`). Findings whose fix is a team decision (`liste_ausserhalb_regel`) go to the Friday close as `Für dich:` points.
End with the approval question: "Freigabe für alle, Abwahl per Nummer, oder einzelne Punkte ändern?"