Files
agent-prod/skills/lead-backlog/SKILL.md
T
m3ta-chironandClaude Fable 5.2 0067724277 feat(lead): Stil-Skill und KI-Hinweis für alle Texte an Kollegen
Die Vorgabe galt bisher nur für Kommentare. Sie gilt jetzt auch für
To-do- und Listenbeschreibungen sowie Dokumente; To-do-Titel bleiben
ohne Hinweis. Die Meeting-Zusammenfassung wird in Saschas Stil
geschrieben statt im Ton des Meetings.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2026-11-12 13:03:46 +01:00

7.3 KiB
Raw Blame History

name, description, compatibility
name description compatibility
lead-backlog 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". 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 <project name or ID>. 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/ap/PM/.okf/systems/basecamp.md: Backlog project and category to-do-set IDs, API gotchas (section "Gotchas Projektüberführung")
  • /home/sascha.koenig/ap/PM/.okf/processes/it-basecamp-regeln.md: approval protocol, binding for every write, including the Backlog exception
  • /home/sascha.koenig/ap/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 <backlog-id> --json (dock), carry on, and report the mismatch.

Load the basecamp skill before any CLI call; check flags with basecamp <cmd> --agent --help.

Texts colleagues read (Basecamp comments, to-do and list descriptions, documents; Zammad internal notes): load sascha-internal-communication-style before drafting the first one and write the German text in that style. To-do titles stay plain. End every such text with one empty line and the AI marker in italics, exactly:

<Text>

*✨unterstützt durch KI✨*

Show each text 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.
  • 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. 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 <id> --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 to a scratchpad file. Title: <Projektname> (überführt) — <Zustand in 3–5 Worten>.

  • 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.
  • Attachments (screenshots, files in descriptions or comments) that are needed to understand an open to-do travel with it: download with basecamp files download "<href>" --out <dir> and attach to the child to-do (todos create … --attach). 📥 Backlog readers usually have no access to 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: <Owner> informieren. Pinging is not part of this skill.

4. Create

basecamp todolists create "<Titel>" --description "$(cat <scratchpad-file>)" --in <backlog-id> --todoset <category-id> --json
basecamp todos create "<Inhalt>" --in <backlog-id> --list <new-list-id> --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/ap/PM/.okf/:

  • projects/basecamp-portfolio.md: strike through the project row and link the Backlog list (~~**Name**~~ … *→ [Backlog <Kategorie> migriert YYYY-MM-DD](<link>)*).
  • 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.