decision-queue
Skill0 starsChanged 5 months agoMITView on GitHub
Forces decisions instead of letting them rot. Use when the operator says "decision", "I need to decide", "park this", "I'll think about it later", "add to queue", "what decisions am I dodging", or any time the operator tries to defer something without a deadline. Logs decisions with hard deadlines and surfaces stale ones.
In this repository9 other files it gives its agents.
- coordinatorSkill
- discovery-sprintSkill
- hair-productSkill
- midday-pulseSkill
- morning-briefSkill
- nightly-wrapSkill
- permissionsSkill
- revenue-experimentSkill
- venture-triageSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 6 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 30
When the operator says "park this" or "I need to decide X later":
- Distinctive: line 39
When the operator says "what decisions am I dodging" or invoked by morning-brief:
- Very specific: line 41
Read decisions.md Pending section.
- Distinctive: line 54
When the operator makes a call:
- Very specific: line 56
Write the outcome to decisions.md Resolved section.
- Very specific: line 57
If the decision spawned action items, push them to today's or tomorrow's top-3.md.
- Distinctive: line 63
Bias toward reversible decisions: When stakes are low, force a fast call.
- Distinctive: line 64
Bias against re-litigating: If a decision was resolved <30 days ago and the operator wants to re-open it, ask what changed.
- Distinctive: line 65
Surface chronic deferrers: If the operator has extended the same decision twice, force-close it.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Decision Queue
The single most important skill for the operator's productivity. ADHD + 10 ventures = decision avoidance. This kills that.
State file
~/Vault/Vantage-OS/decisions.md
Schema (markdown):
## Pending
- [ ] [Decision question] | Owner: the operator | Due: YYYY-MM-DD | Venture: [name] | Stakes: [low/med/high] | Notes: [optional]
## Resolved (last 30 days)
- [x] [Decision] → [outcome] | Closed: YYYY-MM-DDWhen invoked
Adding a decision
When the operator says "park this" or "I need to decide X later":
- Force a question, not a topic. Reject "think about the website" - require "should the website launch with 1 product or 3?"
- Force a deadline. No "soon" or "later." Get a specific date. Default to 7 days if the operator won't commit. Bigger stakes get more time (up to 21 days). Low-stakes decisions get 3 days.
- Force stakes. Low (reversible), Medium (some cost to undo), High (binding or capital).
- Append to
decisions.mdPending section.
Reviewing the queue
When the operator says "what decisions am I dodging" or invoked by morning-brief:
- Read
decisions.mdPending section. - Sort by:
- Overdue (red flag)
- Due within 48h
- Due this week
- Due later
- For each overdue decision: do not let the operator scroll past. Force one of:
- Decide now (write outcome, move to Resolved)
- Extend deadline ONCE with reason. Second extension is an automatic decision: drop it.
- Drop it (mark as "not deciding, accepting default")
Resolving a decision
When the operator makes a call:
- Write the outcome to
decisions.mdResolved section. - If the decision spawned action items, push them to today's or tomorrow's
top-3.md. - Note: the outcome is logged for accountability. In future triage, surface any pattern of bad decisions or chronic deferral.
Quality rules
- One decision = one question. "What should I do about the website" is rejected. "What's the v1 product count: 1, 2, or 3?" is accepted.
- Bias toward reversible decisions. When stakes are low, force a fast call. Don't waste a 7-day window on a 5-minute decision.
- Bias against re-litigating. If a decision was resolved <30 days ago and the operator wants to re-open it, ask what changed. If nothing changed, reject the re-open.
- Surface chronic deferrers. If the operator has extended the same decision twice, force-close it.
Default deadlines by stakes
| Stakes | Description | Max time |
| Low | Reversible in <1 hr, <$50 cost | 3 days |
| Medium | Some commitment, $50-500 cost | 7 days |
| High | Binding, >$500, or affects partners | 14 days |
| Critical | Capital, contracts, family business risk | 21 days max |
Output examples
Adding:
Logged: "Should the hair product launch with 1 SKU or 2-3 SKUs?"
Due: 2026-05-24 (7 days)
Stakes: High
Venture: Hair productSurfacing overdue:
⚠️ Overdue decisions
1. "Should I keep Volt or sell it?" - due 2026-05-10 (7 days overdue)
Options: decide now, extend (1 extension left), or drop (Volt stays)
2. ...Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

