aiwf-set-priority

Sets or clears priority levels on gap and decision entities via atomic commits.

Updated May 9, 2026
One-click install
npx skills add https://github.com/23min/aiwf --skill aiwf-set-priority-23min
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiwf-set-priority
Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded/aiwf-set-priority
Command: npx skills add https://github.com/23min/aiwf --skill aiwf-set-priority-23min

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about aiwf-set-priority

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I change the priority of a gap or decision in aiwf?

Run `aiwf set-priority <id> <level>` where level is one of urgent, high, medium, or low. To remove the priority entirely, run `aiwf set-priority <id> --clear`. The change is written to frontmatter and committed in a single atomic commit.

What priority levels does aiwf set-priority support?

The verb accepts a closed set of four levels: urgent, high, medium, and low. Passing any other value is refused with a message naming the allowed levels, and `--clear` is mutually exclusive with a level argument.

Can I set priority on an epic, milestone, ADR, or contract?

No. Priority is scoped to gap and decision entities only. Running set-priority on an epic, milestone, ADR, or contract is refused with a message naming the two kinds that carry priority.

Why not just edit the priority field in frontmatter directly?

Hand-editing bypasses the verb layer, so `aiwf history` will not show the change and the next `aiwf check` reports a `provenance-untrailered-entity-commit` warning. The verb records the mutation with proper commit trailers.

What happens if I set a priority the entity already has?

The verb reports nothing to change and exits with status 0 without creating a commit. The same applies when running `--clear` on an entity whose priority is already unset.