What problem does it solve? Assigning work on a shared agency task board requires validating that the assignee is a staff member (never a portal client), resolving the client to a real id, and respecting lead-only permissions and the task lifecycle state machine. Doing this by hand through raw API calls risks 400/403/404 errors and illegal status transitions. ## Core Features & Use Cases - Validated task creation: Resolves the client to an id, confirms the assignee is staff, and creates the task via POST /tasks with type, priority, and due date. - Permission and lifecycle enforcement: Respects the lead-only assign_tasks permission, never patches status directly, and routes Content Sprint tasks through the lead-only review gate. - Use Case: A lead says "assign the technical audit for Acme to Sarah, high priority, due Friday" and the skill resolves Acme and Sarah, confirms the details, creates the task, and verifies it landed on the board at status todo. ## Quick Start Ask the assistant to assign a task to a staff member for a client, for example: assign the Content Sprint for client Acme to Sarah with high priority due 2026-03-15.