helfen-industries/obsidian-vault
v0.2.0MIT
Workflows for a personal Obsidian knowledge vault with customer and project fact sheets, decisions, concepts, processes, meeting notes, and tasks
Changelog
All notable changes to this plugin are documented here.
[0.2.0] - Unreleased
Added
- Appointment workflow (
vault-appointment-create): creates an appointment in the user's Outlook calendar from a vault note or a direct request through the vault's99-System/Skripte/Export-Termin.ps1and the Power Automate flowVault-Terminexport. It shows a-WhatIfpreview first, sends invitations only after explicit confirmation of the listed attendees, never invents dates, durations, or attendee addresses, adds theobsidian://note link only to appointments without attendees, checks the flow result with-Status, and after confirmation appends the returned line under## Termineof the source note.
[0.1.0] - Unreleased
Added
- Plugin README with the working concept for a personal Obsidian vault: knowledge and delivery layers, vault contract, customer resolution, change gates, Git handling, and concept-to-spec alignment.
- Read-only customer context brief (
vault-customer-context) with deterministic customer resolution by name, alias, repository path, Git remote, or DevOps project. - Shared write discipline (
vault-note-write) with search-before-create, template handling, change gates for fact sheets and decided ADRs, vault check, scaffold-only local commits, and push only on request. - Workflows for meeting notes, concepts in technical-spec Part A structure, ADRs, customer fact sheets, process documentation, and vault maintenance with inbox triage.
- Scripts:
Get-VaultCustomerContext.ps1,Test-VaultNote.ps1, and the read-only repository scannerGet-RepoFacts.ps1. - Task workflow (
vault-task-create): tasks for the vault's task board from a mail pasted in chat, from an Azure DevOps work item throughado-remote-mcpor the vault'sImport-DevOpsAufgabe.ps1, or by converting an imported inbox mail (## Inhaltbecomes## Auftrag,## Anhängestays); every new task starts withstatus: inbox.
Changed
- Vault structure: numbered folders
00-Inbox,10-Kunden,20-Projekte,30-Agents,80-Daily,90-Templates, and99-System; the vault root is recognized byAGENTS.mdand10-Kunden/. Test-VaultNote.ps1checks customers and internal projects, the typesaufgabe,problem,session,katalog,anweisung, andlearningwith their folders and status values, task fields (quelle,faellig,start/endeasYYYY-MM-DDTHH:mm,mail-*,devops,devops-link,## Auftrag),projektunder20-Projekte, and neverkundetogether withprojekt. Unknown source values may beoffen. System files (AGENTS.md,Dashboard.md,Task Board.base,90-Templates/,99-System/,Excalidraw/) are skipped.- Git: notes are excluded by the vault's
.gitignoreand are never committed or forced withgit add -f; workflows commit only scaffold they create and reportnicht versioniertfor notes. vault-customer-contextresolves projects as well, lists open tasks (statusother thanarchiv), and lists matching appointments of the next 7 days from the generated Outlook calendar with subject and time only.vault-profile-updatecreates and refreshes project fact sheets from90-Templates/Projektsteckbrief.md, creates the subfolders with.gitkeep, and proposes adding a new name to the lists inAGENTS.md.vault-maintenanceignores system and generated files, reviews imported mails in00-Inbox/as task, knowledge, or deletion for customers and projects, and reports tasks without a valid status.- Meeting, concept, and decision workflows accept internal projects; processes stay customer-only as defined in
AGENTS.md.