diff --git a/skills/lead-backlog/SKILL.md b/skills/lead-backlog/SKILL.md new file mode 100644 index 0000000..8fda629 --- /dev/null +++ b/skills/lead-backlog/SKILL.md @@ -0,0 +1,96 @@ +--- +name: lead-backlog +description: | + Transfer a whole Basecamp project into 📥 Backlog / Ideenspeicher without losing content, decisions, open points or the colleagues' exchange, then leave it ready to archive. For stalled projects and projects that are really just an idea. Single to-dos are parked by lead-radar instead. + Triggers: "Projekt ins Backlog", "Projekt überführen", "Projekt parken", "brachliegendes Projekt aufräumen", "Projekt schließen ohne Informationsverlust". +compatibility: opencode, claude-code +--- + +# lead-backlog + +One project in, one structured entry in 📥 Backlog out: a to-do list in the matching category, with the original still reachable after Sascha archives it. + +Invocation: `/lead-backlog `. Several projects run one after the other, each with its own approval. + +## Sources of truth + +Read before acting; these hold the facts, this skill holds only behaviour: + +- `/home/sascha.koenig/p/PM/.okf/systems/basecamp.md`: Backlog project and category to-do-set IDs, API gotchas (section "Gotchas Projektüberführung") +- `/home/sascha.koenig/p/PM/.okf/processes/it-basecamp-regeln.md`: **approval protocol**, binding for every write, including the Backlog exception +- `/home/sascha.koenig/p/PM/.okf/playbooks/projekt-in-backlog-ueberfuehren.md`: when a transfer is the right move + +An ID that fails: resolve it by name via `basecamp projects show --json` (dock), carry on, and report the mismatch. + +Load the `basecamp` skill before any CLI call; check flags with `basecamp --agent --help`. + +## Steps + +### 1. Inventory + +Read the whole project: to-dos (open **and** done, per list), messages with their comments, comments under to-dos, vault documents and files, card tables if present. Determine the true last activity from `basecamp timeline --in --json`. + +Find the project owner: OKF concept under `projects/`, else the Basecamp project description, else ask Sascha. + +**Done when** every list, message and vault item has been opened, and you can state the done/total ratio, last real activity, and owner. + +### 2. Classify + +Pick the category from the to-do sets in `systems/basecamp.md`; "passt am ehesten" is enough. 🗑️ Verworfen / Archiv is not a target. + +Pick the type, which sets the form of the entry: + +| Type | Signal | Form | +|---|---|---| +| **A** stalled, with open work | concrete open to-dos that lead somewhere | list + open to-dos as child to-dos, 1:1 | +| **B** idea or vision | loose skeleton, or to be replanned on reactivation | list with description only | +| **C** looks done, is not | e.g. 2/2 ticked, but planning is outstanding or the real scope was never captured | like B + ⚠️ "nicht abgeschlossen" | + +**Done when** category and type each have a one-line reason. + +### 3. Draft and propose + +Write the description following [references/vorlage.md](references/vorlage.md) to a scratchpad file. Title: ` (überführt) — `. + +- Done work appears as a summary in section 3, never as to-dos. +- Exchange with substance is quoted verbatim with name and date. This is the most common loss when tidying up. +- Include what is needed to resume or to reject the idea with good reason; the full history stays in the archived original. + +Present in German, as one numbered proposal for this project: + +1. Category, type, title, and the **complete description text**. +2. Type A: the child to-dos, without due dates or assignees (parked work has neither, and assigning would notify people). +3. **Zitate:** each quote with author and source. 📥 Backlog is visible across the organisation, so compare the original project's audience and flag quotes that were written for a smaller circle or concern a person; for those, propose a summary. +4. **Owner informiert?** Name the owner and ask. Sascha as owner: mark as not applicable. +5. The OKF edits from step 5. + +**Done when** Sascha has approved explicitly and confirmed the owner knows. If the owner does not know yet, stop for this project and report `Für dich: informieren`. Pinging is not part of this skill. + +### 4. Create + +```bash +basecamp todolists create "" --description "$(cat )" --in --todoset --json +basecamp todos create "" --in --list --json # type A, one per open to-do +``` + +Keep group prefixes (🔥/👤/🤖/🏗️ …) in child to-dos. The description cannot be changed via API after creation, which is why the approved text goes in unchanged. + +**Done when** the list reads back with the description rendered, and for type A the to-do count matches the proposal. A wrong list is reported as `Für dich:` with its link; removing it is Sascha's call. + +### 5. Update OKF + +As approved, edit under `/home/sascha.koenig/p/PM/.okf/`: + +- `projects/basecamp-portfolio.md`: strike through the project row and link the Backlog list (`~~**Name**~~ … *→ [Backlog migriert YYYY-MM-DD]()*`). +- The project's concept under `projects/`, if any: same pointer in its Basecamp line, task state replaced by the link (goals, context and decisions stay). +- `log.md`: one dated `applied:` entry with project, list link and type. + +Set `generated.at` to today on edited concepts and run the `validate` skill. Git stays with Sascha: report the changed paths. + +**Done when** `validate` passes. + +### 6. Report + +In German: list link, type, to-do count, changed OKF paths, and `Für dich: Originalprojekt archivieren (nicht löschen, sonst brechen die Links)`. The original stays untouched by this skill. + +**Done when** the report is out. diff --git a/skills/lead-backlog/references/vorlage.md b/skills/lead-backlog/references/vorlage.md new file mode 100644 index 0000000..ed07f73 --- /dev/null +++ b/skills/lead-backlog/references/vorlage.md @@ -0,0 +1,79 @@ +# Entry template and HTML + +Reached from step 3 of `SKILL.md`. The list description is final at creation, so write it complete. Adapt section labels to the case ("Ziel/Vision", "Idee/Konzept", "Stand"); leave out sections with nothing to say. + +## Template (German) + +``` +Überführt aus Projekt: — +Gestartet: · Eingestellt: · Letzte Aktivität: (~X Wochen brach) + +1) +<1–2 Sätze: was war das Ziel, was die Idee> + +2) + + +3) Was ist schon erledigt? (nicht wiederholen) + + +4) Was ist noch offen? (falls reaktiviert) + + +5) 💬 Austausch der Kollegen / ⭐ Artefakte (erhalten) + + +6) Reaktivierung + Reifecheck erfüllt? +⚠️ Bei Reaktivierung: + +7) Quellen +Originalprojekt (ARCHIVIEREN, nicht löschen): +· verwandt: · zuletzt aktiv: +``` + +## HTML rules + +Basecamp renders list descriptions with tight line spacing. + +| Effect | Use | Renders badly | +|---|---|---| +| Gap between sections | `


