claude/skills/woop/SKILL.md
Guide users through the WOOP goal-setting framework (Wish, Outcome, Obstacle, Plan) by Gabriele Oettingen. Use when someone wants to set a goal, create an action plan, build a new habit, or work through behavior change using mental contrasting and implementation intentions.
npx skillsauth add strager/dotfiles woopInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
WOOP is a science-based mental strategy developed by psychologist Gabriele Oettingen (NYU). It combines positive visualization with mental contrasting - acknowledging obstacles - which research shows is more effective than positive thinking alone.
Use the AskUserQuestion tool throughout. Take one step at a time. Do not rush.
Goal: Identify a specific, meaningful, challenging-but-feasible goal.
Goal: Deeply explore the best possible result. This step is critical for motivation - spend 2-3 exchanges here.
Do not rush this phase. The vividness of the outcome visualization drives motivation.
Goal: Identify the main INTERNAL obstacle. Explore multiple, then narrow to one.
Goal: Create a specific if-then plan that directly addresses the chosen obstacle.
CRITICAL: You must explicitly reference the obstacle they chose.
Research note: Implementation intentions (if-then plans) have been shown to roughly double the success rate of goal achievement.
## Your WOOP
**WISH**: [Their specific goal]
**OUTCOME**: [Best result - include both emotional and practical benefits discussed]
**OBSTACLE**: [Their chosen main internal barrier]
**PLAN**: "If [obstacle situation], then I will [specific action]."
---
### Key Reminders
- [Personalized insight extracted from discussion]
- [Another relevant insight]
- [Research-backed tip relevant to their specific goal]
Sometimes the user's ultimate wish is too ambitious to tackle directly. The gap between where they are now and where they want to be is too large, or there's a foundational obstacle blocking everything downstream. In these cases, help them create a phased WOOP - a Phase 1 goal that builds toward their ultimate wish.
Watch for these indicators during the Obstacle phase:
| Sign | Example | |------|---------| | The obstacle is upstream of the goal | User wants to "date consistently" but the real barrier is social anxiety that prevents approaching anyone | | Skills or confidence are missing | User wants to "give a TED talk" but has never spoken publicly | | The if-then plan feels unrealistic | When you propose actions, user says "I don't think I could actually do that" | | User needs evidence, not belief | User won't adopt positive self-talk; they need real-world data to shift their beliefs | | The gap feels paralyzing | User seems overwhelmed when discussing concrete next steps |
If you notice these signs, ask:
"It sounds like there might be a foundational step before [ultimate goal]. Would it help to break this into phases - a Phase 1 that builds the skills/confidence you need, then a Phase 2 that tackles the bigger goal?"
If the user agrees, restructure the WOOP:
## Your WOOP
### Ultimate Wish
[Their long-term goal - the north star]
**Why it matters**: [Core motivation from Outcome phase]
---
### Phase 1: [Name the foundation being built]
**WISH**: [Stepping-stone goal with clear success signal]
**OUTCOME**: [Benefits of completing Phase 1, including readiness for Phase 2]
**OBSTACLE**: [The foundational internal barrier]
**PLAN**: "If [obstacle situation], then I will [specific action]."
---
### Key Reminders
- [Personalized insights]
- When [success signal], you're ready for Phase 2
Phasing can become a way to avoid the real goal indefinitely. Mitigate this by:
| Situation | Response | |-----------|----------| | External obstacle given | "That's a real challenge, but for WOOP we focus on internal obstacles. What's something within you (a habit, feeling, or belief) that makes [external obstacle] harder to handle?" | | Vague answers | "Let's get more specific. When exactly does this happen? What triggers it?" | | Wants to skip ahead | "Let's slow down - the research shows each step matters. Can you tell me more about [current step]?" | | Multiple obstacles at once | "Those are all valid. Let's explore each briefly, then identify which one is the biggest barrier." | | Goal seems too ambitious | "It sounds like there might be a foundational step first. Would it help to break this into phases?" |
Use these to provide science-backed context and validate user choices:
development
Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.
development
Maintainer workflow for OpenClaw releases, prereleases, changelog release notes, and publish validation. Use when Codex needs to prepare or verify stable or beta release steps, align version naming, assemble release notes, check release auth requirements, or validate publish-time commands and artifacts.
development
Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.
development
End-to-end Parallels smoke, upgrade, and rerun workflow for OpenClaw across macOS, Windows, and Linux guests. Use when Codex needs to run, rerun, debug, or interpret VM-based install, onboarding, gateway smoke tests, latest-release-to-main upgrade checks, fresh snapshot retests, or optional Discord roundtrip verification under Parallels.