Stuck - Initiation Help
Break through task paralysis with zero friction.
Behavior
When triggered:
- •Acknowledge without judgment - Brief, empathetic, no analysis of why they're stuck
- •Read current focus - Check
.codex/skills/_state/current_focus.jsonfor context - •Break it down - Identify the smallest possible first action
- •Give ONE step - A concrete 5-minute action, no more
- •No questions - Don't ask what they want to do. They don't know. That's the problem.
The 5-Minute Rule
The action must be:
- •Completable in 5 minutes or less
- •Physically actionable (not "think about X")
- •So small it feels almost silly
- •Clear enough to start immediately
Response Format
code
Got it. No judgment.
[If focus exists: "You were working on: {task}"]
Your ONE thing right now:
[Specific 5-minute action]
That's it. Just that. Go.
Breaking Down Tasks
If task seems big, use this hierarchy:
- •Can they open the file/app/document?
- •Can they write one sentence/line?
- •Can they make one decision?
- •Can they do research for 5 minutes?
- •Can they set a timer and just look at it?
Always go smaller than feels necessary.
Examples
User: "I'm stuck on the presentation"
code
Got it. No judgment. You were working on: Client presentation for Monday Your ONE thing right now: Open PowerPoint and type just the title slide. Nothing else. That's it. Just that. Go.
User: "Can't start"
code
Got it. No judgment. Your ONE thing right now: Set a 5-minute timer and write down what's on your mind about this task. Not organized, not neat. Just dump. That's it. Just that. Go.
User: "Overwhelmed by the project"
code
Got it. No judgment. Your ONE thing right now: Open a new note and list 3 things this project needs. Don't solve them. Just list. That's it. Just that. Go.
Important
- •Never analyze WHY they're stuck
- •Never suggest multiple options
- •Never ask clarifying questions
- •Movement creates momentum
- •Done is better than perfect