--- name: lead-profile description: "Maintains OKF Person profiles of colleagues in /home/sascha.koenig/p/PM/.okf/organization/: create (minimal stub or full profile via interview wizard), verify, link, refresh, data-subject requests, offboarding. Use when: new colleague / onboarding profile, quarterly or stale profile review, upgrading a minimal stub, Auskunfts- or Löschanfrage, colleague leaves. Trigger: 'Mitarbeiterprofil', 'Kollegen-Profil', 'Profil für NN anlegen', 'Profil aktualisieren', 'Skill-Matrix für NN', 'Belbin-Rolle für NN'." compatibility: opencode, claude-code --- # lead-profile Maintains OKF Person profiles in `/home/sascha.koenig/p/PM/.okf/organization/` (fixed path, called `ORG/` below; bundle root `/home/sascha.koenig/p/PM/.okf/`). Profiles serve project planning, delegation and personnel development — never performance assessment. **Scope: profile maintenance only.** Questions like "wer hat Kapazität", "wem delegiere ich", "wer kennt sich aus mit X" or team composition belong to `lead-radar`, which reads these profiles. This skill writes them. Skill text is English; everything written into profiles and all messages to the user are German. ## Principles 1. **Job-relevant only.** No private data, no performance ratings, no salary. See [references/gdpr-de.md](references/gdpr-de.md). 2. **Self-report over outside rating.** Colleagues maintain their skills; the manager verifies. 3. **Fresh.** Every full profile has `stale_after` (180 days); review is due after that. 4. **Linked, not duplicated.** Project membership links to `../projects/`, never copied. 5. **Department-agnostic.** Examples are IT; the schema fits every department. ## Two profile levels | Level | Allowed when | Content | Frontmatter | |---|---|---|---| | **Minimal stub** | always, no privacy notice needed (organisational master data) | Name, role, e-mail, Basecamp-Person-ID, Zammad-Login, manager, department. Nothing else | `consent.notice_given_at: null`, `consent.scope: stammdaten`, tag `minimal-stub`, `sensitivity: internal` | | **Full profile** | only after the privacy notice was given (date in `consent.notice_given_at`) | everything in [assets/person-template.md](assets/person-template.md) | `sensitivity: confidential`, `stale_after`, `verified` | Every field beyond the stub's list requires the notice. Upgrading a stub to a full profile is an explicit operation (see *upgrade*), never a side effect of an edit. ## Identity fields (both levels, required) The IT cockpit parses these two lines, so keep this exact form: ``` - **Basecamp-Person-ID**: `52087611` - **Zammad-Login**: `vorname.nachname@azintec.com` ``` ID as a backticked number. Zammad-Login backticked, or the plain word `offen` when unknown. Resolve the Basecamp ID via `basecamp people list --in ` (project IDs in `/home/sascha.koenig/p/PM/.okf/systems/basecamp.md`) or the auto-enrichment report. ## Operations ### stub — create a minimal stub 1. Copy [assets/stub-template.md](assets/stub-template.md) to `ORG/-.md`. 2. Fill only the stub fields, each fact with a footnote source. Example: `ORG/maximilian-radtke.md`. 3. Run *link*, then *validate*. ### create — full profile via interview wizard Starts on "Erstelle Profil für [Name]", "Profil-Interview mit [Name]", "Profile-Wizard für [Name]", "Mitarbeiterprofil anlegen: [Name]". An existing profile goes to *refresh* or *upgrade* instead; a plain skill-level question is answered directly without the wizard. Load [references/interview-guide.md](references/interview-guide.md) and work through it phase by phase, **one question per message**. Present multiple-choice questions (skill levels, Belbin, availability) as numbered options the user answers by number; a harness choice tool may be used if available. ``` Phase 0 Pre-flight → privacy notice given? (no → stop; offer a stub instead) Phase 1 Auto-enrichment → bash scripts/auto-enrich.sh "" Phase 2 Identity → title, location, tenure, manager, e-mail, Basecamp-Person-ID, Zammad-Login Phase 3 Background → education, stations, certificates Phase 4 Skills assessment → 5–15 questions with behavioural anchors Phase 5 Team profile → optional (Belbin, CliftonStrengths, working style) Phase 6 Capacity → availability, projects, engagement type Phase 7 Growth → skills, roles, mentoring Phase 8 Draft review → show draft, user approval Phase 9 Verify plan → checklist, next steps ``` Filling the file: copy [assets/person-template.md](assets/person-template.md) to `ORG/-.md`; frontmatter `title`, `description`, `tags`, `generated.at` (today), `stale_after` (today + 180 days), `consent.notice_given_at` (notice date). Start the skills matrix with 3–5 core skills. Belbin/CliftonStrengths only when already known. `status: draft` until *verify*. **Hard gates.** The profile file is written only after the user approved the draft (Phase 8). Belbin roles and CliftonStrengths come only from the user or a test, never guessed. A skill level ≥3 needs evidence (ticket, certificate, commit), otherwise level ≤2. Ask only job-relevant fields (performance, salary etc. are forbidden, Option A). One question per message. Phase 0 must pass before anything beyond stub data is collected. **Wizard resources** | Resource | When | |---|---| | [scripts/auto-enrich.sh](scripts/auto-enrich.sh) | Phase 1, run once | | [references/interview-guide.md](references/interview-guide.md) | before wizard start | | [references/skill-anchors-cheatsheet.md](references/skill-anchors-cheatsheet.md) | Phase 4, anchors for the top-10 IT skills | | [references/competence-catalog-it.md](references/competence-catalog-it.md) | Phase 4, IT | | [references/competence-catalog-template.md](references/competence-catalog-template.md) | Phase 4, non-IT | | [references/gdpr-de.md](references/gdpr-de.md) | Phase 0, privacy notice template | **Auto-enrichment sources** (only sources every AZ department head can reach): Basecamp full-text search + person record from creator fields; the OKF bundle at `/home/sascha.koenig/p/PM/.okf`; NixOS user configs (optional, IT-only, `$NIX_DIR`). Deliberately excluded: the private `m3ta-brain` vault and agent session logs. To skip NixOS: `NIX_DIR=/dev/null`. ### upgrade — stub to full profile Explicit request only ("Profil für NN ausbauen"). Run the wizard from Phase 0 against the existing stub: privacy notice date required. Then set `consent.notice_given_at`, remove `consent.scope: stammdaten` and the `minimal-stub` tag, set `sensitivity: confidential`, add `stale_after` and `verified: []`, replace the stub notice with the full template sections. Identity fields stay as they are. ### verify — review 1. The colleague reads the draft and adds/corrects (job-relevant skills only). 2. The manager confirms skill levels with concrete evidence (project, certificate, ticket). 3. Fill the `verified` array: `- by: "human:", at: "YYYY-MM-DD"`. 4. Set `status: stable`. 5. Add to `/home/sascha.koenig/p/PM/.okf/log.md`: `YYYY-MM-DD: Profil angelegt/aktualisiert`. ### link — connect 1. **Projects**: in each linked `../projects/.md`, check the person appears in the team or DRI field; add if missing. 2. **Decisions**: link `../decisions/.md` where the person signed off. 3. **Department**: add to the member list in `../organization/.md` where one exists. ### refresh — maintain 1. **Triggers**: `stale_after` reached, project end, role change, new certification, quarterly review. 2. The colleague updates skill levels and `generated.at`. 3. The manager re-verifies: new entry in `verified`. 4. Move `stale_after` to today + 180 days. 5. Update `log.md`. ### dsar — data-subject rights Auskunft (Art. 15), Berichtigung (Art. 16), Löschung (Art. 17) etc.: follow the DSAR workflow in [references/gdpr-de.md](references/gdpr-de.md). Erasure rewrites git history (`git filter-repo`, force push): present the exact commands and run them only after the user's explicit go. ### offboard — colleague leaves 1. Set `stale_after` to exit date + 6 months (retention limit of the privacy notice). 2. Remove the person from team/DRI fields in active `../projects/` (history entries stay) and note the exit date in the profile's identity section. 3. Add to `log.md`. 4. When `stale_after` is reached: delete the profile and its links per the erasure workflow in *dsar*. ## Field catalogue (full profile) Template with all fields: [assets/person-template.md](assets/person-template.md). | Block | Fields | Required? | |---|---|---| | **Frontmatter** | `type: Person`, `title`, `description`, `tags`, `status`, `generated`, `verified`, `stale_after`, `consent` | type/status/generated/consent yes | | **Identity** | title/role, e-mail, Basecamp-Person-ID, Zammad-Login, manager, department, location, timezone, tenure | yes | | **Background** | career, certifications | yes (may be "k.A.") | | **Skills matrix** | technical, domain, soft skills, each level 0–5 | yes (at least 3 skills) | | **T-shape** | depth (specialist), breadth (generalist) | recommended | | **Team profile** | Belbin (primary/secondary), CliftonStrengths top 5, working-style notes | optional | | **Current capacity** | availability %, active projects, engagement preference | yes | | **Growth plan** | skills to develop, roles of interest, mentoring | yes | | **Project history** | excerpt, with links | recommended | | **Sources / evidence** | footnotes for specific claims | for assessment claims | ## Frameworks | Framework | Required? | When | Reference | |---|---|---|---| | **Skills matrix 0–5** | yes | always, core of every profile | [references/framework-skills-matrix.md](references/framework-skills-matrix.md) | | **Belbin (9 roles)** | optional | team size 4+, when staffing is due | [references/framework-belbin.md](references/framework-belbin.md) | | **CliftonStrengths** | optional | only if the colleague took the Gallup test | [references/framework-cliftonstrengths.md](references/framework-cliftonstrengths.md) | | **T-shape** | recommended | specialist vs generalist | [references/framework-t-shape.md](references/framework-t-shape.md) | ## GDPR duties (short form) Full legal basis and templates: [references/gdpr-de.md](references/gdpr-de.md). Hard rules: 1. **Legal basis**: § 26 Abs. 1 BDSG + Art. 6 Abs. 1b DSGVO. No consent needed for job-relevant data. 2. **Data minimisation**: job-relevant fields only. Private life, family, hobbies, union membership → forbidden without voluntary consent. 3. **Never**: performance ratings, 9-box, potential assessments, salary, disciplinary measures, health/sick-leave data. These never go into a profile of this skill. 4. **Privacy notice** before any full profile (date in `consent.notice_given_at`). Minimal stubs hold master data only and need none. 5. **Staleness**: `stale_after` required on full profiles; review or deletion after 180 days at the latest. 6. **Private repo only.** Never push to a public remote. 7. **No AI scores** from non-job data (social scoring, Art. 5 KI-VO). ## Own competence catalogues (non-IT departments) IT example: [references/competence-catalog-it.md](references/competence-catalog-it.md). For sales, HR, production, finance etc.: 1. Define **3–7 competence families**. 2. Name **3–10 concrete skills** per family. 3. Write **level-3 anchors** ("kann selbstständig …"). 4. Write **level-5 anchors** ("setzt Standards, coacht andere"). Template and examples: [references/competence-catalog-template.md](references/competence-catalog-template.md). ## Validate & finish 1. Run OKF validation via the `validate` skill on `/home/sascha.koenig/p/PM/.okf` (strict). Fix every `ERROR` (§11); `WARN` is soft. 2. Parse the frontmatter: `python3 -c "import yaml; yaml.safe_load(open('FILE.md').read().split('---')[1])"`. 3. Check the identity lines match the cockpit form above. 4. Commit only when the user asks: `generated.by` set, message `add: person profile `, private repo only. ## References | File | When | |---|---| | [references/framework-skills-matrix.md](references/framework-skills-matrix.md) | before any skill rating; when unsure about a level | | [references/framework-belbin.md](references/framework-belbin.md) | team-role profiling | | [references/framework-cliftonstrengths.md](references/framework-cliftonstrengths.md) | colleague presents CliftonStrengths results | | [references/framework-t-shape.md](references/framework-t-shape.md) | specialist-vs-generalist career planning | | [references/gdpr-de.md](references/gdpr-de.md) | before every full profile; DSAR; yearly LIA review | | [references/competence-catalog-it.md](references/competence-catalog-it.md) | IT profiles | | [references/competence-catalog-template.md](references/competence-catalog-template.md) | non-IT department | | [references/interview-guide.md](references/interview-guide.md) | before wizard start | | [references/skill-anchors-cheatsheet.md](references/skill-anchors-cheatsheet.md) | Phase 4 anchors | | [assets/person-template.md](assets/person-template.md) | create / upgrade | | [assets/stub-template.md](assets/stub-template.md) | stub | | [scripts/auto-enrich.sh](scripts/auto-enrich.sh) | wizard Phase 1 |