department-scrum

Create a scrum.yaml in your profile directory with your team roster, Slack channel IDs, and brain cross-reference rules, then schedule three cron jobs: send-scrum-dms.py at 9am, check-scrum-replies.py warn at 11am, and report mode at 5pm.

The check-scrum-replies.py script reads the daily state file, detects missing replies via Slack conversation threads, sends DM warnings to non-responders at 11am, and posts a per-member compliance report with on-time, late, and missed counts at 5pm.

Yes, each department profile defines its own task_id_patterns regex and domain_terms in scrum.yaml, such as TS-20\d{2}-\d{3} for Projects or PO-\d+ for Finance. Cross-department isolation tests verify patterns never overlap between profiles.

YAML double-quoted strings interpret escape sequences, so \d causes a ScannerError. Always wrap regex patterns in single quotes, for example pattern: 'TS-20\d{2}-\d{3}', while non-regex fields can stay double-quoted.

Yes, a holiday gate uses an offline Hijri calendar algorithm covering Malaysian national holidays. On holidays the 9am, 11am, and 5pm jobs exit early, and an optional midnight cron job auto-pauses and resumes the scrum schedule.

Do not use it for ad-hoc meetings, sprint planning, backlog grooming, or non-scrum communication. It is designed specifically for structured daily standups with the 4 standard questions and compliance tracking.