Safe schedule generation with mandatory backup. REQUIRES database backup before any write operations to schedule tables. Use when generating schedules, bulk assigning, or executing swaps.
Detected risks:
The Safe Schedule Generation skill provides a controlled and secure approach to generating and modifying schedules in a database-backed environment. Its primary purpose is to ensure that any operation affecting schedule tables, such as creating new schedules, bulk assignments, or executing swaps, is executed only after a verified backup has been created. This approach mitigates the risk of data loss or corruption, protecting both historical records and manual overrides. By enforcing strict pre-flight checks, this skill ensures that schedule modifications are safe and auditable, preserving the integrity of the canonical assignment records.
Key features include mandatory backup verification before any write operation, checks on backend health, and validation of required data such as people and rotation templates. It distinguishes between prescriptive and descriptive truths, reading from `rotation_templates` and `weekly_patterns` and writing results to `half_day_assignments`. The skill tracks the source of each assignment slot to ensure human overrides and preloaded data are not inadvertently overwritten. Additionally, it enforces backup safety rules, including minimum retention policies, protection of initial backups, and user-confirmed cleanup operations.
This skill is intended for schedule administrators, system operators, or any user responsible for maintaining rotation assignments in healthcare or similar environments where accurate scheduling is critical. Typical use cases include generating new weekly schedules, performing bulk assignments of personnel to rotations, executing swaps between scheduled slots, and clearing or regenerating assignment blocks. By following the mandatory pre-flight checklist, users can safely perform these operations without risking data loss or compromising audit trails.
You must verify that a recent backup exists, ensure the backend service is healthy, confirm necessary data such as people and rotation templates exist, and obtain explicit user confirmation before proceeding.
The skill reads from `rotation_templates` and `weekly_patterns` and writes to `half_day_assignments`. Any operation that modifies the `assignments` table requires backup verification.
No, it must be serialized with schedule-optimization, SCHEDULING, solver-control, and swap-management tasks to avoid conflicts.
If no recent backup exists or the backup check fails, all schedule modification operations are blocked until a verified backup is created.
Schedule administrators, system operators, or anyone responsible for managing rotation assignments in environments requiring strict data integrity and auditability should use this skill.
Quick Setup:
.claude/skills/