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:
1 parent
16dac49044
commit
06acee80c2
11 files changed
+75
-60
No files matched your search
@@ -23,10 +23,10 @@ Invocation: `/lead-radar <tag|freitag|ich|person <slug>|portfolio>`. Without a m
|
||||
|
||||
Read before acting; these hold the facts, this skill holds only behaviour:
|
||||
|
||||
- `/home/sascha.koenig/p/PM/.okf/processes/it-basecamp-regeln.md`: task rules, the six 👥 IT lists, 30-day rule, Zammad boundary, **approval protocol** (binding for every write)
|
||||
- `/home/sascha.koenig/p/PM/.okf/systems/basecamp.md`: project, list and folder IDs
|
||||
- `/home/sascha.koenig/p/PM/.okf/organization/*.md`: people (role, skills, Basecamp person ID, Zammad login)
|
||||
- `/home/sascha.koenig/p/PM/tools/it-cockpit/README.md`: the data layer and what each scope returns
|
||||
- `/home/sascha.koenig/ap/PM/.okf/processes/it-basecamp-regeln.md`: task rules, the six 👥 IT lists, 30-day rule, Zammad boundary, **approval protocol** (binding for every write)
|
||||
- `/home/sascha.koenig/ap/PM/.okf/systems/basecamp.md`: project, list and folder IDs
|
||||
- `/home/sascha.koenig/ap/PM/.okf/organization/*.md`: people (role, skills, Basecamp person ID, Zammad login)
|
||||
- `/home/sascha.koenig/ap/PM/tools/it-cockpit/README.md`: the data layer and what each scope returns
|
||||
|
||||
An ID that fails: resolve it by name, carry on, and add the mismatch to the Drift block.
|
||||
|
||||
@@ -44,20 +44,20 @@ 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:<person-id>)`, 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.
|
||||
- Basecamp: `[@Vorname Nachname](person:<person-id>)`, ID from `.okf/organization/` or, for colleagues outside the IT team, from the table "Basecamp-Personen-IDs häufiger Gegenüber" in `.okf/systems/basecamp.md`; fallback `basecamp people pingable --jq '.data[] | select(.name == "…")'`. A person found only via the fallback becomes a Drift proposal (add the row to that table). Milan Urban's Basecamp display name is `milan`; mention him with his full name anyway. 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`): `<a href="<zammad-url>/#user/profile/<uid>" data-mention-user-id="<uid>">Vorname Nachname</a>`, uid via `GET /api/v1/users/search?query=<login>`. 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
|
||||
|
||||
From `/home/sascha.koenig/p/PM`:
|
||||
From `/home/sascha.koenig/ap/PM`:
|
||||
|
||||
```bash
|
||||
python3 tools/it-cockpit/cockpit.py --json --scope <mode> [--person <slug>]
|
||||
```
|
||||
|
||||
For `ich` add `--dry-run`: the state is written only at the very end of the run, after execution (see `references/ich.md`). A run takes 20–90 s. Save the JSON to the scratchpad and work from that file. Every output carries `drift` and `errors`; an entry under `errors` (e.g. Zammad without `ZAMMAD_TOKEN`) means that source is blind for this run: say so in one line at the top of the Lagebild and continue with the rest. Use live `basecamp` calls only for detail questions the cockpit does not answer (comments under an item, a card's history).
|
||||
For `ich` add `--dry-run`: the state is written only at the very end of the run, after execution (see `references/ich.md`). A cockpit run takes 20–90 s; a full `ich` run with Sally and execution takes 30–60 minutes of tool time, say so when the user asks for a quick look. Save the JSON to the scratchpad and work from that file. Every output carries `drift` and `errors`; an entry under `errors` (e.g. Zammad without `ZAMMAD_TOKEN`) means that source is blind for this run: say so in one line at the top of the Lagebild and continue with the rest. Use live `basecamp` calls only for detail questions the cockpit does not answer (comments under an item, a card's history).
|
||||
|
||||
**Done when** the JSON is on disk and you know which sources are blind.
|
||||
|
||||
@@ -95,7 +95,7 @@ Follow [references/execute.md](references/execute.md): one command per change, t
|
||||
|
||||
### 5. Persist and report
|
||||
|
||||
For `ich` and `portfolio` write the document as the mode's reference describes, reflecting what was actually executed. Other modes write nothing.
|
||||
For `ich` and `portfolio` write the document as the mode's reference describes, reflecting what was actually executed, then write the mode's state (`ich`: second cockpit run without `--dry-run`). Other modes write nothing. Anything the run created that the OKF must know (folder IDs, person IDs, list IDs) is proposed under ⚠️ Drift in step 3 and written in step 4; a run never leaves an ID only in a Basecamp document.
|
||||
|
||||
Report in German: executed items with links, failed items with error, document URL (if any), open `Für dich:` points.
|
||||
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
# Executing approved proposals
|
||||
|
||||
Reached from step 4 of `SKILL.md`. The approval protocol in `/home/sascha.koenig/p/PM/.okf/processes/it-basecamp-regeln.md` is the rule; this file is the mechanics.
|
||||
Reached from step 4 of `SKILL.md`. The approval protocol in `/home/sascha.koenig/ap/PM/.okf/processes/it-basecamp-regeln.md` is the rule; this file is the mechanics.
|
||||
|
||||
## Order per item
|
||||
|
||||
@@ -29,8 +29,11 @@ Mention the addressees as described under **Mentions** in `SKILL.md` (`[@Name](p
|
||||
| Complete | `basecamp todos complete <id> --json` |
|
||||
| Read back | `basecamp todos show <id> --json` |
|
||||
| Create to-do (own commitment, mode `ich` only) | `basecamp todos create "<Titel>" --in <project-id> --list <list-id> --assignee <sascha-id> [--due YYYY-MM-DD] --description "<Kontextsatz + Sally-Link>" --json` |
|
||||
| Move to another project | no API call exists; create in the target project (`todos create … --in <target> [--todoset <id>] --list <list-id>`) with the original title, a context sentence and the original's URL, comment on the original with the new URL, complete the original |
|
||||
|
||||
Creating a to-do is allowed only in mode `ich`, only for Sascha's own commitment from a Sally recording, owner always Sascha. The description carries one context sentence and the link to the recording; the new to-do gets the same why-comment as every change.
|
||||
Creating a to-do is allowed in mode `ich` for Sascha's own commitment from a Sally recording (owner always Sascha), and in any mode as the second half of a project move or of parking (rule 5 of the approval protocol). The description carries one context sentence and the link to the recording or the original; the new to-do gets the same why-comment as every change. On a project move the owner may change when the approval says so; then the new owner is mentioned in the comment on the new to-do, and the requester is mentioned in the comment on the original.
|
||||
|
||||
Projects with several to-do sets (🔁 Übergaben & Koordination, [IT] - Data Hub Analytics v1) need `--todoset <id>` on `todolists list` and `todos create`; IDs in `systems/basecamp.md`. The person must be a member of the target project (`basecamp people list --in <id>`), otherwise the move is a `Für dich:` point.
|
||||
|
||||
**Parking:**
|
||||
|
||||
@@ -58,4 +61,4 @@ Every Zammad article this skill writes has `"internal": true` and ends with the
|
||||
|
||||
## OKF
|
||||
|
||||
Edit the concept files under `/home/sascha.koenig/p/PM/.okf/` as approved, set `generated.at` to today, then run the `validate` skill on the bundle. Git stays with Sascha: report the changed paths.
|
||||
Edit the concept files under `/home/sascha.koenig/ap/PM/.okf/` as approved, set `generated.at` to today, then run the `validate` skill on the bundle. Git stays with Sascha: report the changed paths.
|
||||
@@ -1,52 +1,62 @@
|
||||
# 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-11-05-lead-radar-ich.md` §1): A commitments kept (Termintreue), B too much held personally, C open loops from meetings, D focus. Then a look back at the numbers.
|
||||
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`)
|
||||
## 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). Keys under `ich`:
|
||||
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`), `erledigt`, `puenktlich`, `termintreue`, `delegiert`, `sonstig_weg`, `neu`, `vorheriger_lauf`. `vorheriger_lauf == null` is the first run: comparison fields are `null`, say "Vergleich ab dem zweiten Lauf".
|
||||
- `klassifikation`: `ueberfaellig`, `heute`, `diese_woche`, `still_30d`, `ohne_termin` (Daily Quests excluded).
|
||||
- `listen_je_projekt`: every open to-do, grouped project → list.
|
||||
- `erledigt`: completed since the last run, each with `completed_at` (null when Basecamp gave no event).
|
||||
- `verlauf`: the last four metric rows, oldest first.
|
||||
- Top level: `abwesenheiten` (next 10 days), `drift`, `errors`.
|
||||
- `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 the OKF profiles in `/home/sascha.koenig/p/PM/.okf/organization/` before section 3, and `processes/meeting-runden.md` before section 1.
|
||||
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`: the last 7 days (back to `vorheriger_lauf` when that is longer ago), Sascha as participant. Keep recordings with `sallyStatus = transcriptionAndSummarizationCompleted`; list the others in one line as "noch nicht ausgewertet".
|
||||
2. Per recording: `list_tasks` filtered to tasks assigned to Sascha, plus follow-ups from `get_summary` that name Sascha.
|
||||
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`), owner Sascha, date from the meeting or marked `Vorschlag`, description = one context sentence + link to the Sally recording.
|
||||
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 `kennzahlen.mehrfach_verschoben` exactly one recommendation:
|
||||
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 the person is not absent in the next 10 days (`abwesenheiten`). 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?`.
|
||||
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). 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.
|
||||
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
|
||||
|
||||
@@ -58,11 +68,13 @@ Table of this run's `kennzahlen` next to `verlauf` (up to four earlier runs), th
|
||||
# Wochenreview – YYYY-MM-DD
|
||||
|
||||
## Kurzfazit
|
||||
[2–4 Sätze]
|
||||
[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
|
||||
|
||||
@@ -73,10 +85,10 @@ Table of this run's `kennzahlen` next to `verlauf` (up to four earlier runs), th
|
||||
- [To-do](link) → Vorname (Rolle) — Vorschlag Nr. N
|
||||
|
||||
## Aufräumen
|
||||
- [To-do](link) — parken / clarify / close
|
||||
- [To-do](link) — parken / clarify / close / Umzug nach Projekt X
|
||||
|
||||
## Erledigt seit letztem Review
|
||||
- [To-do](link) · pünktlich / zu spät
|
||||
- [To-do](link) · pünktlich / zu spät / ohne Zeitstempel
|
||||
|
||||
## Kennzahlen
|
||||
| | heute | −1 | −2 | −3 | −4 |
|
||||
@@ -84,6 +96,7 @@ Table of this run's `kennzahlen` next to `verlauf` (up to four earlier runs), th
|
||||
| offen | | | | | |
|
||||
| ohne Termin | | | | | |
|
||||
| überfällig | | | | | |
|
||||
| still ≥ 30 d | | | | | |
|
||||
| Termintreue | | | | | |
|
||||
| verschoben / ≥3× | | | | | |
|
||||
| delegiert | | | | | |
|
||||
@@ -99,7 +112,6 @@ Table of this run's `kennzahlen` next to `verlauf` (up to four earlier runs), th
|
||||
|
||||
After execution (step 4 of `SKILL.md`):
|
||||
|
||||
1. Save the review as document `YYYY-MM-DD – Wochenreview` in 🔒 Meins → folder `Wochenreviews` 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 and keep its URL. 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 `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.
|
||||
|
||||
**First run:** the folder `Wochenreviews` does not exist yet (`systems/basecamp.md` says so). Add one numbered proposal "Ordner `Wochenreviews` in 🔒 Meins anlegen und ID in `systems/basecamp.md` eintragen"; after approval create it with `basecamp files folders create Wochenreviews --in <meins-id> --json` and replace the placeholder in the ID table with the new ID.
|
||||
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.
|
||||
@@ -27,7 +27,7 @@ Guardrail: the output contains no comparison between people, no ranking or score
|
||||
| Something the person needs from Sascha (Rückfrage, admin rights, Fachbereich answer) | Sascha's answer as a comment on the item/card, drafted for him to confirm; or a `Für dich:` point when it needs action outside the allowed set (granting rights) |
|
||||
| Overdue or 30 days silent | a question for the 1:1 ("Was brauchst du, um X abzuschließen?"); a Basecamp change only if the person already said so in a comment |
|
||||
| Absence collides with a due date | new date as a 1:1 question |
|
||||
| Sascha's to-do matching the person's role/skills, not colliding with absences | delegation proposal: owner change + comment with context and definition of done |
|
||||
| Sascha's to-do matching the person's role/skills, not on the **Nicht delegierbar** list in `sascha-koenig.md`, due date not inside an absence | delegation proposal: owner change + comment with context and definition of done; a stub profile without skills allows role-level matches only, say so |
|
||||
|
||||
## Lagebild template
|
||||
|
||||
|
||||
Reference in new issue
Block a user