feat: add own skills
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
02e2797fbd
commit
ac6208717c
41 files changed
+4632
No files matched your search
@@ -0,0 +1,51 @@
|
||||
# Executing approved proposals
|
||||
|
||||
Reached from step 4 of `SKILL.md`. The approval protocol in `/home/sascha.koenig/p/PM/.okf/processes/it-basecamp-regeln.md` is the rule; this file is the mechanics.
|
||||
|
||||
## Order per item
|
||||
|
||||
1. Make the change.
|
||||
2. Put the comment on the same object: one or two German sentences with the reason, ending in `(lead-radar, <Modus>, YYYY-MM-DD)`. Example: `Neuer Termin 06.11., Lieferant hat Rückmeldung für KW 45 zugesagt. (lead-radar, freitag, 2026-11-13)`.
|
||||
3. Read the object back and check the new value.
|
||||
|
||||
Work through the list in number order. A failing item does not stop the run: note command and error, go on, and report it at the end.
|
||||
|
||||
## Basecamp
|
||||
|
||||
Write mentions as plain names (no `@`), and leave `--notify` off: the comment is the trail, reminders belong to automation A3.
|
||||
|
||||
| Action | Command (check flags with `--agent --help`) |
|
||||
|---|---|
|
||||
| Change owner | `basecamp todos update <id> --assignee <person-id> --json` |
|
||||
| Set date | `basecamp todos update <id> --due YYYY-MM-DD --json` |
|
||||
| Comment | `basecamp comments create <id> - < <scratchpad-file>` (stdin keeps umlauts intact) |
|
||||
| Move to list (same project) | `basecamp todos position <id> --to 1 --list <list-id> --json` |
|
||||
| Complete | `basecamp todos complete <id> --json` |
|
||||
| Read back | `basecamp todos show <id> --json` |
|
||||
|
||||
**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.
|
||||
|
||||
**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.
|
||||
|
||||
## Zammad
|
||||
|
||||
Allowed: set owner, internal note. Requires `ZAMMAD_TOKEN`; base URL from `ZAMMAD_URL`, default as in `tools/it-cockpit/cockpit.py`. Without a token, list the Zammad items as `Für dich:` points with ticket link.
|
||||
|
||||
```bash
|
||||
# owner (owner_id = Zammad user id; resolve via GET /api/v1/users/search?query=<login>)
|
||||
curl -sf -X PUT -H "Authorization: Token token=$ZAMMAD_TOKEN" -H "Content-Type: application/json" \
|
||||
"$ZAMMAD_URL/api/v1/tickets/<id>" -d '{"owner_id": <uid>}'
|
||||
# internal note (the "why" comment for Zammad)
|
||||
curl -sf -X POST -H "Authorization: Token token=$ZAMMAD_TOKEN" -H "Content-Type: application/json" \
|
||||
"$ZAMMAD_URL/api/v1/ticket_articles" \
|
||||
-d '{"ticket_id": <id>, "body": "<Grund>", "type": "note", "internal": true}'
|
||||
```
|
||||
|
||||
Every Zammad article this skill writes has `"internal": true`.
|
||||
|
||||
## OKF
|
||||
|
||||
Edit the concept files under `/home/sascha.koenig/p/PM/.okf/` as approved, set `generated.at` to today, then run the `validate` skill on the bundle. Git stays with Sascha: report the changed paths.
|
||||
Reference in new issue
Block a user