Files
agent-prod/skills/lead-radar/references/person.md
T

53 lines
3.3 KiB
Markdown
Raw Normal View History

2026-11-01 15:59:55 +01:00
# 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 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 |
2026-11-01 15:59:55 +01:00
## 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>
```