Auto-Adaptive Priority Memory
This skill auto-evolves. Observe prioritization signals, detect patterns, confirm before internalizing.
Core Loop:
- Assess — When tasks arrive, evaluate urgency + importance
- Classify — Assign priority level (P0-P3)
- Route — P0 immediately, P1-P3 into queue
- Learn — Notice when user overrides priority → propose pattern
- Confirm — After 2+ corrections, ask: "Should X always be P[n]?"
Check signals.md for urgency indicators. Check patterns.md for learned priority rules.
Priority Levels
| Level |
Response |
Examples |
| P0 |
Interrupt immediately |
Server down, security breach, deadline today |
| P1 |
Next available slot |
Blocking work, waiting users, same-day tasks |
| P2 |
Scheduled queue |
Important but not urgent, planning, reviews |
| P3 |
Backlog |
Ideas, "someday", low-impact optimizations |
Default: When uncertain, ask. Start conservative, learn boundaries.
Urgency Signals
Automatic P0 triggers:
- Words: "urgent", "ASAP", "down", "broken", "emergency"
- Context: External deadlines, blocked team members
- Pattern: User previously escalated similar tasks
Automatic P3 triggers:
- Words: "when you have time", "no rush", "idea for later"
- Context: No deadline mentioned, exploratory
Entry Format
One line: pattern: priority (level) [context]
Examples:
deploy-issues: P0 (confirmed) [always urgent]refactoring: P2 (pattern) [user deprioritized 3x]docs-updates: P3 (confirmed) [explicit "low priority"]
Work Categories
Time Patterns
Source Routing
Overrides
Queue Management
When multiple tasks compete:
- Group by priority — P0 first, always
- Within same priority — Order by arrival or explicit sequence
- Report queue — "3 P1 tasks queued, handling X first"
- Re-triage on change — New P0 interrupts P1 work
Learning Triggers
Phrases that signal priority pattern:
- "This should be higher priority"
- "Drop everything and..."
- "This can wait"
- "Handle [X] before [Y]"
- "Not urgent" / "No rush"
After hearing these: Update entry, wait for 2nd occurrence, then confirm permanent rule.
Empty sections = still learning. Start conservative, observe corrections, propose only after patterns emerge.
1---2name: triage3description: Auto-learns to prioritize tasks by urgency, impact, and user patterns. Grows smarter with each decision.4---5
6## Auto-Adaptive Priority Memory
7
8This skill auto-evolves. Observe prioritization signals, detect patterns, confirm before internalizing.
9
10**Core Loop:**
111. **Assess** — When tasks arrive, evaluate urgency + importance
122. **Classify** — Assign priority level (P0-P3)
133. **Route** — P0 immediately, P1-P3 into queue
144. **Learn** — Notice when user overrides priority → propose pattern
155. **Confirm** — After 2+ corrections, ask: "Should X always be P[n]?"
16
17Check `signals.md` for urgency indicators. Check `patterns.md` for learned priority rules.
18
19---
20
21## Priority Levels
22
23| Level | Response | Examples |
24|-------|----------|----------|
25| P0 | Interrupt immediately | Server down, security breach, deadline today |
26| P1 | Next available slot | Blocking work, waiting users, same-day tasks |
27| P2 | Scheduled queue | Important but not urgent, planning, reviews |
28| P3 | Backlog | Ideas, "someday", low-impact optimizations |
29
30**Default:** When uncertain, ask. Start conservative, learn boundaries.
31
32---
33
34## Urgency Signals
35
36Automatic P0 triggers:
37- Words: "urgent", "ASAP", "down", "broken", "emergency"
38- Context: External deadlines, blocked team members
39- Pattern: User previously escalated similar tasks
40
41Automatic P3 triggers:
42- Words: "when you have time", "no rush", "idea for later"
43- Context: No deadline mentioned, exploratory
44
45---
46
47## Entry Format
48
49One line: `pattern: priority (level) [context]`
50
51Examples:
52- `deploy-issues: P0 (confirmed) [always urgent]`
53- `refactoring: P2 (pattern) [user deprioritized 3x]`
54- `docs-updates: P3 (confirmed) [explicit "low priority"]`
55
56---
57
58### Work Categories
59<!-- Task types and default priorities -->
60
61### Time Patterns
62<!-- Time-based rules: mornings, Fridays, etc. -->
63
64### Source Routing
65<!-- Priority by source: Slack vs email vs direct -->
66
67### Overrides
68<!-- User corrections that became patterns -->
69
70---
71
72## Queue Management
73
74When multiple tasks compete:
751. **Group by priority** — P0 first, always
762. **Within same priority** — Order by arrival or explicit sequence
773. **Report queue** — "3 P1 tasks queued, handling X first"
784. **Re-triage on change** — New P0 interrupts P1 work
79
80---
81
82## Learning Triggers
83
84Phrases that signal priority pattern:
85- "This should be higher priority"
86- "Drop everything and..."
87- "This can wait"
88- "Handle [X] before [Y]"
89- "Not urgent" / "No rush"
90
91**After hearing these:** Update entry, wait for 2nd occurrence, then confirm permanent rule.
92
93---
94
95*Empty sections = still learning. Start conservative, observe corrections, propose only after patterns emerge.*
modbender