From 27eefdc9cf47260afaba32ef0593bc6576acae12 Mon Sep 17 00:00:00 2001 From: m3ta-chiron Date: Thu, 5 Nov 2026 10:30:06 +0100 Subject: [PATCH] =?UTF-8?q?feat(lead):=20Erw=C3=A4hnungen=20in=20Lead-Skil?= =?UTF-8?q?ls=20aufnehmen?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit - Adressaten und Betroffene werden als echte Mentions geschrieben (Basecamp `person:`-Link, Zammad `data-mention-user-id`), damit sie benachrichtigt werden - Sascha wird nicht erwähnt, da Schreibzugriffe über seinen Account laufen - Basecamp-Kommentare bleiben ohne `--notify`; Erinnerungen bleiben bei A3 - Betrifft lead-backlog, lead-meeting-followup, lead-meeting-prep und lead-radar (inkl. references/execute.md) --- skills/lead-backlog/SKILL.md | 5 +++++ skills/lead-meeting-followup/SKILL.md | 5 +++++ skills/lead-meeting-prep/SKILL.md | 5 +++++ skills/lead-radar/SKILL.md | 5 +++++ skills/lead-radar/references/execute.md | 8 ++++---- 5 files changed, 24 insertions(+), 4 deletions(-) diff --git a/skills/lead-backlog/SKILL.md b/skills/lead-backlog/SKILL.md index d78cde8..0519d49 100644 --- a/skills/lead-backlog/SKILL.md +++ b/skills/lead-backlog/SKILL.md @@ -34,6 +34,11 @@ Load the `basecamp` skill before any CLI call; check flags with `basecamp Show the comment in the proposal exactly as it will be posted, marker included. +**Mentions**: name every colleague the comment addresses or affects (owner, new owner, whoever is asked something) as a real mention, so they get a notification. A plain name notifies no one. Do not mention Sascha: Basecamp and Zammad writes run under his account. A comment with no addressee gets no mention. Show the mention in the proposal as `@Vorname Nachname`. + +- Basecamp: `[@Vorname Nachname](person:)`, ID from `.okf/organization/`, fallback `basecamp people pingable --jq '.data[] | select(.name == "…")'`. Not a bare `@Name`: the CLI resolves it fuzzily and can hit the wrong person. Only people with access to the project are pingable; for anyone else, say so in the proposal. +- Zammad (internal note, `text/html`): `Vorname Nachname`, uid via `GET /api/v1/users/search?query=`. A typed `@Name` is plain text there. Zammad subscribes the mentioned user to the ticket and notifies them. Mentions count only when the note is created, and only for agents with access to the ticket's group. + ## Steps ### 1. Inventory diff --git a/skills/lead-meeting-followup/SKILL.md b/skills/lead-meeting-followup/SKILL.md index 649b6eb..2d94a0d 100644 --- a/skills/lead-meeting-followup/SKILL.md +++ b/skills/lead-meeting-followup/SKILL.md @@ -37,6 +37,11 @@ Load the `basecamp` skill before any Basecamp CLI call. Check flags with `baseca Show the comment in the proposal exactly as it will be posted, marker included. +**Mentions**: name every colleague the comment addresses or affects (owner, new owner, whoever is asked something) as a real mention, so they get a notification. A plain name notifies no one. Do not mention Sascha: Basecamp and Zammad writes run under his account. A comment with no addressee gets no mention. Show the mention in the proposal as `@Vorname Nachname`. + +- Basecamp: `[@Vorname Nachname](person:)`, ID from `.okf/organization/`, fallback `basecamp people pingable --jq '.data[] | select(.name == "…")'`. Not a bare `@Name`: the CLI resolves it fuzzily and can hit the wrong person. Only people with access to the project are pingable; for anyone else, say so in the proposal. +- Zammad (internal note, `text/html`): `Vorname Nachname`, uid via `GET /api/v1/users/search?query=`. A typed `@Name` is plain text there. Zammad subscribes the mentioned user to the ticket and notifies them. Mentions count only when the note is created, and only for agents with access to the ticket's group. + ## Steps ### 1. Pick the recording diff --git a/skills/lead-meeting-prep/SKILL.md b/skills/lead-meeting-prep/SKILL.md index f1cf8da..4ee5464 100644 --- a/skills/lead-meeting-prep/SKILL.md +++ b/skills/lead-meeting-prep/SKILL.md @@ -35,6 +35,11 @@ The run is read-only. Load the `basecamp` skill before any Basecamp CLI call; ch Show the comment in the proposal exactly as it will be posted, marker included. +**Mentions**: name every colleague the comment addresses or affects (owner, new owner, whoever is asked something) as a real mention, so they get a notification. A plain name notifies no one. Do not mention Sascha: Basecamp and Zammad writes run under his account. A comment with no addressee gets no mention. Show the mention in the proposal as `@Vorname Nachname`. + +- Basecamp: `[@Vorname Nachname](person:)`, ID from `.okf/organization/`, fallback `basecamp people pingable --jq '.data[] | select(.name == "…")'`. Not a bare `@Name`: the CLI resolves it fuzzily and can hit the wrong person. Only people with access to the project are pingable; for anyone else, say so in the proposal. +- Zammad (internal note, `text/html`): `Vorname Nachname`, uid via `GET /api/v1/users/search?query=`. A typed `@Name` is plain text there. Zammad subscribes the mentioned user to the ticket and notifies them. Mentions count only when the note is created, and only for agents with access to the ticket's group. + ## Steps ### 1. Identify the round diff --git a/skills/lead-radar/SKILL.md b/skills/lead-radar/SKILL.md index eb5921a..19798fb 100644 --- a/skills/lead-radar/SKILL.md +++ b/skills/lead-radar/SKILL.md @@ -41,6 +41,11 @@ Load the `basecamp` skill before any Basecamp CLI call; check flags with `baseca Show the comment in the proposal exactly as it will be posted, marker included. +**Mentions**: name every colleague the comment addresses or affects (owner, new owner, whoever is asked something) as a real mention, so they get a notification. A plain name notifies no one. Do not mention Sascha: Basecamp and Zammad writes run under his account. A comment with no addressee gets no mention. Show the mention in the proposal as `@Vorname Nachname`. + +- Basecamp: `[@Vorname Nachname](person:)`, ID from `.okf/organization/`, fallback `basecamp people pingable --jq '.data[] | select(.name == "…")'`. Not a bare `@Name`: the CLI resolves it fuzzily and can hit the wrong person. Only people with access to the project are pingable; for anyone else, say so in the proposal. +- Zammad (internal note, `text/html`): `Vorname Nachname`, uid via `GET /api/v1/users/search?query=`. A typed `@Name` is plain text there. Zammad subscribes the mentioned user to the ticket and notifies them. Mentions count only when the note is created, and only for agents with access to the ticket's group. + ## Steps ### 1. Pull the data diff --git a/skills/lead-radar/references/execute.md b/skills/lead-radar/references/execute.md index 31975a5..4db810d 100644 --- a/skills/lead-radar/references/execute.md +++ b/skills/lead-radar/references/execute.md @@ -8,7 +8,7 @@ Reached from step 4 of `SKILL.md`. The approval protocol in `/home/sascha.koenig 2. Put the comment on the same object: one or two German sentences with the reason in `sascha-internal-communication-style`, ending in `(lead-radar, , YYYY-MM-DD)`, then one empty line and the italic AI marker. Example (Markdown, the CLI converts it): ```md - Neuer Termin 06.11., der Lieferant hat uns die Rückmeldung für KW 45 zugesagt. (lead-radar, freitag, 2026-11-13) + [@Jannik Müller](person:) Neuer Termin 06.11., der Lieferant hat uns die Rückmeldung für KW 45 zugesagt. (lead-radar, freitag, 2026-11-13) *✨unterstützt durch KI✨* ``` @@ -18,7 +18,7 @@ Work through the list in number order. A failing item does not stop the run: not ## Basecamp -Write mentions as plain names (no `@`), and leave `--notify` off: the comment is the trail, reminders belong to automation A3. +Mention the addressees as described under **Mentions** in `SKILL.md` (`[@Name](person:)`), so the comment notifies them. Beyond that, send no extra notifications: no `--notify`, no pings. Reminders belong to automation A3. | Action | Command (check flags with `--agent --help`) | |---|---| @@ -48,10 +48,10 @@ curl -sf -X PUT -H "Authorization: Token token=$ZAMMAD_TOKEN" -H "Content-Type: # internal note (the "why" comment for Zammad) curl -sf -X POST -H "Authorization: Token token=$ZAMMAD_TOKEN" -H "Content-Type: application/json" \ "$ZAMMAD_URL/api/v1/ticket_articles" \ - -d '{"ticket_id": , "body": "

Grund


✨unterstützt durch KI✨

", "content_type": "text/html", "type": "note", "internal": true}' + -d '{"ticket_id": , "body": "

/#user/profile/\" data-mention-user-id=\"\">Vorname Nachname, Grund


✨unterstützt durch KI✨

", "content_type": "text/html", "type": "note", "internal": true}' ``` -Every Zammad article this skill writes has `"internal": true` and ends with the italic AI marker after an empty line; send it as `text/html`, since plain text cannot render italics. +Every Zammad article this skill writes has `"internal": true` and ends with the italic AI marker after an empty line; send it as `text/html`, since plain text cannot render italics. Addressees go in as mention links (see `SKILL.md`); the note above shows the form. ## OKF