Resolve Cycles
CFAR rationality technique using 5-minute time-boxed problem-solving to break through procrastination and analysis paralysis. Use when the user: (1) is overthinking and needs to just try solving something, (2) is stuck in analysis paralysis, (3) needs permission to attempt something imperfect, (4) wants to build problem-solving momentum, or (5) has a "bug" (life problem) that might be solvable with focused effort. Triggers: "resolve cycle", "just try it", "5 minutes", "stop overthinking", "analysis paralysis", "stuck", "procrastinating", "yoda timer", "bug hunt", "CFAR".
Install
npx skills add EquiStamp/CFAR-Claude-Skills --skill resolve-cyclesgit clone --depth 1 https://github.com/EquiStamp/CFAR-Claude-Skills.git /tmp/CFAR-Claude-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/CFAR-Claude-Skills/resolve-cycles ~/.claude/skills/resolve-cyclesPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Resolve Cycles
A CFAR technique using 5-minute time-boxed problem-solving to break through inertia. Deceptively simple but empirically effective: set a timer, actually solve the problem, stop.
## Three Modes
1. **Design Mode** — Help identify which problems ("bugs") are good candidates for resolve cycles
2. **Practice Mode** — Run a resolve cycle on a low-stakes practice problem
3. **Execute Mode** — Facilitate a real resolve cycle on an active stuck point
## Why It Works
Most procrastination isn't laziness — it's activation energy. People optimize for the *appearance* of trying rather than the *reality* of solving. Resolve Cycles strip away this appearance-management:
- **5 minutes is "safe"** — low psychological cost to invest
- **Bounded urgency** — creates deadline pressure without excess demand
- **Permission to succeed** — explicitly gives permission to actually solve the problem
- **No meta-cognition** — the ticking clock eliminates second-guessing
## Core Process
### Cycle 1: Solve It
1. **Identify the bug**: Any problem worth improving
2. **Set a real timer**: 5 minutes, audible alarm (important — don't use silent timers)
3. **Start immediately**: Don't prepare, brief, or explain. Just start.
4. **Actually solve**: Focus exclusively on solving until the timer sounds
### Cycle 2: Plan It (if Cycle 1 didn't fully solve)
If incomplete, spend another 5 minutes creating an actionable plan where each step fits into a 5-minute resolve cycle.Details
- Skill name
resolve-cycles- Repository
- EquiStamp/CFAR-Claude-Skills
- Path
resolve-cycles/SKILL.md- Repo updated
- 5 February 2026
FAQ
What does the Resolve Cycles skill do?
CFAR rationality technique using 5-minute time-boxed problem-solving to break through procrastination and analysis paralysis. Use when the user: (1) is overthinking and needs to just try solving something, (2) is stuck in analysis paralysis, (3) needs permission to attempt something imperfect, (4) wants to build problem-solving momentum, or (5) has a "bug" (life problem) that might be solvable with focused effort. Triggers: "resolve cycle", "just try it", "5 minutes", "stop overthinking", "analysis paralysis", "stuck", "procrastinating", "yoda timer", "bug hunt", "CFAR".
How do I install the Resolve Cycles skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add EquiStamp/CFAR-Claude-Skills --skill resolve-cycles. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Resolve Cycles popular?
It lives in EquiStamp/CFAR-Claude-Skills, which has 5 GitHub stars and 1 forks.
Related skills
Aversion Factoring
5EquiStamp/CFAR-Claude-Skills
CFAR rationality technique for decomposing aversions into specific addressable components using the LEGO brick model. Use when the user: (1) avoids something they believe they should do, (2) says "I hate doing X" and wants to understand why, (3) wants to overcome a specific aversion, (4) practice decomposing emotional resistance, or (5) wants to understand the gap between what they want to want and what they actually want. Triggers: "aversion factoring", "I hate", "I avoid", "I can't make myself", "why do I resist", "overcome aversion", "ugh field", "CFAR", "decompose aversion".
Bucket Errors
5EquiStamp/CFAR-Claude-Skills
CFAR rationality technique for identifying where you've entangled questions that should be separate, causing you to flinch away from evidence. Use when the user: (1) feels defensive about acknowledging something true, (2) conflates unrelated beliefs ("Am I a good writer?" with "Did I spell this correctly?"), (3) has trouble accepting feedback, (4) wants to practice detecting question substitution, or (5) notices they avoid thinking about certain topics. Related to Kahneman's attribute substitution. Triggers: "bucket error", "conflating", "flinching away", "defensive about", "question substitut
Double Crux
5EquiStamp/CFAR-Claude-Skills
CFAR rationality technique for resolving disagreements by finding shared underlying belief divergence points (cruxes). Use when the user wants to: (1) resolve a disagreement by finding the real point of contention, (2) prepare for a difficult conversation by mapping belief structure, (3) practice collaborative truth-seeking, (4) examine beliefs by finding what would change their mind, or (5) facilitate a structured disagreement between two positions. Triggers: "double crux", "disagree", "what would change my mind", "crux", "resolve disagreement", "find the real issue", "belief examination", "C
Sy Trace Plan
9jscraik/Agent-Skills
Plan traceable work bullets that connect intent, evidence, acceptance, and proof gaps. Use when an idea or reframe needs decomposition into traceable work units before tracker or slice specification.
Pride Self Recognition
5EquiStamp/CFAR-Claude-Skills
CFAR rationality technique for discovering authentic values by converting frustrations and annoyances into positive value statements. Uses iterative loop of expressing annoyance, finding the underlying value, re-expressing, and checking if the emotional charge has shifted. Use when the user: (1) is frustrated or annoyed and wants to understand why, (2) wants to discover what they really care about, (3) needs to move from self-criticism to self-recognition, (4) wants to identify their authentic values (vs. "shoulds"), (5) practice converting complaints into values, or (6) wants to understand th
Sy Tracker Plan
9jscraik/Agent-Skills
Plan tracker-ready slices with dependencies, labels, acceptance fields, and validation placeholders. Use when trace work needs Linear-ready or tracker-ready issue structure without actually mutating the tracker.
Browse the most popular Claude skills, all other skills, or write your own with the skills generator.