constraint-preflight
Pre-flight verification for scheduling constraint development. Use when adding, modifying, or testing constraints to ensure they are properly implemented, exported, registered, and tested before commit.
Security Assessment
Detected risks:
About constraint-preflight
The constraint-preflight skill provides a pre-flight verification process for scheduling constraint development. It addresses a common problem in constraint-based scheduling systems where constraints are created, tested, and exported but fail to be registered in the ConstraintManager, resulting in constraints not being applied during schedule generation. This skill ensures that all constraints are properly implemented, exported, and registered before committing changes, preventing the "implemented but not registered" issue that can disrupt schedule accuracy.
Key features of this skill include verification of constraint registration within the ConstraintManager, checking the hierarchy of soft constraint weights, and ensuring consistency across different manager methods such as create_default() and create_resilience_aware(). It validates that constraints in the prescriptive layer are correctly influencing schedule generation, while also providing clarity on how these changes interact with the descriptive layer represented by existing assignments. The skill integrates with existing testing workflows, complementing unit tests by confirming that constraints are not only logically correct but also actively used by the scheduler.
This skill is primarily used by developers and engineers working on scheduling systems who add or modify constraints. It is valuable before committing changes to version control, particularly in environments where schedules are critical and must adhere to strict rules. Typical use cases include creating new constraints, updating existing ones, verifying proper registration after exports, and running pre-commit checks to prevent oversights that could compromise schedule generation. It is suitable for teams using Python-based scheduling frameworks and those who need robust validation processes for constraint management.
FAQ
When should I run the constraint-preflight verification?
You should run it whenever creating new constraints, modifying existing ones, or before committing any constraint-related changes to ensure they are properly registered and implemented.
Does this skill automatically update existing assignments?
No, changes to constraints only affect the prescriptive layer. Existing half-day assignments must be regenerated manually to reflect constraint changes.
Which layers does this skill check?
It primarily verifies constraints in the prescriptive layer, ensuring they influence schedule generation correctly, while also considering their impact on the descriptive layer during testing.
What requirements exist for using this skill?
It requires a Python-based scheduling system with constraints exported in __init__.py and registered in ConstraintManager methods. The skill assumes a standard directory structure for constraints.
Can this skill detect missing tests for constraints?
No, it does not check the correctness of constraint logic tests. It verifies that exported constraints are registered and consistent across manager methods.
Install constraint-preflight
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
