← ClaudeAtlas

swiz-task-governancelisted

Understand and comply with swiz task governance enforcement
mherod/swiz · ★ 3 · Code & Development · score 56
Install: claude install-skill mherod/swiz
> **Note on task tools**: This skill uses canonical task tool names (`TaskCreate`, `TaskUpdate`, `TaskList`, `TaskGet`). If your environment uses different names, consult the Tool Equivalence table in CLAUDE.md. If no task tool is available, maintain an internal numbered checklist and skip task status calls. ## Purpose Invoke this skill when: - A PreToolUse hook blocked your Bash/Edit/Write with a task governance violation - You need to recover from a "no in_progress task" block - Your task buffer dropped below the required minimum - You are starting a new session and need to orient your task state ## Current Task State !`swiz tasks list 2>/dev/null || echo "swiz tasks unavailable"` ## The State Machine Tasks follow a strict one-way state machine: ``` pending → in_progress → completed ``` - **NEVER** skip `in_progress`. `pending → completed` is blocked by the `pretooluse-task-transition-validator` hook. - **NEVER** complete a task you just created without doing substantive work (no phantom completion). - Use `deleted` only to remove tasks that are genuinely obsolete — never to clean up governance violations. ## Buffer Requirements (enforced by `pretooluse-require-tasks`) The hook blocks **Bash, Edit, Write, and Skill** tool calls unless: 1. **≥ 1 task is `in_progress`** 2. **≥ 2 tasks are incomplete** (pending + in_progress combined) Maintain the buffer proactively — do not wait for a block to appear: - When pending count drops below 2: immediately call `TaskCreat