What problem does it solve? Developers working on the HumanOS HR platform risk violating critical business rules (R1-R27) when writing database migrations, RLS policies, approval chains, or auth.users operations, which can cause data loss, broken approval flows, or security exposure of sensitive employee documents. ## Core Features & Use Cases - Blocking-rule checklist: Flags immediately blocking violations such as writing to prohibited schemas (public., humanos.), self-approval, exposing restricted medical documents, and unfiltered destructive operations on auth.users. - Approval chain guidance: Details ticket status transitions, approval JSONB structure, SOP-driven chain fidelity rulings (ADR-0027), stamp formats, and back-and-forth modification flows. - Use Case: Before writing a migration that adds an approval step for a PRESTAMO ticket, consult this Skill to confirm the full chain (supervisor + hr_admin + president) applies with no threshold logic, and that the stamp format and request_number generation follow R7 and R17. ## Quick Start Ask the agent to review your planned migration or approval logic against the ICONSA business rules before writing any SQL touching the HumanOS database.
