Skip to content

Classification and Priority Guide

Priority Matrix

Priority Criteria
hoch Compliance-critical, certification blocker, regulatory deadline, security gap
mittel Quality improvement, process gap, cross-ref improvement, content deepening
niedrig Nice-to-have, cosmetic, optimization, knowledge base enrichment

Evaluation Criteria

Automated checks run during the evaluate step:

  1. YAML Completeness — Verify required aufgabe fields (title, type, management_system, classification, status) and vorschlag-specific fields (kategorie, quelle, erstellt_am) are present
  2. Norm Reference Validation — Extract norm references from body text (e.g. ISO 9001 7.1.6, DSGVO Art. 33) and validate against known prefixes
  3. Duplicate Detection — Search the target vault area for files with overlapping title keywords (2+ matches) or matching norm references
  4. Scope Estimation — Count .md files in the target vault area to estimate effort:
  5. klein: 1-5 files
  6. mittel: 6-20 files
  7. gross: 20+ files
  8. Dependency Mapping — Find vault files across all areas that reference the same norms, to identify cross-cutting concerns

Triage Decisions

Accept (Small) — stays as aufgabe

  • Single file fix or update
  • Clear scope, estimable in < 2 hours
  • Set zustaendig, frist, prioritaet
  • Add Umsetzungsschritte checklist to body

Accept (Large) — create GitHub Issue

  • Multi-file change (5-20 files)
  • Needs coordination or research
  • Create GitHub Issue with IMS label
  • Add issue URL to aufgabe body as reference
  • Set zustaendig and frist on the aufgabe

Accept (CWP) — create Content Work Package

  • 20+ files affected or new domain area
  • Requires structured sprint approach
  • Flag for CWP creation in .content-state.yaml
  • Use /vt-v-cwp to set up the new CWP

Defer

  • Valid item but not urgent
  • Set frist to a future triage date (e.g. 3 months out)
  • Add note in body explaining deferral reason
  • Keep status: offen, keep zustaendig: null

Reject

  • Not applicable, duplicate, or out of scope
  • Set status: erledigt
  • Set erledigt_am to today
  • Add note explaining rejection reason

Source-Based Priority Hints

Source Default Priority
regulatorisch hoch (regulatory deadlines are fixed)
vorfall hoch (prevent recurrence)
audit mittel (systematic improvement)
management-review mittel (strategic direction)
gap-analyse mittel (proactive closure)
team niedrig (unless compliance-related)