| name | decisions-start |
| description | The front door to the Decisions pack: get unstuck when you cannot decide, cannot prioritise, or have lost the thread. Trigger on "help me decide", "cut my list to one", "I'm overwhelmed", "I'm stuck", "what should I do", "help me think this through", "should I start this", "where do I stand", or any open-ended request where the user is blocked on a choice or a list rather than on a specific task. You name the block; the OS reads your own files, then routes you to the move that clears it: weigh a real choice, gate a new idea, cut an overloaded list to one thing, read the state of your whole OS, or run the weekly reset. One honest disclaimer, reasoning only, and the call stays yours. Routes to decision-framework, forcing-questions, priority-triage, queue, strategic-read, strategic-analysis, or weekly-review depending on the block.
|
| why | A founder running alone has no chief of staff to think with, so decisions stall and lists grow until everything feels urgent. This is the one entry that reads which kind of stuck you are and routes to the move that clears it, instead of making you name the right skill while overwhelmed. |
| enhance | Keep context/priorities.md, brain/flags.md, and cadence/weekly-commitments.md current. The decision skills read your real state, so the more honest those files are, the sharper the call they help you reach. |
| summary | Name the block; the OS reads your own state and routes you to the move that clears it. |
| allowed-tools | ["Read","Bash"] |
| mcp_requirements | [] |
Decisions Start
Runs on: reasoning - this skill reads your own operating files and routes you to the member skill that clears the block. It reasons over what you already hold; it makes no external call and it does not make the decision for you. On a read-only or cloud surface, it explains the same route from the files it can read.
This is the front door for being stuck. There are a few kinds of stuck and they need different moves: a real choice between options, a shiny new idea you cannot tell is worth it, a list so long everything feels urgent, or a fog where you have lost the thread of where you stand. This skill reads which one you are in and points you at the move that clears it.
The principle: do the thinking with you, not for you. The OS reads your own state and structures the call; it never pretends to know your gut, your risk appetite, or what you can live with. It surfaces the decision clearly. You make it.
The kinds of stuck
| You are | What it means | Where it routes |
|---|
| Weighing a choice | a real decision between named options | decision-framework |
| Tempted by something new | a shiny idea you cannot tell is worth starting | forcing-questions |
| Drowning in a list | too many things, everything feels urgent | priority-triage (cut to one) |
| Capacity-blind | unsure what is actually on your plate right now | queue (the 3-item cap) |
| Lost the thread | you do not know where you stand across the whole OS | strategic-read |
| Sizing a market or rival | a strategic read of an opportunity or competitor | strategic-analysis |
| Due a reset | the week has drifted and needs a retro and re-plan | weekly-review |
Not sure which? Say "I'm just stuck" and the OS asks the one sorting question (is it one decision, one too-long list, or a general fog) and routes from your answer. When in doubt it runs strategic-read first, because seeing where you stand usually names the block for you.
Read the state before routing
The route is only as good as what it knows. Before choosing, read . If it is missing, or its line is more than 3 days old, run first and read the fresh one. The open-flags block tells you what is stuck, the must-do block tells you what this week is actually about, and the patterns block tells you what keeps happening - a front door that routes without them is a cold start at the exact moment the user is deciding whether this OS knows them. If Python is unavailable, route from the files you can read and say so.
