What problem does it solve? When something a user can see or feel changes in the program, the manual under docs/ often still describes the old state. This Skill keeps every chapter accurate in both English and German, and turns the manual-writing pass into a systematic review that finds program faults no test suite catches. ## Core Features & Use Cases - Bilingual chapter maintenance: Every chapter lives as docs/<name>.md (English) and docs/<name>.de.md (German); both must change together or text_no_german_left_test.py fails. - User-perspective review pass: Reading the program as a user uncovers dead switches, wrong messages, and missing tracks that green tests pass over; each chapter read produces one log line with text fixes and program findings counted separately. - Findings become tests: Every discrepancy found must become a test before the release tag, or a fully specified entry in docs/notes/aufgaben.md describing setup, assertion, and failure condition. - Use Case: After changing a default in the export dialog, use this Skill to update both language chapters, log the per-chapter review line, and file any out-of-scope program findings as tests instead of patching them in passing. ## Quick Start Update the manual chapters under docs/ in both English and German to reflect the recent UI change, and log one review line per chapter read.
