Skip to content

vt-v-write

Write or enrich VMS content files in the VisiTrans vault. Routes to the appropriate domain expert agent (isms-expert, dsms-expert, qms-ims-expert) based on the file's management_system YAML field. Provides domain-specific reference material for accurate content creation. Use with a file path or glob pattern as argument.

Plugin: vms
Category: Other
Command: /vt-v-write

VMS Content Writer

This skill routes content writing tasks to the appropriate domain expert agent based on the target file's management_system YAML field.

Process

  1. Identify target files from the argument (path or glob pattern)
  2. Read YAML frontmatter of each target file to determine management_system
  3. Impact analysis (pre-write) — For each target file, run impact_analyzer.py from plugins/vms/skills/vms-audit/scripts/:
  4. Command: python3 impact_analyzer.py <vault_path> <target_file>
  5. Display the result to the author: "N files reference this file: [list with domains]"
  6. If zero references: display "No files reference this file"
  7. This helps the author understand the blast radius before making changes
  8. Load domain references from references/ directory:
  9. For ISMS controls: control-patterns.md, reifegrad-criteria.md, norm-mapping.md
  10. For DSMS content: vvt-exemplars.md, rechtsgrundlagen.md, tom-art32-reference.md
  11. For QMS/IMS: control-patterns.md (ISO 9001 section)
  12. Route to domain agent via Task tool:
  13. management_system: ISMS → isms-expert
  14. management_system: DSMS → dsms-expert
  15. management_system: QMS or IMS → qms-ims-expert
  16. Verify output — Check that YAML was updated and content body was enriched
  17. Impact analysis (post-write) — Re-run impact_analyzer.py for each written file:
  18. Command: python3 impact_analyzer.py <vault_path> <target_file>
  19. Display: "Check these N files for consistency with your changes: [list]"
  20. If zero references: skip this reminder

Domain References

Load these references before invoking the domain agent. Pass relevant content as context:

For ISMS Controls

  • references/control-patterns.md — Exemplary completed controls showing the target format
  • references/reifegrad-criteria.md — SPICE maturity level 0-5 decision criteria
  • references/norm-mapping.md — ISO 27001 ↔ VDA ISA ↔ NIS2 cross-reference table

For DSMS Content

  • references/vvt-exemplars.md — Example VVT entries for a SaaS company
  • references/rechtsgrundlagen.md — DSGVO Art.6/9 legal basis reference
  • references/tom-art32-reference.md — TOM categories with implementation guidance

For QMS/IMS Content

  • references/control-patterns.md — ISO 9001 section with exemplary controls

Batch Processing

When processing multiple files: - Group by management_system to minimize agent context switches - Process in batches of 20-30 files - After each batch, invoke /vt-v-audit --changed to validate

Important

  • Always read the target file FIRST before writing — understand its current state
  • Preserve existing Dataview queries, navigation links, and structure
  • Only fill in empty fields and add missing content
  • Write all content in German, following the VisiTrans tone of voice:
  • Use "wir" instead of passive constructions ("Wir prüfen..." not "Es wird geprüft...")
  • Use "du/ihr/euch" internally, never formal "Sie" (except in customer-facing or legal documents)
  • Short, direct sentences. Say what we do, not what we aspire to do
  • No corporate flourishes: never use "bekennt sich zu", "prägt unser Handeln", "zentrale Verpflichtung", "von entscheidender Bedeutung"
  • Descriptive headers ("Worum es geht") instead of bureaucratic ones ("Zielsetzung und Selbstverpflichtung")
  • Quick test: "Would a 15-person team in Hamburg actually write it this way?"
  • See vault/VMS/00 - Hilfe/VMS Hilfe/Handreichung- Schreibstil und Tonalität.md for full guidelines
  • Use [[wiki-links]] for cross-references to other vault files