helfen-industries/obsidian-vault
Workflows for a personal Obsidian knowledge vault with customer and project fact sheets, decisions, concepts, processes, meeting notes, and tasks
Create an appointment in the user's Outlook calendar from a note of the personal Obsidian vault (C:\Dev\Knowledge) or from a direct request - through the vault's Export-Termin.ps1 and the Power Automate flow Vault-Terminexport - with a preview, invitations only after explicit confirmation, a status check of the flow result, and an optional line under
Create or revise a business concept (Konzept) for a customer requirement or an internal project in the Obsidian vault, structured like Part A of the technical specification - summary and intention, initial situation and context, target process as a Mermaid flowchart with numbered steps, scope, and key decisions - with sourced facts, open questions, and linked ADRs. Use when the user wants to draft, write, structure, review, or tighten a concept or solution idea for a customer or project, prepare a work item before specification, or compare a concept with an existing technical spec.
Load verified customer or project knowledge from the personal Obsidian vault (C:\Dev\Knowledge) - fact sheet, decisions in force, concepts, processes, open items, open tasks, and the customer's or project's Outlook appointments of the next 7 days - optionally focused on one Azure DevOps work item, as a short linked brief. Use when the user asks for "Kundenkontext laden", "Projektkontext", customer or project context, open tasks, upcoming appointments, or what was decided or agreed for a customer or internal project; when starting or analyzing work in a customer repository under C:\Dev\Customers or a project repository; and before writing a concept, meeting note, decision, task, or specification. Read-only.
Record, supersede, accept, or reject an architecture or business decision as an ADR in the Entscheidungen folder of a customer or internal project in the Obsidian vault, with context, decision, rejected alternatives, consequences, and sources. Use when the user says "Entscheidung festhalten" or "ADR anlegen", records an agreed solution, when a meeting or concept produces a lasting decision, or when an existing decision is replaced or withdrawn.
Check and tidy the Obsidian knowledge vault - validate frontmatter, filenames, ADR numbering, task status and fields, checkbox placement, template remnants, and links against the vault's AGENTS.md, report stale fact sheets and forgotten open items, and triage notes and imported mails in 00-Inbox to customers or projects as task, knowledge, or deletion. Use when the user asks to "Inbox aufräumen", "Mails sichten", "Vault prüfen", clean up, check, or tidy the knowledge base, asks which tasks have no valid status, or after many manual edits in Obsidian.
Turn raw meeting notes, bullet points, or a transcript into a structured meeting note in the Meetings folder of a customer or internal project in the Obsidian vault, with decisions, open questions, and todos in vault syntax, then propose ADRs for lasting decisions, fact-sheet updates, and answers to known open questions. Use when the user says "Meeting-Notiz ablegen" or "Protokoll", pastes notes from a customer or project meeting, workshop, or call, or asks to document what was discussed or agreed.
Write, update, move, or delete notes in the personal Obsidian knowledge vault (default C:\Dev\Knowledge) under the vault's AGENTS.md contract - locate the vault, resolve the customer or project folder, search before creating, fill templates and frontmatter, gate changes to existing facts, verify with the vault check, and commit only versioned scaffold files. Use from every vault workflow before any file change, and whenever an agent is about to create or change a Markdown note in the vault.
Document a customer's current (Ist) or target (Soll) business process in the Prozesse folder of the Obsidian vault with trigger, roles and systems, a Mermaid swimlane flowchart, numbered steps, variants, documents and interfaces, and open questions. Use when the user wants to describe, map, visualize, or compare a business process such as order handling, picking, purchasing, production, or invoicing for a customer, or prepare process knowledge for a concept.
Create or refresh a customer's or internal project's fact sheet (00-Steckbrief.md) in the Obsidian vault from verifiable sources only - local repositories read-only (app.json, BC build artifacts, apps and dependencies, Git remotes, plans folders), Azure DevOps projects, dated meeting notes, and explicit user statements - and check off answered open questions. Use when adding a new customer or project to the vault, when the user says "Steckbrief anlegen", "Projektsteckbrief anlegen", "Steckbrief pflegen", or "Steckbrief aktualisieren", after BC upgrades or new apps, or when the context brief reports stale or contradictory facts.
Create a task note (typ aufgabe) for the task board of the personal Obsidian vault (C:\Dev\Knowledge) - from a mail text pasted in chat, from an Azure DevOps work item ID or URL, or by converting an imported mail in 00-Inbox into a task - always with status inbox and filed under the customer's or project's Aufgaben folder. Use when the user says "Aufgabe anlegen", "Aufgabe aus dieser Mail", "Work Item als Aufgabe übernehmen", "aus der Inbox-Mail eine Aufgabe machen", pastes a mail to file in the vault, or when a meeting note or inbox triage produces a task with its own content.