feat: add own skills
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
02e2797fbd
commit
ac6208717c
41 files changed
+4632
No files matched your search
@@ -0,0 +1,94 @@
|
||||
---
|
||||
name: lead-radar
|
||||
description: |
|
||||
Sascha's leadership radar: read the IT cockpit through one lens, turn the situation into
|
||||
numbered decision proposals, execute them in Basecamp/Zammad after one batch approval.
|
||||
Modes: tag (morning Lagebild, Zammad + 👥 IT), freitag (prepare the Friday close),
|
||||
meins (weekly review of Sascha's own 🔒 Meins to-dos), person <slug> (prepare a 1:1),
|
||||
portfolio (monthly review of Sascha's projects). Also answers "wem delegiere ich X"
|
||||
via person mode.
|
||||
Triggers: "Lagebild", "Freitags-Abschluss vorbereiten", "Wochenreview", "1:1 vorbereiten",
|
||||
"Portfolio-Review".
|
||||
compatibility: opencode, claude-code
|
||||
---
|
||||
|
||||
# lead-radar
|
||||
|
||||
Guiding question of every run: *What must Sascha decide now, and whom does he give it to?* One run = one mode → one Lagebild → one numbered proposal list → one batch approval → execution.
|
||||
|
||||
Invocation: `/lead-radar <tag|freitag|meins|person <slug>|portfolio>`. Without a mode, pick from the user's words via the trigger phrases above; still unclear → ask with the five modes as options.
|
||||
|
||||
## Sources of truth
|
||||
|
||||
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
|
||||
|
||||
An ID that fails: resolve it by name, carry on, and add the mismatch to the Drift block.
|
||||
|
||||
Load the `basecamp` skill before any Basecamp CLI call; check flags with `basecamp <cmd> --agent --help`, they evolve. For German text that colleagues read (comments, notes), follow `sascha-internal-communication-style`.
|
||||
|
||||
## Steps
|
||||
|
||||
### 1. Pull the data
|
||||
|
||||
From `/home/sascha.koenig/p/PM`:
|
||||
|
||||
```bash
|
||||
python3 tools/it-cockpit/cockpit.py --json --scope <mode> [--person <slug>]
|
||||
```
|
||||
|
||||
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).
|
||||
|
||||
**Done when** the JSON is on disk and you know which sources are blind.
|
||||
|
||||
### 2. Read the situation through the mode's lens
|
||||
|
||||
Open the mode's reference and follow it; it says which keys to read, how to judge them, and which proposals each finding yields:
|
||||
|
||||
| Mode | Reference | Persists |
|
||||
|---|---|---|
|
||||
| `tag` | [references/tag.md](references/tag.md) | nothing |
|
||||
| `freitag` | [references/freitag.md](references/freitag.md) | nothing |
|
||||
| `meins` | [references/meins.md](references/meins.md) | doc in 🔒 Meins → `Wochenreviews` |
|
||||
| `person <slug>` | [references/person.md](references/person.md) | nothing, by hard rule |
|
||||
| `portfolio` | [references/portfolio.md](references/portfolio.md) | doc in 🔒 Meins → `02 Projekte & Initiativen` |
|
||||
|
||||
**Done when** every item in the mode's buckets has either a proposal or a one-line reason why it needs none.
|
||||
|
||||
### 3. Present: Lagebild, proposals, drift
|
||||
|
||||
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.
|
||||
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?"
|
||||
|
||||
**Done when** the user has answered explicitly. Silence or a follow-up question is not approval; answer it and ask again.
|
||||
|
||||
### 4. Execute the approved items
|
||||
|
||||
Follow [references/execute.md](references/execute.md): one command per change, the short "why" comment on every changed object, read-back afterwards.
|
||||
|
||||
**Done when** every approved item is either verified in Basecamp/Zammad/OKF or reported as failed with the exact command and error.
|
||||
|
||||
### 5. Persist and report
|
||||
|
||||
For `meins` and `portfolio` write the document as the mode's reference describes, reflecting what was actually executed. Other modes write nothing.
|
||||
|
||||
Report in German: executed items with links, failed items with error, document URL (if any), open `Für dich:` points.
|
||||
|
||||
**Done when** the report is out and, for `meins`/`portfolio`, the document is readable in Basecamp.
|
||||
|
||||
## Guardrails
|
||||
|
||||
- Every write waits for the batch approval; the approval covers exactly the numbered items shown.
|
||||
- Proposals carry their reason; a bare "Termin verschieben" is incomplete.
|
||||
- OKF holds goals, context, decisions and links; task state lives in Basecamp (spec §3.2). OKF fixes go through the same approval and end with the `validate` skill on the bundle.
|
||||
- Process KPIs only: counts per list or per process, never per-person rankings.
|
||||
- Owner reminders belong to automation A3; the skill's output to colleagues is the comment on the object, nothing else.
|
||||
@@ -0,0 +1,51 @@
|
||||
# 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.
|
||||
|
||||
## Order per item
|
||||
|
||||
1. Make the change.
|
||||
2. Put the comment on the same object: one or two German sentences with the reason, ending in `(lead-radar, <Modus>, YYYY-MM-DD)`. Example: `Neuer Termin 06.11., Lieferant hat Rückmeldung für KW 45 zugesagt. (lead-radar, freitag, 2026-11-13)`.
|
||||
3. Read the object back and check the new value.
|
||||
|
||||
Work through the list in number order. A failing item does not stop the run: note command and error, go on, and report it at the end.
|
||||
|
||||
## Basecamp
|
||||
|
||||
Write mentions as plain names (no `@`), and leave `--notify` off: the comment is the trail, reminders belong to automation A3.
|
||||
|
||||
| Action | Command (check flags with `--agent --help`) |
|
||||
|---|---|
|
||||
| Change owner | `basecamp todos update <id> --assignee <person-id> --json` |
|
||||
| Set date | `basecamp todos update <id> --due YYYY-MM-DD --json` |
|
||||
| Comment | `basecamp comments create <id> - < <scratchpad-file>` (stdin keeps umlauts intact) |
|
||||
| Move to list (same project) | `basecamp todos position <id> --to 1 --list <list-id> --json` |
|
||||
| Complete | `basecamp todos complete <id> --json` |
|
||||
| Read back | `basecamp todos show <id> --json` |
|
||||
|
||||
**Parking:**
|
||||
|
||||
- Inside 🔒 Meins: move to the Meins backlog list (ID in `systems/basecamp.md`).
|
||||
- From 👥 IT or a project into 📥 Backlog / Ideenspeicher (another project; `position` cannot cross projects): create a to-do in 📥 Backlog with the original title, its context and a link to the original, then comment on the original with the link to the new item and complete it. Shown to the user as one proposal.
|
||||
|
||||
**Cards** (card tables, e.g. Azubi board): comment with `basecamp comments create <card-id>`; moving cards between columns is the card owner's job, so propose it as a `Für dich:` point.
|
||||
|
||||
## Zammad
|
||||
|
||||
Allowed: set owner, internal note. Requires `ZAMMAD_TOKEN`; base URL from `ZAMMAD_URL`, default as in `tools/it-cockpit/cockpit.py`. Without a token, list the Zammad items as `Für dich:` points with ticket link.
|
||||
|
||||
```bash
|
||||
# owner (owner_id = Zammad user id; resolve via GET /api/v1/users/search?query=<login>)
|
||||
curl -sf -X PUT -H "Authorization: Token token=$ZAMMAD_TOKEN" -H "Content-Type: application/json" \
|
||||
"$ZAMMAD_URL/api/v1/tickets/<id>" -d '{"owner_id": <uid>}'
|
||||
# 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": <id>, "body": "<Grund>", "type": "note", "internal": true}'
|
||||
```
|
||||
|
||||
Every Zammad article this skill writes has `"internal": true`.
|
||||
|
||||
## 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.
|
||||
@@ -0,0 +1,52 @@
|
||||
# Mode `freitag`: prepare the Friday close
|
||||
|
||||
When: before the Friday close (Fri 10:30, 15 min, whole team, chaired by Sascha). Lens: apply the 30-day rule, clear the waiting list, and leave Sascha with a cheat sheet of three priorities.
|
||||
|
||||
## Input (`--scope freitag`)
|
||||
|
||||
- `still_30d`: 👥 IT to-dos without a comment for 30 days.
|
||||
- `wartend_nachfassen`: "Wartet auf extern / Fachbereich" items whose follow-up date has been reached.
|
||||
- `regelverstoesse.ohne_owner`, `regelverstoesse.ohne_termin`.
|
||||
- `pro_person`: per person the open count, overdue count, and items due in the next 10 days. Use it **only** to check that next week's commitments fit around `abwesenheiten`; it never appears in the Lagebild as a table or comparison.
|
||||
- `abwesenheiten`: next 10 days.
|
||||
- `drift`: `liste_ausserhalb_regel` entries are Friday decisions by definition.
|
||||
|
||||
## Judgement
|
||||
|
||||
| Finding | Proposal (one of) |
|
||||
|---|---|
|
||||
| 30 days silent | **weiter**: new date + comment with the next step · **parken**: into 📥 Backlog (see `execute.md`) · **schließen**: complete + comment why. Pick the one the item's description and history support; when unclear, say "im Abschluss fragen" and propose a comment asking the owner |
|
||||
| Follow-up date reached | new follow-up date + comment with what is awaited from whom · or complete when the answer is visibly in |
|
||||
| No owner / no date | owner + date, labelled `Vorschlag` |
|
||||
| Due next week while owner is absent | new date or owner change, as a question for the close |
|
||||
| List outside the rule | `Für dich:` keep (Friday decision) or archive (Sascha does it himself) |
|
||||
|
||||
## Lagebild template
|
||||
|
||||
```md
|
||||
# Freitags-Abschluss – <TT.MM.JJJJ>
|
||||
|
||||
**Kurzfazit:** <2–3 Sätze>
|
||||
|
||||
## 30 Tage still → weiter / parken / schließen
|
||||
- <Titel · Owner · still seit N Tagen · Link> → Empfehlung
|
||||
|
||||
## Wartet auf extern – Nachfassen fällig
|
||||
- <Titel · wartet auf wen/was · Link> → Empfehlung
|
||||
|
||||
## Regelverstöße
|
||||
- <Titel · fehlt Owner/Termin · Link>
|
||||
|
||||
## Nächste Woche: Abwesenheiten
|
||||
- <Person · von–bis> (+ betroffene Termine, falls vorhanden)
|
||||
|
||||
## Spickzettel: drei Prioritäten für nächste Woche
|
||||
1. <Priorität · warum · wer>
|
||||
2. …
|
||||
3. …
|
||||
|
||||
## Beschlüsse im Abschluss
|
||||
- <Liste außerhalb der Regel, Punkte "im Abschluss fragen">
|
||||
```
|
||||
|
||||
The three priorities come from overdue and next-week items with the widest effect (blocks others, external deadline, security); each names one owner.
|
||||
@@ -0,0 +1,61 @@
|
||||
# Mode `meins`: weekly review of Sascha's own to-dos
|
||||
|
||||
When: weekly. Lens: Sascha's own to-dos in 🔒 Meins; a review with judgement and recommendations, not a list dump.
|
||||
|
||||
## Input
|
||||
|
||||
- `--scope meins` → `meins.listen` (open to-dos per list) and `meins.klassifikation` (`ueberfaellig`, `heute`, `diese_woche`, `still_30d`, `wartend_nachfassen`, `ohne_owner`, `ohne_termin`).
|
||||
- Last review: the newest document in folder `Wochenreviews` (`basecamp files list --in <meins-id> --vault <folder-id> --json`); its date bounds "Erledigt seit letztem Review". No folder or no document yet → use the last 7 days.
|
||||
- Completed to-dos: `basecamp todos list --in <meins-id> --completed --all --json`, keep those completed after that date.
|
||||
|
||||
## Classify every open to-do (exactly one class)
|
||||
|
||||
- `🔥 Diese Woche erledigen/entscheiden`: due now, strategically important, or blocking others
|
||||
- `⚠️ Überfällig`: due date passed
|
||||
- `⏳ Wartet auf Rückmeldung`: delegated, blocked, or needs another person (includes the Meins waiting list)
|
||||
- `🧹 Aufräumen`: unclear, duplicate, stale, or no longer relevant
|
||||
- `📦 Backlog`: valid but not for this week
|
||||
|
||||
## Score each 🔥, ⚠️ and ⏳ item
|
||||
|
||||
| Dimension | Values |
|
||||
|---|---|
|
||||
| Dringlichkeit | überfällig / diese Woche / später / ohne Termin |
|
||||
| Klarheit | nächster Schritt klar? Definition of Done vorhanden? |
|
||||
| Momentum | neu / 7+ Tage still / 30+ Tage still (`still_tage`) |
|
||||
| Ownership | Sascha / wartet auf jemanden / unklar |
|
||||
|
||||
The scores drive the recommendation per item: **do, defer, delegate, clarify, park, close**. Each recommendation that changes Basecamp becomes a numbered proposal (new date, move to the Meins backlog list, owner change for delegation, complete with comment, comment that rewrites an unclear item's next step).
|
||||
|
||||
## Review template (chat and document)
|
||||
|
||||
```md
|
||||
# Wochenreview To-dos – YYYY-MM-DD
|
||||
|
||||
## Kurzfazit
|
||||
[2–4 Sätze]
|
||||
|
||||
## Top 5 für diese Woche
|
||||
1. [Todo](link) — Warum jetzt / nächster Schritt
|
||||
|
||||
## Überfällig
|
||||
- [Todo](link) — Empfehlung: do / defer / delegate / clarify / close
|
||||
|
||||
## Wartet auf Rückmeldung
|
||||
- [Todo](link) — wartet auf [Person/Sache], nächster Nachfasspunkt
|
||||
|
||||
## Aufräumen
|
||||
- [Todo](link) — Grund und empfohlene Aktion
|
||||
|
||||
## Erledigt seit letztem Review
|
||||
- [Todo](link)
|
||||
|
||||
## Vorgeschlagene Änderungen
|
||||
1. [nummeriert wie in der Freigabeliste; im Dokument mit Status ✅ umgesetzt / ❌ abgewählt / ⚠️ fehlgeschlagen]
|
||||
```
|
||||
|
||||
## Document
|
||||
|
||||
After execution (step 5 of `SKILL.md`), save the review as document `YYYY-MM-DD – Wochenreview` in 🔒 Meins → folder `Wochenreviews`, with the change list showing what was actually done. Use `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.
|
||||
|
||||
**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.
|
||||
@@ -0,0 +1,53 @@
|
||||
# Mode `person <slug>`: prepare a 1:1
|
||||
|
||||
When: before a 1:1 with one team member. Lens: what this person carries, what they need from Sascha, and what Sascha could hand to them. The output is a conversation guide for Sascha, written so the person could read it over his shoulder.
|
||||
|
||||
## Boundary (spec §4.1, hard)
|
||||
|
||||
The lens describes **one person's work items and needs in their own terms**: what is open, what is stuck, what they are waiting for, what Sascha can unblock or delegate. Every statement points at an item with a link.
|
||||
|
||||
Guardrail: the output contains no comparison between people, no ranking or score, no judgement of performance, of commenting behaviour, or of lead times per person. Process KPIs live in the monthly KPI review, at process level. **Nothing is stored**: no document, no notes file, no OKF edit about the person (profile maintenance belongs to `lead-profile`). The scratchpad JSON is the only artefact and stays there.
|
||||
|
||||
## Input (`--scope person --person <slug>`)
|
||||
|
||||
`<slug>` is a file name in `.okf/organization/` without `.md`. A wrong slug makes the cockpit exit with the list of valid slugs: offer them and ask.
|
||||
|
||||
- `person`: name, Basecamp ID, email, profile path. Read the profile itself for role, skills and responsibilities.
|
||||
- `basecamp.offen` across all projects, with `ueberfaellig`, `diese_woche`, `still_30d`.
|
||||
- `braucht_von_sascha`: "Wartet auf extern / Fachbereich" items of the person that name Sascha.
|
||||
- `board_rueckfragen` (optional; present once the cockpit provides it): cards in "Rückfrage / Benötige Admin-Rechte"-type columns of the Azubi card table, each `{title, column, url, still_tage}`. Absent key → skip that section silently.
|
||||
- `zammad.offen`, `zammad.sla_4h` (blind without `ZAMMAD_TOKEN`).
|
||||
- `abwesenheiten`: the person's absences in the next 10 days.
|
||||
- Delegation candidates: Sascha's own open to-dos, `basecamp todos list --assignee <sascha-id> --all-projects --json` (Sascha's ID from his profile).
|
||||
|
||||
## Judgement
|
||||
|
||||
| Finding | Proposal |
|
||||
|---|---|
|
||||
| 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 |
|
||||
|
||||
## Lagebild template
|
||||
|
||||
```md
|
||||
# 1:1 <Vorname> – Vorbereitung <TT.MM.JJJJ>
|
||||
|
||||
**Kurzfazit:** <2–3 Sätze: was läuft, wo es hakt, was du mitbringen solltest>
|
||||
|
||||
## Braucht von dir
|
||||
- <Item · seit N Tagen · Link> → was du klärst
|
||||
|
||||
## Offen bei <Vorname>
|
||||
<überfällig · diese Woche · 30 Tage still · Zammad (SLA) – je Zeile Titel · Projekt · Termin · Link>
|
||||
|
||||
## Abwesenheiten (10 Tage)
|
||||
- <von–bis>
|
||||
|
||||
## Delegationsideen
|
||||
- <dein To-do · passt zu Rolle/Skill X · Link>
|
||||
|
||||
## Gesprächsfragen
|
||||
1. <offene Frage zu einem konkreten Item>
|
||||
```
|
||||
@@ -0,0 +1,63 @@
|
||||
# Mode `portfolio`: monthly portfolio review
|
||||
|
||||
When: monthly (first run December). Lens: every project Sascha holds open to-dos in. Per project: is there an owner, a goal, a next milestone? Then: keep, hand over, park, or cut.
|
||||
|
||||
## Input (`--scope portfolio`)
|
||||
|
||||
`portfolio.projekte[]`: `project_id`, `project`, `saschas_offene`, `ueberfaellig`, `ohne_termin`, `still_30d`, `okf_konzepte` (OKF project files linking to that Basecamp project), `todos` (Sascha's open to-dos there).
|
||||
|
||||
Sort the rows first:
|
||||
|
||||
- **Initiatives** (time-bounded projects): the review subject.
|
||||
- **Standing spaces** (👥 team spaces, 🔒 Meins, 📥 Backlog, 🔁 coordination, templates; archetypes in `systems/basecamp.md`): no owner/goal/milestone check; list them in one block with their counts only.
|
||||
|
||||
`okf_konzepte` is matched by link, so a concept may only mention the project. Open each one and keep it as the project's concept only if it is about that project.
|
||||
|
||||
## Per initiative: three checks
|
||||
|
||||
| Check | Source | Missing → |
|
||||
|---|---|---|
|
||||
| Owner | OKF concept (owner/Verantwortlich); else Basecamp project description | `Owner fehlt` |
|
||||
| Ziel | OKF concept (goal/purpose) | `Ziel fehlt` → OKF stub proposal or `Für dich:` |
|
||||
| Nächster Meilenstein | Basecamp: next dated to-do or schedule entry in the project (`basecamp todos list --in <id> --json`, `basecamp schedule …`) | `Meilenstein fehlt` |
|
||||
|
||||
## Recommendation (one per initiative)
|
||||
|
||||
- **weiterführen**: all three present and Sascha's to-dos move; proposals only for overdue/undated items (date, comment).
|
||||
- **abgeben**: Sascha is not the natural owner. Proposals: owner change of Sascha's to-dos to the named successor + comment with context. The project-level handover itself is a `Für dich:` point.
|
||||
- **parken**: no momentum and no deadline. Proposals: Sascha's to-dos to the project's backlog or to 📥 Backlog (see `execute.md`), each with comment.
|
||||
- **streichen**: goal obsolete. Proposals: complete Sascha's to-dos with a comment naming the decision. Archiving the project is a `Für dich:` point.
|
||||
|
||||
## OKF: task state out, links in (spec §3.2)
|
||||
|
||||
For every OKF concept of an initiative, find task state: to-do lists, "nächster Schritt bis …", status-of-work lines, dated action items. Propose one numbered OKF edit per file that replaces that state with a link to the Basecamp project or list, keeping goals, context and decisions. Show a short before/after excerpt in the proposal. Also propose missing `owner`/goal lines where the review established them.
|
||||
|
||||
## Lagebild template (chat and document)
|
||||
|
||||
```md
|
||||
# Portfolio-Review – YYYY-MM-DD
|
||||
|
||||
## Kurzfazit
|
||||
[2–4 Sätze: wie viele Initiativen, wo Sascha zu viel hält, was abgegeben/geparkt/gestrichen werden soll]
|
||||
|
||||
## Initiativen
|
||||
| Projekt | Owner | Ziel | Nächster Meilenstein | Deine offenen | Empfehlung |
|
||||
|---|---|---|---|---|---|
|
||||
| [Name](link) | … / fehlt | ✅ / fehlt | TT.MM. / fehlt | N (davon M überfällig) | weiterführen / abgeben an X / parken / streichen |
|
||||
|
||||
## Begründungen
|
||||
- **Projekt**: warum diese Empfehlung
|
||||
|
||||
## Ständige Bereiche
|
||||
- <👥 IT, 🔒 Meins … mit Anzahl deiner offenen>
|
||||
|
||||
## OKF: Aufgabenstand durch Links ersetzt
|
||||
- <Datei → was ersetzt wird>
|
||||
|
||||
## Vorgeschlagene Änderungen
|
||||
1. [nummeriert wie in der Freigabeliste; im Dokument mit Status ✅ / ❌ / ⚠️]
|
||||
```
|
||||
|
||||
## Document
|
||||
|
||||
After execution, save the review as document `YYYY-MM-DD – Portfolio-Review` in 🔒 Meins → folder `02 Projekte & Initiativen` (IDs in `systems/basecamp.md`) with `basecamp files documents create "<Titel>" "$(cat <scratchpad-file>)" --in <meins-id> --vault <folder-id> --no-subscribe --json`. Read it back and keep its URL.
|
||||
@@ -0,0 +1,48 @@
|
||||
# Mode `tag`: morning Lagebild
|
||||
|
||||
When: in the morning after the cockpit, before the 10-minute briefing (led by Mexx; Sascha attends). Lens: what needs an owner or a decision **today**.
|
||||
|
||||
## Input (`--scope tag`)
|
||||
|
||||
- `zammad`: `ohne_owner`, `sla_4h`, `prio_ohne_antwort`, `absprache_ohne_datum`, `wiedervorlage_faellig` (`offen` is context only). `null` plus an `errors` entry = Zammad blind.
|
||||
- `basecamp_it`: `ueberfaellig`, `heute`, `diese_woche`, `wartend_nachfassen`, `ohne_owner`, `ohne_termin`, `still_30d`.
|
||||
- `abwesenheiten`: who is out today and in the next 10 days.
|
||||
|
||||
Read the OKF profiles of the team for role and skills before proposing an owner.
|
||||
|
||||
## Judgement
|
||||
|
||||
| Finding | Proposal |
|
||||
|---|---|
|
||||
| Ticket without owner | owner from role/skills in the profiles, someone present today (check `abwesenheiten`) + internal note |
|
||||
| SLA in < 4 h, prio without answer for 24 h | owner confirm or change + internal note; the customer reply itself stays with the owner |
|
||||
| "Absprache getroffen" without date, Wiedervorlage due | internal note asking the owner for the next date; owner change only if the owner is absent |
|
||||
| 👥 IT overdue | comment asking for a new date per rule 1 (owner sets the date); owner change only if the owner is absent beyond the due date |
|
||||
| 👥 IT due today | none unless the owner is absent today → owner change or new date |
|
||||
| Rule violation (no owner / no date) | set owner and date, labelled `Vorschlag` |
|
||||
| Wartet auf extern, follow-up date reached | new follow-up date + comment with what is being waited for |
|
||||
| `still_30d` | leave for Friday; mention the count only |
|
||||
|
||||
An absent owner is the strongest reason for an owner change; everything else first asks the owner via a comment.
|
||||
|
||||
## Lagebild template
|
||||
|
||||
```md
|
||||
# Lagebild IT – <TT.MM.JJJJ>
|
||||
|
||||
**Kurzfazit:** <2–3 Sätze: was heute brennt, was entschieden werden muss>
|
||||
|
||||
## Zammad
|
||||
<ohne Owner · SLA gefährdet · Prio ohne Antwort · Wiedervorlage – je Zeile: #Nr Titel · Owner · Alter · Link>
|
||||
|
||||
## 👥 IT
|
||||
<überfällig · heute · Nachfasser · Regelverstöße – je Zeile: Titel · Owner · Termin · Liste · Link>
|
||||
|
||||
## Abwesend
|
||||
<heute / nächste 10 Tage>
|
||||
|
||||
## Fürs Briefing (max. 3)
|
||||
1. <Punkt, den Sascha im Briefing anspricht>
|
||||
```
|
||||
|
||||
Empty sections collapse to one line ("Zammad: nichts ohne Owner, kein SLA-Risiko").
|
||||
Reference in new issue
Block a user