菜单
Project/Urgent/List/Limitations. Structured discovery before prescribing solutions. Understand the situation before acting. Activates on "what's the context", "tell me about the situation", "discovery", "understand before solving", "pull framework", or "what have you tried?"
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Capture a just-made decision into one durable record so the reasoning survives the session. Writes a single markdown file to the project's decisions/ folder: the call, the reasoning, the weakest assumption, what would change the verdict, and when to reuse the pattern. Checks for an existing record on the same decision and updates it instead of creating a near-duplicate. Activates on "codify this decision", "record this decision", "save the decision record", "make this decision durable", or right after a kill-go verdict, decision-brief, or /decide session.
7-move decision gate for AI deployment. Prevents early promise from becoming unquestioned infrastructure. Based on Stuart Winter-Tear's AI Graduation Path. Activates on "AI deployment", "graduation", "should we scale this AI", "pilot to production", "AI governance", "prove this works", or "when is this ready?"
3 diagnostic questions for evaluating any industry, market, or business model through the lens of arbitrage gaps. Identifies durable advantages vs. closing ones. Based on Nate Jones' Arbitrage Gap Framework. Activates on "arbitrage", "competitive advantage", "moat", "durable advantage", "market gap", "industry analysis", or "what gap am I exploiting?"
Extract and rank assumptions from any plan, idea, or strategy. Identifies what to test first. Anti-sycophancy tool — surfaces beliefs the user treats as facts. Activates on "what am I assuming", "assumptions", "what could go wrong", "blind spots", "stress test my thinking", or "what haven't I considered?"
A 20-minute pressure test for B2B ideas, positioning angles, offers, content theses, product bets, and client recommendations. Built for PMMs, product managers, founders, consultants, writers, and editors who need a strong sounding board before committing. Activates on "vet this idea", "pressure-test this angle", "should I pursue this", "is this positioning any good", "validate this offer", or "help me decide if this is worth it."
One-page decision brief that passes the Simple/Surprising/Easy test. Turns a messy decision into a constraint that generates action. Based on Alex MH Smith's creative brief framework. Activates on "write a brief", "decision brief", "one-pager", "clarify the direction", "what's the constraint", or "make this simple."
| name | pull-framework |
| version | 1.0.0 |
| description | Project/Urgent/List/Limitations. Structured discovery before prescribing solutions. Understand the situation before acting. Activates on "what's the context", "tell me about the situation", "discovery", "understand before solving", "pull framework", or "what have you tried?" |
| user-invocable | false |
Ask each in order. Don't prescribe solutions until all four are answered.
"What are you working on?"
Get the full picture. Not just the task, but the context. What's the project? What's the goal? Who's involved? What stage is it at?
If the user jumps to a narrow problem, zoom out first: "Before we dig into that — what's the bigger thing this is part of?"
"What's urgent about it?"
Why now? What's the deadline? What breaks if this doesn't get resolved? Is the urgency real (external deadline, user impact) or perceived (internal pressure, perfectionism)?
If nothing is urgent, that's useful information. It means there's time to think properly instead of reacting.
"What have you tried?"
Everything attempted so far. What worked partially? What failed completely? What did you learn from each attempt?
CRITICAL: People often skip what they've already tried and go straight to "help me solve this." Pull it out. Prior attempts contain signal about what the real problem is.
"What's not working? What constraints are you operating under?"
What's blocking progress? Resource constraints? Technical limitations? Organizational politics? Knowledge gaps?
Separate constraints you can change from constraints you must accept. The strategy looks different for each.
Only after all four questions are answered, synthesize:
# Discovery Brief: [Topic]
Date: [date]
## Project
[What they're working on, in context]
## Urgency
[Why now, real vs. perceived]
## Prior Attempts
[What's been tried, what was learned]
## Limitations
[Changeable vs. fixed constraints]
## Actual Problem
[Restated after discovery — may differ from initial framing]
## Recommended Next Step
[One specific action]
Based on the PULL Framework. Understand before prescribing.
Problem discovered → run problem-framing to diagnose deeper, or preflight if you're ready to scope a session.
Part of the ThinkHaven Method Kit by Kevin Holland. Full Board of Directors experience: ThinkHaven