--- name: furkastrasse-fps-autoprotocol description: "Furkastrasse-FPS-AutoProtocol: Fachplanersitzungen für Projekt 410.2725.10 Schaffhausen – WÜB Furkastrasse gemäss etablierter ERNE-Protokollgliederung aus Vorprotokollen erstellen und archivieren." version: 1.0.0 author: Hermes Agent license: MIT metadata: hermes: tags: [furkastrasse, fps, fachplanersitzung, erne, autoprotocol, project-specific, protocol, transcript] --- # Furkastrasse-FPS-AutoProtocol Use this skill whenever the user sends or references a **Fachplanersitzung / FPS / Fachplaner-Jourfix** for project **410.2725.10 – Schaffhausen – WÜB Furkastrasse**. This project is **not** to be forced into the generic FPS structure. Furkastrasse is already in an established running protocol series; future FPS protocols must follow the **existing Furkastrasse protocol structure from prior protocols**, especially the archived **Protokoll 28. Fachplanersitzung vom 10.06.2026**. ## Always load alongside - `fps-autoprotocol` for general transcript/protocol rules. - `document-productivity-workflows` for DOCX/PDF and ERNE-CI verification. - `knowledge-vault-workflows` for project archive/retrieval. ## Required project context files Also consult `references/furkastrasse-fps-user-approved-rules.md` for the user-approved FPS 29 correction: strict Furkastrasse FPS structure, latest optimized DOCX reference, and the rule that transcript/video/protocol-basis references must not appear in client-facing FPS protocols. Before generating any Furkastrasse FPS protocol, inspect: ```text ~/jarvis_memory/work/projects/furkastrasse/project.md ~/jarvis_memory/work/projects/furkastrasse/meetings/README.md ~/jarvis_memory/work/projects/furkastrasse/meetings/2026-06-10_fachplanersitzung_28_context/fps_structure_context.md ``` Use the archived PDF/text only when needed for details: ```text ~/jarvis_memory/work/projects/furkastrasse/meetings/2026-06-10_fachplanersitzung_28_context/artifacts/260610_hffi_Protokoll_28_Fachplanersitzung.pdf ~/jarvis_memory/work/projects/furkastrasse/meetings/2026-06-10_fachplanersitzung_28_context/artifacts/260610_hffi_Protokoll_28_Fachplanersitzung.txt ``` ## Truth-source rule For a new FPS, the new video/audio/provisional transcript is the truth source. The prior protocol is a **structure, role, continuity and pendenzen context**, not proof that the same facts still apply. - Do not copy old pendenzen blindly. - Continue old pendenzen only if the new transcript confirms, updates, or discusses them. - If the new meeting contradicts the old protocol, record the current meeting and mark the earlier point as superseded/unclear. - Never invent deadlines, owners, decisions, or status. ## Furkastrasse FPS standard structure Use this established order unless the user explicitly instructs otherwise. This is mandatory for Furkastrasse because the project already has an established running FPS protocol series: 1. Genehmigung Protokoll 2. Infos von Bauherrn / BauKo-Sitzung 3. Stand der Planung / offene Sachfragen 1. Architekt 2. Holzbau 3. Bauingenieur 4. Haustechnik 5. Elektroingenieur 4. Stand der Ausschreibungen 5. Termine 6. PQM, Q-Schwerpunkte Fachplaner 7. Pendenzen- und Beschlussliste 8. Infos an Bauherren / BauKo-Sitzung 9. Abwesenheit / Stv. 10. Nächste Sitzung Do **not** use the generic management-summary / Ampelstatus / risks-and-chances format for Furkastrasse FPS unless the user explicitly asks for it. The body should follow the previous Furkastrasse protocol style: Teilnehmerseite, Traktandenliste, then a through-running protocol table with section rows and concrete sub-items, plus a separate pendenzen/beschluss list. ## Header / participants / protocol conventions Use the prior Furkastrasse FPS convention. If the user provides an edited/optimized protocol, treat it as the latest formatting/wording reference for future Furkastrasse FPS documents. Important external-protocol rule: **Do not mention the transcript, Teams transcript, MP4/video recording, audio recording, or AutoProtocol/source basis inside the final FPS protocol** unless the user explicitly asks for a source note. These can be kept in internal archive metadata, but not in the client-facing protocol. Do not list the transcript or video as protocol attachments/beilagen. Latest user-approved Furkastrasse FPS formatting/wording reference: ```text ~/jarvis_memory/work/projects/furkastrasse/meetings/2026-07-01_fachplanersitzung_29/artifacts/260701_Furkastrasse_Protokoll_29_Fachplanersitzung_user_optimiert.docx ``` For future Furkastrasse FPS: use the MP4/audio/transcript only as internal truth source, generate the protocol in the established Furkastrasse table structure, then strip all source/protocol-basis references before delivery. - Project line: `Projekt: 410.2725.10 - Schaffhausen - WÜB Furkastrasse` - Protocol title: `Protokoll Fachplanersitzung` - Date/time and place, usually Teams. - Participants grouped as: - `Anwesend` - `Entschuldigt` - `Verteiler` - Use Kürzel/name/company/email style if the output format supports it. - Use legend: `I = Information, B = Beschluss, P = Pendenz`. - Main protocol table columns should follow the prior format where practical: - `Nr` - `Traktandum` - `Verantwortlich` - `Termin` - type/status `I/B/P` - Pendenzenliste should be separate and follow: - `Pos.` - `Datum` - `Pendenz` - `Verantwortlich` - `Termin` - `Erledigt` ## Known participant / Kürzel context from Protokoll 28 Use only for recognition and consistency; confirm against new meeting where possible. ### Anwesend in Protokoll 28 - `FRS` – Stefan Fritsche – ERNE AG Holzbau - `HÄM` – Martin Hänz – Hänz AG - `HOF` – Fiona Hoffbauer – ERNE AG Holzbau - `PAD` – Dario Papalo – Studio Oesch Papalo - `SAL` – Larissa Salis – WaltGalmarini AG Dipl. Ing. ETH SIA USIC - `SCL` – Lars Schwager – R+B engineering ag - `WEM` – Markus Wetter – EnGePlan AG Energie- und Gebäudetechnikplanung ### Entschuldigt in Protokoll 28 - `BÖO` – Olaf Böhme – ERNE AG Holzbau - `WIS` – Stefan Wick – R+B engineering ag ### Verteiler in Protokoll 28 - `GAM` – Marcel Gasser – ERNE AG Holzbau - `GRC` – Christian Gruber – Magma AG - `LIM` – Marcel Limbach – Timbatec Holzbauingenieure (Schweiz) AG ## Continuity points from Protokoll 28 These are useful continuity checks for the next FPS, not automatic carry-over items: - Architektur: Übersichtspläne in Ausführungsplanung überführen. - Architektur: Türliste korrigieren und freigeben bis 12.06.2026. - Bauingenieur: Zusätzliche Arbeitsfugen im Beton / Wände über Türen mit Arbeitsfuge im Sturz; gestalterische Freigabe mit Architektur klären. - Bauingenieur: Offerte Statik Betonfertigteile erwartet; Statik für erste Treppen dringend. - Haustechnik: Martin Hänz erstellt Durchbruchliste; Fertigstellung ca. in vier Wochen, danach Korrekturlauf. - Ausschreibungen vergeben: Abbruch/Tiefbau/Werkleitung/Baumeister, Schutzraum, Gerüst, Elektro, Heizung, Sanitär, Fertignasszellen, Aussentüren, Aufzüge, Fenster, Lüftung, Innentüren, Küchen, Schlosser-/Metallbau, Metalltüren Traforaum/Nebenräume/Keller. - Ausschreibungen ausstehend: Dacharbeiten, Betonfertigteile, Trockenbau, Estrich, Parkett/Fliesen, Maler, Tiefgaragentor, Umgebung. - Termine: Terminplan vom 18.12.2025 war in Protokoll 28 gültig. - Abwesenheiten: als Kontext prüfen, nicht automatisch übernehmen. ## Processing workflow for the next Furkastrasse FPS 1. Extract/read the new video/audio/provisional transcript. 2. Load Furkastrasse `project.md` and `fps_structure_context.md`. 3. If audio is present, transcribe with WhisperX/AutoProtocol; if provisional transcript is supplied, use it and only re-transcribe if needed for quality. 4. Create a cleaned transcript with time/speaker/technical statement traceability. 5. Reconcile current meeting against Protokoll 28: - mark continued pendenzen; - mark closed/resolved items only if explicitly stated; - add new discussed points; - do not preserve obsolete points as active. 6. Draft protocol in the Furkastrasse FPS structure above. 7. Produce user-facing DOCX and PDF. 8. Archive under: ```text ~/jarvis_memory/work/projects/furkastrasse/meetings/YYYY-MM-DD_fachplanersitzung_/meeting.md ~/jarvis_memory/work/projects/furkastrasse/meetings/YYYY-MM-DD_fachplanersitzung_/artifacts/ ``` 9. Update: ```text ~/jarvis_memory/work/projects/furkastrasse/meetings/README.md ~/jarvis_memory/work/projects/furkastrasse/project.md ``` ## ERNE CI/layout expectations - Prefer the established Furkastrasse/FPS protocol look over generic management-summary format. - Keep ERNE header/footer if a template is available. - Do not overload pages: keep sufficient header/footer clearance. - Tables must be readable and not clipped. - Generate PDF from final DOCX and verify via `pdfinfo`, `pdftotext`, and rendered-page visual QA. ## Output style Final protocol should be concise and formal, Swiss Hochdeutsch, no emojis inside the document. The chat status to the user may be concise with ✅/🧪 as usual.