What problem does it solve? Hand-editing the priority: frontmatter field on aiwf planning entities bypasses the verb layer, so the change never appears in aiwf history and the next aiwf check flags a provenance-untrailered-entity-commit warning. This Skill routes priority changes through the aiwf set-priority verb so every mutation is validated and committed with proper trailers. ## Core Features & Use Cases - Closed-set priority levels: Set a gap or decision to urgent, high, medium, or low, or clear the priority back to unset with --clear. - Validated, atomic commits: The verb refuses unknown ids, wrong entity kinds, and invalid levels, then writes exactly one commit carrying aiwf-verb, aiwf-entity, and aiwf-actor trailers. - Idempotent behavior: Requests that are already satisfied exit cleanly without committing, and any change reverses through the same verb. - Use Case: During backlog triage, tell the assistant "mark gap G-12 urgent" and the priority is updated, committed, and auditable in aiwf history. ## Quick Start Ask the assistant to mark a specific gap or decision as urgent, high, medium, or low priority, or to clear its existing priority tag.