` | consecutive `

` | +| Label + content | `

1) Ziel
Inhalt…

` | label and content as separate flat lines | +| Bullets | `
  • …
` | `• Text` + `
` | +| Quoted comment | `
…
` | bare paragraphs (attribution gets lost) | +| Link | `Text` | bare URL | +| Bold | `` | `**text**` | + +Build rule: each section is `

Label…

`, sections separated by one `


`, lists and quotes as their own block elements. + +## Worked example + +Title: `Kapazitätsbasierte Auftragseinsteuerung (überführt) — Idee mit Diskussionsstand` (category 🏭 Produktion & Qualität). Description excerpt: + +```html +

Überführt aus Projekt: + Kapazitätsbasierte Auftragseinsteuerung + — Gestartet 08.07.2026 · nur Diskussionsstand

+


+

1) IST-Zustand (André Hänig)
+ Kundenbestellungen werden ohne Rückkopplung zu Fertigungskapazitäten erfasst …

+


+

2) 💬 Austausch der Kollegen (08.07.2026, erhalten)

+

Laurentiu Mihai (09:16):

+
Ergänzung: Vertrieb stimmt FAs mit Planung ab … Größtes Problem: BPL-Artikel …
+


+

3) Reaktivierung
+ Wieder ein Projekt, wenn Kapazitäts-/Engpass-Themen angegangen werden …

+


+

4) Quellen
+ Original (ARCHIVIEREN, nicht löschen): …

+``` + +## Lessons from past transfers + +- **Glossary:** add one line for domain abbreviations in the quoted exchange (FA, WBZ, BPL, AE …) so it stays readable later. +- **Related projects:** link them and say how they relate, e.g. Auftragseinsteuerung as the upstream lever for Engpasssteuerung. +- **Type C:** mark it plainly: "⚠️ NICHT abgeschlossen, sieht nur so aus, Planung steht aus". +- **Type B:** write "bei Reaktivierung neu planen" into the Reaktivierung section so the old skeleton is not adopted blindly. diff --git a/skills/lead-radar/SKILL.md b/skills/lead-radar/SKILL.md index dbc833c..ca8c40b 100644 --- a/skills/lead-radar/SKILL.md +++ b/skills/lead-radar/SKILL.md @@ -64,7 +64,7 @@ Open the mode's reference and follow it; it says which keys to read, how to judg 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. +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. A stalled project or one that is really just an idea becomes `Für dich: /lead-backlog `. 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?" diff --git a/skills/lead-radar/references/execute.md b/skills/lead-radar/references/execute.md index e7f2352..22f9df3 100644 --- a/skills/lead-radar/references/execute.md +++ b/skills/lead-radar/references/execute.md @@ -27,6 +27,7 @@ Write mentions as plain names (no `@`), and leave `--notify` off: the comment is - 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. +- A whole project: `Für dich: /lead-backlog `; it runs with its own approval. **Cards** (card tables, e.g. Azubi board): comment with `basecamp comments create `; moving cards between columns is the card owner's job, so propose it as a `Für dich:` point. diff --git a/skills/lead-radar/references/portfolio.md b/skills/lead-radar/references/portfolio.md index 085dea9..09c2592 100644 --- a/skills/lead-radar/references/portfolio.md +++ b/skills/lead-radar/references/portfolio.md @@ -26,6 +26,7 @@ Sort the rows first: - **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. +- **überführen**: the whole project is stalled or really just an idea. No to-do proposals; `Für dich: /lead-backlog `. - **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) @@ -38,12 +39,12 @@ For every OKF concept of an initiative, find task state: to-do lists, "nächster # 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] +[2–4 Sätze: wie viele Initiativen, wo Sascha zu viel hält, was abgegeben/geparkt/überführt/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 | +| [Name](link) | … / fehlt | ✅ / fehlt | TT.MM. / fehlt | N (davon M überfällig) | weiterführen / abgeben an X / parken / überführen / streichen | ## Begründungen - **Projekt**: warum diese Empfehlung