fix(lead): Anhänge bei Projektumzug und Parken mitnehmen
- execute.md: Anhänge aus Beschreibung und Kommentaren herunterladen und am neuen To-do anhängen; Read-back nennt die Anzahl - lead-backlog: dasselbe für Kind-To-dos bei der Überführung - ich.md: Anhangszahl im Aufräumen-Block Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This commit is contained in:
1 parent
06acee80c2
commit
22691d2ba2
3 files changed
+5
-2
No files matched your search
@@ -33,12 +33,14 @@ Mention the addressees as described under **Mentions** in `SKILL.md` (`[@Name](p
|
||||
|
||||
Creating a to-do is allowed in mode `ich` for Sascha's own commitment from a Sally recording (owner always Sascha), and in any mode as the second half of a project move or of parking (rule 5 of the approval protocol). The description carries one context sentence and the link to the recording or the original; the new to-do gets the same why-comment as every change. On a project move the owner may change when the approval says so; then the new owner is mentioned in the comment on the new to-do, and the requester is mentioned in the comment on the original.
|
||||
|
||||
**Attachments travel with the to-do.** Before a project move or parking, read the original's `description` for `<bc-attachment … href="…" filename="…">` blocks and check its comments for attachments. Download each with `basecamp files download "<href>" --out <dir>` (the CLI writes `<dir>/<filename>`), then attach them to the new to-do: either `todos create … --attach <file>` or a first comment `comments create <new-id> "<Text>" --attach <file> [--attach …]`. The new owner often has no access to the original project, so a link alone loses the screenshots. Report "N Anhänge übernommen" per item in the read-back.
|
||||
|
||||
Projects with several to-do sets (🔁 Übergaben & Koordination, [IT] - Data Hub Analytics v1) need `--todoset <id>` on `todolists list` and `todos create`; IDs in `systems/basecamp.md`. The person must be a member of the target project (`basecamp people list --in <id>`), otherwise the move is a `Für dich:` point.
|
||||
|
||||
**Parking:**
|
||||
|
||||
- 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.
|
||||
- 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, a link to the original and the original's attachments (see below), 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 <Projekt>`; it runs with its own approval.
|
||||
|
||||
**Cards** (card tables, e.g. Azubi board): comment with `basecamp comments create <card-id>`; moving cards between columns is the card owner's job, so propose it as a `Für dich:` point.
|
||||
|
||||
Reference in new issue
Block a user