feat(lead): KI-Marker und Kommentarstil in Lead-Skills aufnehmen

- lead-backlog, lead-meeting-followup, lead-meeting-prep, lead-radar: Kommentare (Basecamp, Zammad-Notizen) im Stil von sascha-internal-communication-style schreiben
- Jeder Kommentar endet mit einer Leerzeile und dem kursiven Marker "*✨unterstützt durch KI✨*"
- Vorschläge zeigen den Kommentar exakt so, wie er gepostet wird, inklusive Marker
- lead-radar execute.md: Zammad-Notizen als text/html senden, damit die Kursivschrift rendert
This commit is contained in:
m3ta-chiron committed 2026-11-04 14:52:53 +01:00
1 parent 90e8791f5c
commit 38780da558
5 files changed
+52 -6

No files matched your search

+11 -1
View File
@@ -25,6 +25,16 @@ An ID that fails: resolve by name, carry on, and mention the mismatch in the fin
The run is read-only. Load the `basecamp` skill before any Basecamp CLI call; check flags with `basecamp <cmd> --agent --help`.
**Comments** (Basecamp comments, Zammad internal notes): load `sascha-internal-communication-style` and write the German text in that style. End every comment with one empty line and the AI marker in italics, exactly:
```md
<Kommentartext>
*✨unterstützt durch KI✨*
```
Show the comment in the proposal exactly as it will be posted, marker included.
## Steps
### 1. Identify the round
@@ -110,7 +120,7 @@ Then offer, as one numbered list, only what applies:
1. **Profile fields:** the `offen` values the user answered in step 1, as exact replacement lines for `meeting-runden.md`. After an explicit yes, edit the profile (only those lines) and validate the bundle with the `validate` skill.
2. **Basecamp prep document:** on request only. Location from the round profile, default 🔒 Meins → folder `Meetings`; title `YYYY-MM-DD – <Runde> Vorbereitung` (meeting date); `--no-subscribe`; pass the Markdown from a temp file in the scratchpad; read it back and report the URL.
3. **To-do changes** the prep suggests (owner, due date, move, park, complete): propose them per the approval protocol in `it-basecamp-regeln.md` and execute only approved items, each with a short reason comment.
3. **To-do changes** the prep suggests (owner, due date, move, park, complete): propose them per the approval protocol in `it-basecamp-regeln.md` and execute only approved items, each with a short reason comment (style and AI marker as above).
**Done when** the prep is delivered and every offered write is either executed after an explicit yes or left untouched.