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,98 @@
|
||||
---
|
||||
name: lead-meeting-followup
|
||||
description: |
|
||||
Follow up a recorded meeting for Sascha: pull the Sally recording, write the German
|
||||
"📝 Meeting-Zusammenfassung" into the right Basecamp project, then propose rule-compliant
|
||||
Basecamp to-dos (and optional OKF decisions) and create them after approval.
|
||||
Use when the user wants to: document / summarize / follow up a meeting, file meeting notes
|
||||
or a transcript in Basecamp, or turn meeting action items into to-dos.
|
||||
Triggers: "Meeting nachbereiten", "Meeting-Zusammenfassung", "letztes Meeting nach Basecamp".
|
||||
compatibility: opencode, claude-code
|
||||
---
|
||||
|
||||
# lead-meeting-followup
|
||||
|
||||
The single path for meeting follow-up in the `lead-*` family. One run = one recording → one Basecamp document → approved to-dos.
|
||||
|
||||
## Sources of truth
|
||||
|
||||
Read before acting; these hold the facts, this skill holds only behaviour:
|
||||
|
||||
- `/home/sascha.koenig/p/PM/.okf/processes/meeting-runden.md`: round profiles (filing project, Sally search term, participants)
|
||||
- `/home/sascha.koenig/p/PM/.okf/processes/it-basecamp-regeln.md`: to-do rules, the six 👥 IT lists, approval protocol
|
||||
- `/home/sascha.koenig/p/PM/.okf/systems/basecamp.md`: project, list and folder IDs
|
||||
- `/home/sascha.koenig/p/PM/.okf/organization/*.md`: people and their Basecamp person IDs
|
||||
|
||||
An ID that fails: resolve by name, carry on, and mention the mismatch in the final report.
|
||||
|
||||
Load the `basecamp` skill before any Basecamp CLI call. Check flags with `basecamp <cmd> --agent --help`; they evolve.
|
||||
|
||||
## Steps
|
||||
|
||||
### 1. Pick the recording
|
||||
|
||||
Use the Sally MCP tools (`search_appointments`, `get_recordings`, `get_summary`, `get_transcription`; read each tool's schema for its arguments). List Sascha's ~5 most recent recordings (title, date) and let the user pick; default to the newest.
|
||||
|
||||
Fetch the full transcription and Sally's summary. Sally's summary and task suggestions are raw material; the transcript is authoritative. For a long transcript, hand extraction to a subagent if the harness offers one: ask for goals, decisions, next steps, action items (task / owner / deadline), open questions, risks, links, in German, one line each.
|
||||
|
||||
**Done when** you hold the transcript-grounded notes and the meeting date, title and participants.
|
||||
|
||||
### 2. Settle the project
|
||||
|
||||
Match the recording title against the Sally search terms in `meeting-runden.md`. On a match, propose that round's filing project and let the user confirm in one word. Otherwise ask, offering a shortlist from `basecamp projects list --json` (names matching participants or keywords) plus free text.
|
||||
|
||||
**Done when** the user has confirmed a project and you hold its numeric ID.
|
||||
|
||||
### 3. Draft and clarify
|
||||
|
||||
Fill `assets/template.md`. Keep every header, emoji and section exactly; write German in the meeting's tone.
|
||||
|
||||
- **Header block:** from recording metadata. Protokoll = the assistant unless a note-taker is named. Bezug = the chosen project. Every header line keeps its two trailing spaces (Markdown hard break); without them Basecamp collapses the header into one line.
|
||||
- **Ziel:** from the opening minutes, the stated purpose.
|
||||
- **Kurzfazit:** 3–5 sentences covering the three bullets (Erkenntnis / Entscheidung / offener Punkt).
|
||||
- **Entscheidungen:** only what was actually agreed, with context and scope; leave the list minimal when nothing was decided.
|
||||
- **Nächste Schritte** (higher-level follow-ups) vs. **To-dos** (concrete assigned actions): each item lives in exactly one of the two.
|
||||
- **Kontext & Links:** project, meeting link, `sally://recording/<id>`.
|
||||
|
||||
Speech-to-text garbles names and jargon: mark every doubt as `[unklar: …]` while drafting, then ask the user about all of them in one batch and apply the answers.
|
||||
|
||||
**Done when** the draft holds zero `[unklar]` markers.
|
||||
|
||||
### 4. Post the document
|
||||
|
||||
Posting is the expected next action; go straight ahead without a "should I post?" gate. Fixes after posting happen by updating the document.
|
||||
|
||||
1. Find the `Meetings` folder in the project (`basecamp files list --in <project> --json`); create it if missing.
|
||||
2. Create the document `YYYY-MM-DD – <Meetingtitel>` (meeting date, never today's) in that folder with `--no-subscribe`. Pass the long Markdown from a temp file in the scratchpad.
|
||||
3. Read it back and keep its URL.
|
||||
|
||||
**Done when** the document is readable in Basecamp and you have its URL.
|
||||
|
||||
### 5. Propose, approve, create
|
||||
|
||||
Draft one to-do per item in "📌 To-dos" and "➡️ Nächste Schritte" (skip when both are empty), following `it-basecamp-regeln.md`:
|
||||
|
||||
- **Title:** verb first, actionable.
|
||||
- **Description:** why it matters, definition of done, dependency, link to the summary document.
|
||||
- **Owner:** exactly one, resolved to a Basecamp person ID via the OKF profiles or `basecamp people list`.
|
||||
- **Due date:** always one. A deadline named in the meeting is resolved against the meeting date; otherwise propose a date and label it `Vorschlag`.
|
||||
- **List:** the best existing list. In 👥 IT one of the six rule lists. Where no list fits, say so and propose the closest one; list creation is reserved for the Friday close.
|
||||
|
||||
Add, under the same approval, a proposal "als OKF-Decision anlegen?" for each decision whose reach goes beyond this meeting.
|
||||
|
||||
Present everything as one numbered list (title, owner, due date, list, description). The user approves as a batch, drops items by number, or edits single items. Act on an explicit answer only.
|
||||
|
||||
Create the approved to-dos (`basecamp todos create … --assignee <id> --due <date> --list <id> --in <project> --json`). Write approved decisions as `type: Decision` concepts in `/home/sascha.koenig/p/PM/.okf/decisions/` with `status: draft`, source `sally://recording/<id>`, and a link to the summary document; validate the bundle with the `validate` skill.
|
||||
|
||||
**Done when** every approved item exists and you report: document URL, to-do URLs, OKF files, and any ID mismatches from the sources-of-truth check.
|
||||
|
||||
## Guardrails
|
||||
|
||||
- Every decision, owner and deadline in the document traces back to the transcript.
|
||||
- The project is always confirmed by the user, even when a round profile suggests it.
|
||||
- Every to-do carries context; a bare title is incomplete.
|
||||
- To-dos and OKF decisions wait for explicit approval; the summary document does not.
|
||||
|
||||
## Template refresh
|
||||
|
||||
`assets/template.md` is a local copy of the Basecamp document "📝 Meeting-Zusammenfassung" (project 👥 IT- und Projektabstimmung CZ/DE `47617617`, document `10159592734`). Refresh it only on request by re-fetching that document.
|
||||
Reference in new issue
Block a user