--- 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.