vincent-triggerslisted

# vincent Triggers A trigger lets something other than a person start vincent work. An event from a poll script, from GitHub, or from a signed push can create a task, or follow up, retry or cancel the task on a branch. Nobody presses a key, so design the smallest trigger that is safe to leave on, and leave turning it on to a human. This skill covers four jobs: - authoring a trigger, - writing its poll script, - arming and debugging it, - migrating or reviewing existing triggers. ## The safety rule Every trigger you write starts disarmed and bounded: - `enabled: false`. - No `on_fire` line, so a fired event's task lands `paused` (`propose`). - No `permission` line, so a created task's agent steps run `restricted`. - An explicit `dedupe_key`. - `limits.max_per_hour`, plus `limits.max_task_cost_usd` on a `create_task`. Four switches arm a trigger or widen what it may do: - `enabled: true` - `on_fire: create` - `permission: workflow` - the global `triggers.enabled` in `config.yaml` Change one only when the user asks for that exact change. Never flip one to make something work, and say what it does before you write it. When they stay off, end by naming what a human must do to arm the trigger. Consequences of the rule: - **Cancel triggers.** A `cancel` action is refused at load unless it writes `on_fire: create`, because a cancel cannot be held for approval. Write one only when the user asks for exactly that. Otherwise explain this and write nothing. - **No `contai