In teams with several active channels, it is easy to lose track: important decisions sit in the middle of a long thread, action items get mentioned in passing, and anyone who was not there live has to work through the history by hand. The Team Digest Loop takes this catch-up effort off your plate.
\nEach day at a fixed time, the workflow retrieves the messages from the past 24 hours in the configured channels, groups them by topic, and filters out small talk. From the remaining content it extracts decisions, open discussions, action items, and announcements, and turns them into a compact digest with channel references, which goes out by email or as a channel post.
\nThe human stays involved at two points: choosing the channels and recipients, and reading the digest itself, which handles the actual substantive judgment. What gets automated is the gathering and pre-sorting, not the assessment of what matters. This is a common automation without a Voyage-specific cut, but with direct value for internal coordination.
\nCopy the prompt below in full into your automation tool or agent builder. As a file: team-digest-schleife.en.json
\n" } ], "schritte": [ { "nr": 1, "titel": "Time trigger", "beschreibung": "On working days at a fixed time, for example 5:00 PM, with an optional pause on weekends.", "rolle": "mensch" }, { "nr": 2, "titel": "Retrieve channels", "beschreibung": "Messages from the past 24 hours are loaded from the defined channels.", "rolle": "automatisch" }, { "nr": 3, "titel": "Cluster threads", "beschreibung": "The messages are grouped by topic, small talk is filtered out.", "rolle": "automatisch" }, { "nr": 4, "titel": "Extract content", "beschreibung": "Decisions, open discussions, action items, and updates are pulled out.", "rolle": "automatisch" }, { "nr": 5, "titel": "Format the digest", "beschreibung": "The digest is built with headings per category, bullet points, and channel references.", "rolle": "automatisch" }, { "nr": 6, "titel": "Send or post", "beschreibung": "The finished digest goes by email to the distribution list or as a post in a channel.", "rolle": "ergebnis" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26", "nutzen": [ { "titel": "Less information overload", "text": "A curated daily digest replaces reading through every single channel." }, { "titel": "Decisions and tasks become visible", "text": "Resolutions and action items are extracted in a structured way instead of getting lost in threads." }, { "titel": "Better asynchronous work", "text": "Anyone who was not there live still stays current." }, { "titel": "A stronger async culture", "text": "Discussions no longer need to be followed in real time." } ], "voraussetzungen": [ { "label": "Team chat", "text": "Slack, Teams, or Discord supplies the channel messages via API or bot access.", "icon": "forum" }, { "label": "Output channel", "text": "Gmail, Outlook, Notion, or a channel for the finished digest.", "icon": "outgoing_mail" }, { "label": "Configuration", "text": "Channel list, time window, and output format are defined in advance.", "icon": "tune" }, { "label": "LLM access", "text": "API key for OpenAI, Claude, or Gemini.", "icon": "key" } ], "betrieb": { "testing": [ { "label": "Test run", "text": "Run the workflow once against an active day with real traffic before you go live.", "icon": "play_circle" }, { "label": "Fetch and clustering", "text": "Check whether all channels are read and similar topics are grouped correctly.", "icon": "download" }, { "label": "Extraction and format", "text": "Verify that decisions and action items are cleanly separated and formatted.", "icon": "fact_check" }, { "label": "Edge cases", "text": "Test low and high traffic, long threads, and multilingual or parallel discussions.", "icon": "rule" } ], "goLive": [ { "label": "Approve", "text": "Activate the workflow only once fetching, digest quality, and delivery are correct.", "icon": "check_circle" }, { "label": "Core channels", "text": "Start with two to three channels and a small recipient group.", "icon": "tag" }, { "label": "Adjust", "text": "Fine-tune the channel list and output format after one to two weeks.", "icon": "tune" }, { "label": "Expand", "text": "Later add sentiment analysis, team-specific digests, a weekly digest, or action item tasks.", "icon": "rocket_launch" } ], "haeufigeFehler": [ { "label": "No messages retrieved", "text": "Check the channel IDs and bot permissions.", "icon": "lock" }, { "label": "Digest too long or too short", "text": "Add an explicit length specification to the prompt.", "icon": "straighten" }, { "label": "Too much small talk", "text": "Add an instruction in the prompt to consistently ignore small talk.", "icon": "filter_alt" }, { "label": "Action items without owners", "text": "Require an owner or mark the item as unclear.", "icon": "person_off" } ] }, "arbeitsprompts": [ { "titel": "Prompt: Summary Agent", "beschreibung": "Evaluates the collected channel messages and delivers the structured summary for the digest.", "prompt": "You are an expert in analyzing team communication. Analyze the following Slack or Teams messages from the past 24 hours and create a concise summary.\n\nContext:\nCompany: [COMPANY_NAME]\nTeam: [TEAM_NAME]\nTime range: [TIME_RANGE]\n\nMessages:\n[CHANNEL_MESSAGES]\n\nTask:\nCreate a structured summary organized into the following categories:\n\n1. Key decisions: what concrete resolutions were made?\n2. Ongoing discussions: what topics are currently being discussed and remain open?\n3. Action items: what concrete tasks were mentioned, with owners if named?\n4. Updates and announcements: what important news came up?\n5. Miscellaneous: other points worth noting.\n\nFormat:\nUse clear headings. Keep it short and concise, a maximum of two to three sentences per point. Avoid unimportant small talk or irrelevant messages. Name the relevant channel in parentheses for important points. Use bullet points for readability.\n\nTone: professional, factual, focused on what matters." } ], "prompt": "GOAL\nBuild a workflow that fetches the messages from the past 24 hours in defined Slack or Teams channels on working days, clusters them by topic, and turns them into a structured daily digest with decisions, open discussions, action items, and updates, delivered by email or as a channel post.\n\nAdapt the structure to the concepts of your automation tool (for example nodes, steps, zaps, or agent actions). While doing so, preserve the trigger logic, the sequence, and the data flow.\n\nTRIGGER\nType: time based, on working days at a fixed time, for example 5:00 PM, with an optional pause on weekends.\nScope: messages and thread replies from the past 24 hours in a defined channel list (Slack, Teams, or Discord, via API or bot).\n\nSTEPS (sequential)\n1. Fetch channels: load all messages from the past 24 hours including thread replies from the configured channel list, each with the channel name attached to the message.\n2. AI step: summary. Insert the working prompt \"Summary Agent\" exactly as given (see the Working Prompts section). It clusters the messages by topic, filters out small talk, and extracts the five categories decisions, discussions, action items, updates, and miscellaneous.\n3. Finalize the digest: build a digest from this with clear headings per category, bullet points, and the relevant channel reference in parentheses.\n4. Output: send the digest by email to the defined distribution list or post it in a dedicated digest channel, depending on configuration.\n\nPROMPT GUIDANCE\nThere is a fixed working prompt for the analysis step, see the Working Prompts section. Insert it unchanged and in full into step 2.\n\nDATA FLOW\nStep 1 to step 2: channel messages including channel names, plus the time range of the past 24 hours, calculated automatically, as input for the placeholders in the working prompt.\nStep 2 to steps 3 and 4: the finished digest text as the basis for formatting and delivery.\n\nERROR HANDLING\nNo messages retrieved: check the channel IDs and bot permissions. End the run with an error notice instead of sending an empty digest.\nNo relevant content after filtering: send a short notice (No relevant discussions today) instead of an empty digest.\nVery high traffic close to the token limit: summarize per channel first, then aggregate across all channel summaries.\nAction items without a recognizable owner: mark these as unclear instead of guessing a person.\n\nPLACEHOLDER CONVENTION\nAll placeholders in square brackets in the working prompt are variables. The channel messages and the time range are mapped dynamically, as described in the data flow. The company name and team name are not dynamic: fill these in manually before activation. List all placeholders that require manual configuration separately at the end.\n\nSELF CHECK BEFORE COMPLETION\nCheck, before you report the workflow as finished:\n1. Are all steps connected correctly, including the time trigger and the optional weekend pause?\n2. Is the working prompt inserted in full and unchanged, and are the channel messages and time range mapped correctly?\n3. Is the output channel (email distribution list or channel) configured as intended?\n4. Are all points listed that require manual configuration: the channel list or channel IDs, bot permissions, recipients, LLM access, company name, and team name?", "einrichtung": { "intro": "Two routes lead to the same result. Pick the one that fits your setup.", "varianten": [ { "variante": "Builder-Prompt", "einleitung": "Suitable when you want to build the workflow in your own automation tool.", "schritte": [ "Open your workflow tool, for example n8n, Make, Zapier or Langdock.", "Create a new workflow and give it a name.", "Choose the AI-assisted build option if your tool offers one.", "Paste the builder prompt from above in full.", "Check the result against the step sequence in this document, then add your access credentials and channels." ] }, { "variante": "JSON-Import", "einleitung": "Suitable when you want to take the workflow over unchanged.", "schritte": [ "Download the JSON file from the JSON export section.", "Open the workflow area of your tool and create a new workflow.", "Give it a name and confirm.", "Open the menu on the workflow name and choose to import a JSON file.", "Upload the file, then add your own access credentials.", "Run a test before you activate the workflow." ] } ] }, "exportMeta": { "datei": "w24_team-digest-schleife__workflow.json", "format": "voyage-workflow/1" }, "download": { "schema": "voyage-workflow/1", "name": "Die Team-Digest-Schleife", "beschreibung": "Ruft täglich die Nachrichten der letzten 24 Stunden aus definierten Slack- oder Teams-Channels ab, clustert sie thematisch und extrahiert Entscheidungen, offene Diskussionen, Action Items und Updates. Daraus entsteht ein strukturierter Daily Digest, der per E-Mail oder als Channel-Post verschickt wird.", "trigger": { "typ": "Zeitgesteuert per Cron", "bedingung": "Der Trigger-Knoten ist auf den Cron-Ausdruck 0 17 * * * (UTC) konfiguriert und startet den Workflow damit jeden Tag um 17:00 Uhr UTC, auch am Wochenende. Eine Pause am Wochenende ist keine Grundeinstellung des Knotens, sondern eine optionale Anpassung des Cron-Ausdrucks, zum Beispiel 0 17 * * 1-5 für ausschließlich Montag bis Freitag." }, "schritte": [ { "nr": 1, "titel": "Zeit-Trigger", "rolle": "mensch", "aktion": "Ein zeitgesteuerter Cron-Trigger mit dem Ausdruck 0 17 * * * startet den Workflow täglich um 17:00 Uhr UTC. Die Fehlerstrategie dieses Knotens ist stop. Eine Wochenend-Pause ist keine Grundeinstellung, sondern eine optionale Anpassung des Cron-Ausdrucks, etwa auf 0 17 * * 1-5 für ausschließlich Werktage.", "prompt_ref": null, "eingang": [], "ausgang": [ "Startsignal (Cron-Auslösung 0 17 * * *, UTC)" ] }, { "nr": 2, "titel": "Channels abrufen", "rolle": "automatisch", "aktion": "Zunächst berechnet ein Code-Schritt (calculateTimeWindow) das Zeitfenster der letzten 24 Stunden im ISO-8601-UTC-Format, das die Slack-API erwartet: oldest und latest als technische Zeitstempel, dazu readableOldest und readableLatest als lesbare deutsche Zeitangaben für die spätere E-Mail. Anschließend durchläuft eine Schleife (channelLoop) die konfigurierte Liste der Slack-Channel-IDs, bis zu 20 Channels, standardmäßig sequentiell und wahlweise parallel schaltbar über die Concurrency-Einstellung. Für jeden Channel ruft getSlackMessages die Nachrichten zwischen oldest und latest ab, inklusive Thread-Antworten (showThreads: true). Der Loop-End-Knoten (channelLoopEnd) sammelt die Ergebnisse aller Iterationen; seine Fehlerstrategie steht standardmäßig auf continue, ein Fehler in einem einzelnen Channel stoppt also nicht den gesamten Lauf.", "prompt_ref": null, "eingang": [ "Startsignal (Cron-Auslösung 0 17 * * *, UTC)" ], "ausgang": [ "Gesammelte Channel-Nachrichten aller Iterationen inklusive Thread-Antworten (channelLoopEnd)", "Berechnetes Zeitfenster: oldest, latest, readableOldest, readableLatest (calculateTimeWindow)" ] }, { "nr": 3, "titel": "Threads clustern", "rolle": "automatisch", "aktion": "Der Zusammenfassungs-Agent (messageAnalyzer) erhält alle gesammelten Nachrichten in einem einzigen strukturierten KI-Aufruf und gruppiert sie thematisch, Small Talk wird herausgefiltert. Dieser Schritt läuft im selben Aufruf wie Schritt 4 und 5; das Ergebnis kommt als strukturiertes Ausgabeschema mit den Pflichtfeldern summary und success sowie den optionalen Feldern message_count und key_topics zurück.", "prompt_ref": "arbeitsprompt-1", "eingang": [ "Gesammelte Channel-Nachrichten aller Iterationen inklusive Thread-Antworten (channelLoopEnd)", "Berechnetes Zeitfenster: oldest, latest, readableOldest, readableLatest (calculateTimeWindow)" ], "ausgang": [ "Thematisch gruppierte Nachrichten ohne Small Talk (Zwischenstand innerhalb desselben KI-Aufrufs)" ] }, { "nr": 4, "titel": "Inhalte extrahieren", "rolle": "automatisch", "aktion": "Aus den gruppierten Nachrichten zieht derselbe KI-Aufruf Entscheidungen, offene Diskussionen, Action Items und Updates heraus. Action Items ohne erkennbare Verantwortliche werden als unklar markiert, nicht geraten. Die identifizierten Hauptthemen landen im Feld key_topics, die Anzahl der analysierten Nachrichten im Feld message_count.", "prompt_ref": "arbeitsprompt-1", "eingang": [ "Thematisch gruppierte Nachrichten ohne Small Talk (Zwischenstand innerhalb desselben KI-Aufrufs)" ], "ausgang": [ "Extrahierte Kategorien und Metadaten: message_count, key_topics" ] }, { "nr": 5, "titel": "Digest formatieren", "rolle": "automatisch", "aktion": "Aus den extrahierten Kategorien formuliert derselbe KI-Aufruf den fertigen Digest direkt als HTML-formatierten Text im Feld summary, mit Überschriften pro Kategorie, Bullet Points und Channel-Referenz in Klammern bei wichtigen Punkten. Das Feld success zeigt an, ob die Analyse erfolgreich war.", "prompt_ref": "arbeitsprompt-1", "eingang": [ "Extrahierte Kategorien und Metadaten: message_count, key_topics" ], "ausgang": [ "Strukturierte Ausgabe des Analyse-Agenten: summary (HTML), success, message_count, key_topics" ] }, { "nr": 6, "titel": "Versand oder Posting", "rolle": "ergebnis", "aktion": "Der Versand-Knoten (sendSummaryEmail) baut daraus eine HTML-E-Mail: Betreff Täglicher Slack Digest, ergänzt um den berechneten Zeitpunkt (readableLatest), Body mit dem Zeitraum aus readableOldest und readableLatest sowie dem Feld summary, dazu ein automatisch generierter Fußtext. Empfänger, CC und BCC werden über die Felder mailRecipient, cc und bcc konfiguriert; der Platzhalter team@example.com muss vor dem Go-Live durch die echten Adressen ersetzt werden. Alternativ lässt sich der Digest statt per E-Mail in einen dedizierten Channel posten.", "prompt_ref": null, "eingang": [ "Strukturierte Ausgabe des Analyse-Agenten: summary (HTML), success, message_count, key_topics", "Berechnetes Zeitfenster: readableOldest, readableLatest (calculateTimeWindow)" ], "ausgang": [ "Versendeter oder geposteter Digest (mailRecipient, mailSubject, mailBody, optional cc/bcc)" ] } ], "prompts": { "arbeitsprompt-1": { "titel": "Zusammenfassungs-Agent", "text": "Sie sind Expertin oder Experte für die Analyse von Team-Kommunikation. Analysieren Sie die folgenden Slack- oder Teams-Nachrichten der letzten 24 Stunden und erstellen Sie eine prägnante Zusammenfassung.\n\nKontext:\nUnternehmen: [UNTERNEHMENSNAME]\nTeam: [TEAMNAME]\nZeitraum: [ZEITRAUM]\n\nNachrichten:\n[CHANNEL_NACHRICHTEN]\n\nAufgabe:\nErstellen Sie eine strukturierte Zusammenfassung nach folgenden Kategorien:\n\n1. Wichtige Entscheidungen: Welche konkreten Beschlüsse wurden getroffen?\n2. Laufende Diskussionen: Welche Themen werden aktuell diskutiert und sind noch offen?\n3. Action Items: Welche konkreten Aufgaben wurden erwähnt, mit Verantwortlichen, falls genannt?\n4. Updates und Ankündigungen: Welche wichtigen Neuigkeiten gab es?\n5. Sonstiges: weitere erwähnenswerte Punkte.\n\nFormat:\nNutzen Sie klare Überschriften. Fassen Sie sich kurz und prägnant, maximal zwei bis drei Sätze pro Punkt. Vermeiden Sie unwichtigen Small Talk oder irrelevante Nachrichten. Nennen Sie bei wichtigen Punkten den jeweiligen Channel in Klammern. Nutzen Sie Bullet Points für bessere Lesbarkeit.\n\nTonalität: professionell, sachlich, auf das Wesentliche fokussiert." } }, "datenfluss": [ { "von": 1, "nach": 2, "nutzlast": "Startsignal aus dailyTrigger (Kante output-success zu input-default), Zeitpunkt des Laufs" }, { "von": 2, "nach": 3, "nutzlast": "channelLoopEnd sammelt die Ergebnisse aus getSlackMessages je Channel-Iteration (Kanten channelLoop zu getSlackMessages zu channelLoopEnd) und übergibt sie an messageAnalyzer (Kante output-success zu input-default): Nachrichten inklusive Thread-Antworten je Channel, dazu der berechnete Zeitraum aus calculateTimeWindow (oldest, latest, readableOldest, readableLatest)" }, { "von": 3, "nach": 4, "nutzlast": "Läuft im selben KI-Aufruf von messageAnalyzer: thematisch gruppierte Nachrichten ohne Small Talk als Zwischenergebnis vor der Kategorien-Extraktion" }, { "von": 4, "nach": 5, "nutzlast": "Ebenfalls im selben Aufruf: extrahierte Kategorien fließen in das strukturierte Ausgabeschema summary, success, message_count, key_topics" }, { "von": 5, "nach": 6, "nutzlast": "messageAnalyzer.output.structured.summary (bereits HTML formatiert) sowie calculateTimeWindow.output.readableOldest und readableLatest fließen in sendSummaryEmail (Kante output-success zu input-default) und füllen dort mailBody und mailSubject" } ], "voraussetzungen": [ "Team-Chat mit API- oder Bot-Zugang, zum Beispiel Slack, Teams oder Discord, mit Leserechten auf den Nachrichtenverlauf und den Channel-Metadaten der konfigurierten Channels", "Ausgabekanal für den Digest, zum Beispiel Gmail, Outlook, Notion oder ein dedizierter Channel", "Konfiguration von Channel-Liste beziehungsweise Channel-IDs, Zeitfenster und Output-Format", "LLM-Zugang per API-Key (OpenAI, Claude oder Gemini)" ], "fehlerbehandlung": [ { "fall": "Trigger, Zeitfensterberechnung, KI-Analyse oder Versand schlagen fehl", "massnahme": "Diese Knoten (dailyTrigger, calculateTimeWindow, messageAnalyzer, sendSummaryEmail) sind auf die Fehlerstrategie stop gesetzt. Ein Fehler dort beendet den gesamten Lauf, es wird kein unvollständiger oder leerer Digest versendet." }, { "fall": "Fehler beim Abruf eines einzelnen Channels", "massnahme": "Der Loop-End-Knoten (channelLoopEnd) steht standardmäßig auf continue. Ein Fehler in einem Channel wird übersprungen, die übrigen Channels werden trotzdem verarbeitet. Bei Bedarf lässt sich das auf stop umstellen, dann bricht ein einzelner Channel-Fehler den gesamten Lauf ab." }, { "fall": "Keine Nachrichten abgerufen", "massnahme": "Channel-IDs und Bot-Berechtigungen prüfen. Lauf mit Fehlerhinweis beenden, statt einen leeren Digest zu versenden." }, { "fall": "Kein relevanter Inhalt nach der Filterung", "massnahme": "Einen kurzen Hinweis versenden (Heute keine relevanten Diskussionen), statt einen leeren Digest zu erzeugen." }, { "fall": "Sehr hoher Traffic nahe am Token-Limit", "massnahme": "Zunächst pro Channel zusammenfassen und anschließend über alle Channel-Zusammenfassungen hinweg aggregieren." }, { "fall": "Digest zu lang oder zu kurz", "massnahme": "Eine explizite Längenvorgabe im Prompt ergänzen." }, { "fall": "Zu viel Small Talk rutscht durch", "massnahme": "Die Anweisung ergänzen, Small Talk konsequent zu ignorieren." }, { "fall": "Action Items ohne Verantwortliche", "massnahme": "Verantwortliche einfordern oder den Punkt als unklar markieren, statt zu raten." } ], "platzhalter": [ { "name": "CHANNEL_NACHRICHTEN", "quelle": "Dynamisch: gesammelte Nachrichten aus getSlackMessages über alle Channel-Iterationen (channelLoopEnd), inklusive Thread-Antworten" }, { "name": "ZEITRAUM", "quelle": "Dynamisch: calculateTimeWindow.output.readableOldest und readableLatest (technisch dahinter: oldest und latest im ISO-8601-UTC-Format für die Slack-API)" }, { "name": "UNTERNEHMENSNAME", "quelle": "Name des Unternehmens, vor der Aktivierung manuell festgelegt" }, { "name": "TEAMNAME", "quelle": "Name des Teams oder der Abteilung, vor der Aktivierung manuell festgelegt" }, { "name": "channelId (Channel-Liste in channelLoop)", "quelle": "Echte Slack-Channel-IDs, manuell einzutragen (zum Beispiel C06TGHU12AB), maximal 20 Channels pro Lauf" }, { "name": "mailRecipient", "quelle": "Empfängeradresse(n) des Digests, manuell einzutragen; der Platzhalter team@example.com muss vor dem Go-Live ersetzt werden" }, { "name": "cc / bcc", "quelle": "Optionale Felder in sendSummaryEmail, nur zu befüllen, wenn zusätzliche Empfänger in Kopie oder Blindkopie gewünscht sind" } ], "herausgeber": "Voyage Digital", "version": "2.0", "stand": "2026-07-26" }, "itemIcon": "mails", "recommended": [ { "slug": "posteingang-route", "category": "workflow", "name": "The Inbox Router", "teaser": "A workflow that automatically classifies incoming emails, applies the matching label, and immediately alerts you when something is urgent.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "status-bruecke", "category": "workflow", "name": "The Status Bridge", "teaser": "A workflow that pulls your project data every week and turns it into a ready status report covering progress, risks and delays, for you to review before it goes out.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "activity" }, { "slug": "google-drive", "category": "tool", "name": "Google Drive", "teaser": "Google's cloud file storage for documents, spreadsheets and presentations, with real-time collaboration, granular sharing and automation through the Drive API.", "domaene": "Betrieb & Projektmanagement", "logoFile": "google-drive.png", "logoEinzug": 1 }, { "slug": "aufgaben-raster", "category": "skill", "name": "The Task Grid", "teaser": "Reads meeting minutes, emails or other texts and extracts all open tasks, both explicit and implicit, with owners and deadlines.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "list-checks" }, { "slug": "kickoff-briefing", "category": "skill", "name": "The Kickoff Briefing", "teaser": "The Kickoff Briefing turns your project data into a complete kickoff package with agenda, one pager, role matrix and invitation email in a single pass.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "flag" }, { "slug": "pdf", "category": "skill", "name": "The PDF Workbench", "teaser": "The PDF Workbench bundles the full range of PDF work into one executable skill with real code execution, from merging and splitting to watermarking, encryption, form filling, and OCR on scanned pages.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "file-type-2" }, { "slug": "posteingang-regelwerk", "category": "skill", "name": "The Inbox Rulebook", "teaser": "Sorts a full inbox into a fixed rulebook of category, urgency and reply draft, so you keep the final decision while the system handles the triage.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "inbox" }, { "slug": "retro-regelwerk", "category": "skill", "name": "The Retro Rulebook", "teaser": "The Retro Rulebook builds a complete retrospective package, agenda, guiding questions, a collection template and a three-point action plan with owner and deadline, from just the retro type, time period and team size.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "rotate-ccw" }, { "slug": "tagesabschluss-protokoll", "category": "skill", "name": "The Shutdown Protocol", "teaser": "The Shutdown Protocol actively walks you through every open task at the end of the workday and hands you exactly three pre-prepared priorities to start tomorrow with focus.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "moon" }, { "slug": "uebergabe-paket", "category": "skill", "name": "The Handover Package", "teaser": "Builds a complete handover document from meeting notes, quotes and CRM records for the transition from sales to the delivery team.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "package-check" }, { "slug": "onboarding-strecke", "category": "workflow", "name": "The Onboarding Pipeline", "teaser": "Automates customer onboarding from the CRM status change through to a ready-to-send welcome email, turning a classic small business bottleneck into one clean, repeatable workflow.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "door-open" }, { "slug": "termin-bruecke", "category": "workflow", "name": "The Appointment Bridge", "teaser": "A workflow that reads incoming appointment requests, checks calendar availability, and drops a ready reply draft with three time proposals into the inbox for review before sending.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "calendar-check" }, { "slug": "okr-stratege", "category": "assistent", "name": "The OKR Strategist", "teaser": "Translates a top-level strategic goal into a complete OKR set with a qualitative objective, measurable key results, concrete initiatives and an alignment check that flags dependencies and risks.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "target" }, { "slug": "prozess-dokumentierer", "category": "assistent", "name": "The Process Documenter", "teaser": "Captures undocumented business processes through a structured interview and turns them into clear, visual process documentation with steps, decision points and responsibilities.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "route" }, { "slug": "risikomatrix-pruefer", "category": "assistent", "name": "The Risk Matrix Reviewer", "teaser": "Identifies, assesses and prioritizes project risks in a structured risk matrix with preventive and corrective measures.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "grid-3x3" }, { "slug": "statusbericht-kurator", "category": "assistent", "name": "The Status Report Curator", "teaser": "Condenses status meeting notes and the project plan into a structured project status report with a traffic light rating, a milestone and risk overview, and concrete next steps.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "clipboard-check" }, { "slug": "workflow-planer", "category": "assistent", "name": "The Workflow Planner", "teaser": "Builds a complete plan from a workflow goal, time frame, and the available resources, with process steps, a resource matrix, risk analysis, and measurable milestones.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "workflow" }, { "slug": "beschaffungs-sichter", "category": "assistent", "name": "The Supplier Scout", "teaser": "Scans the market for a requested product or service and returns a structured shortlist of potential suppliers with baseline information, as a starting point for closer vetting.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "shopping-cart" }, { "slug": "ist-soll-analyst", "category": "assistent", "name": "The Gap Analyst", "teaser": "Systematically compares the current state with the desired target, quantifies the gap between them, and derives initial prioritized actions.", "domaene": "Betrieb & Projektmanagement", "itemIcon": "git-compare" }, { "slug": "gmail", "category": "tool", "name": "Gmail", "teaser": "Gmail is Google's email service, offering mailbox access, powerful search, filter rules, AI-assisted drafting, and automation interfaces through the Gmail API.", "domaene": "Betrieb & Projektmanagement", "logoFile": "gmail.png", "logoEinzug": 1 } ] }