Back to Details

use-framework

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Use Framework - Strategic Framework Application

使用框架 - 战略框架应用

Overview

概述

This skill guides users through applying strategic frameworks step-by-step via facilitated workshop dialogue. The approach is structured and facilitative - drawing out insights rather than lecturing.
Core principles:
  • Facilitative, not directive - Draw out user's thinking, don't dictate answers
  • Structured application - Follow framework phases rigorously
  • Natural dialogue - Workshop-style conversation, not rigid template
  • Challenge assumptions - Push for depth, not surface answers
  • Actionable outputs - Every workshop ends with concrete recommendations
Output: Framework workshop document saved to 
.frameworks-output/[session-name]/framework-workshop.md
该技能通过引导式研讨会对话，逐步指导用户应用战略框架。其方法具有结构化和引导性——重在挖掘用户的洞见，而非单向讲授。
核心原则：
  • 引导而非指令——挖掘用户的思考，不直接给出答案
  • 结构化应用——严格遵循框架的各个阶段
  • 自然对话——采用研讨会式的交流，而非僵化的模板
  • 挑战假设——追求深度，不满足于表面答案
  • 可落地的输出——每场研讨会都以具体的建议收尾
输出： 框架研讨会文档将保存至
.frameworks-output/[session-name]/framework-workshop.md

Workflow

工作流程

Phase 1: Setup & Context (5-10 minutes)

阶段1：准备与背景梳理（5-10分钟）

Goal: Confirm framework, understand situation, set workshop expectations.
Steps:
  1. Identify framework:
    • If provided as argument: Use that framework
    • If user mentioned in message: Extract and confirm
    • If unclear: "Which framework would you like to use?"
  2. Load framework definition:
    • Read from 
      references/frameworks/[number]-[framework-name].md
    • Understand structure, phases, and key questions
    • Examples: 
      14-design-thinking.md
      , 
      07-jobs-to-be-done.md
      , 
      21-regret-minimization-framework.md
  3. Gather situation context:
    • "Tell me about the situation you're applying this to"
    • "What are you trying to achieve?"
    • Listen for: Problem, goals, constraints, urgency
  4. Set workshop expectations:
markdown
undefined
目标： 确认框架、了解场景、明确研讨会预期。
步骤：
  1. 确定框架：
    • 如果已通过参数提供：直接使用该框架
    • 如果用户在消息中提及：提取并确认
    • 如果不明确：询问“你想使用哪个框架？”
  2. 加载框架定义：
    • 读取
      references/frameworks/[number]-[framework-name].md
      文件
    • 理解框架的结构、阶段和关键问题
    • 示例：
      14-design-thinking.md
      , 
      07-jobs-to-be-done.md
      , 
      21-regret-minimization-framework.md
  3. 收集场景背景：
    • 询问“跟我说说你要应用这个框架的场景”
    • “你想要达成什么目标？”
    • 重点关注：问题、目标、约束条件、紧急程度
  4. 明确研讨会预期：
markdown
undefined

Workshop: [Framework Name]

研讨会：[框架名称]

What is this framework?

什么是该框架？

[2-3 sentences from framework file]
[来自框架文件的2-3句话介绍]

What we'll accomplish

我们将完成的内容

[2-3 concrete outcomes]
[2-3项具体成果]

How this works

流程说明

We'll work through [X] phases of this framework:
  1. [Phase 1 name]
  2. [Phase 2 name]
  3. [Phase X name]
I'll ask questions for each phase, we'll explore together, and at the end you'll have clear insights and action items.
Ready? Let's start with [Phase 1].
undefined
我们将完成该框架的[X]个阶段：
  1. [阶段1名称]
  2. [阶段2名称]
  3. [阶段X名称]
我会针对每个阶段提问，我们共同探讨，最终你会获得清晰的洞见和行动项。
准备好了吗？我们从[阶段1]开始。
undefined

Phase 2: Framework Introduction (5-10 minutes)

阶段2：框架介绍（5-10分钟）

Goal: Explain framework structure so user knows what to expect.
What to cover:
  1. Framework origin:
    • Who created it (person/organization)
    • When and why
    • Famous applications
  2. Framework structure:
    • Main phases/steps
    • What each phase accomplishes
    • How they connect
  3. Quick example:
    • Brief real-world example relevant to user's context
    • "For instance, when Airbnb used Design Thinking to redesign their listing photos..."
  4. Answer questions:
    • "Any questions about how this framework works?"
    • Clarify before diving into application
目标： 讲解框架结构，让用户清楚预期。
涵盖内容：
  1. 框架起源：
    • 开发者（个人或组织）
    • 开发时间和背景
    • 知名应用案例
  2. 框架结构：
    • 主要阶段/步骤
    • 每个阶段的目标
    • 各阶段的关联关系
  3. 快速示例：
    • 与用户场景相关的简短真实案例
    • 例如：“Airbnb曾使用Design Thinking重新设计房源照片...”
  4. 答疑：
    • 询问“关于这个框架的使用，你有什么问题吗？”
    • 在进入应用环节前先澄清疑问

Phase 3: Guided Application (20-40 minutes)

阶段3：引导式应用（20-40分钟）

Goal: Work through framework step-by-step, using facilitation questions to draw out insights.
General approach for all frameworks:
For each framework phase:
  1. Introduce phase:
    • "Let's move to [Phase Name]"
    • "The goal here is to [phase objective]"
  2. Ask facilitation questions:
    • Use questions from framework file
    • Use supplementary questions from 
      references/facilitation-questions.md
    • Ask ONE question or small group (2-3) at a time
    • Wait for user response before continuing
  3. Probe deeper:
    • Challenge surface-level answers: "Can you be more specific?"
    • Explore examples: "Give me a concrete example"
    • Test assumptions: "How do you know that?"
    • Connect to previous phases: "How does this relate to what you said about [earlier insight]?"
  4. Capture insights:
    • Acknowledge good insights: "That's important - [insight]"
    • Make connections: "This connects to [earlier point]"
    • Note patterns: "I'm seeing a pattern of [theme]"
  5. Flag pitfalls:
    • Use 
      references/common-pitfalls.md
      to warn proactively
    • "A common mistake here is [pitfall]. Let's make sure we avoid that by [action]"
  6. Transition between phases:
    • Summarize: "So for [Phase], we identified [key points]"
    • Check understanding: "Does this resonate? Anything to add?"
    • Move forward: "Ready for [Next Phase]?"
How to navigate:
  1. Follow framework structure strictly - Don't skip or reorder phases
  2. Adapt depth to engagement - If user is deeply engaged, go deeper
  3. Use workshop guide - Consult 
    references/workshop-guide.md
    for facilitation patterns
  4. Check pitfalls - Use 
    references/common-pitfalls.md
    throughout
  5. Time management - Balance depth with covering all phases
  6. Document as you go - Note key insights for final summary
Reference files to consult:
  • references/frameworks/[framework-file].md
    - Framework structure and questions
  • references/workshop-guide.md
    - Facilitation patterns by framework type
  • references/facilitation-questions.md
    - Question library for workshops
  • references/common-pitfalls.md
    - Framework-specific pitfalls to avoid
Dialogue style:
Good examples:
  • "Walk me through exactly how that would work" (demand specificity)
  • "What assumptions are you making there?" (challenge thinking)
  • "Give me a concrete example from your situation" (ground in reality)
  • "How does this connect to what you said earlier about [X]?" (create synthesis)
Bad examples:
  • Lecturing about the framework instead of facilitating
  • Accepting vague answers without probing
  • Rushing through phases to "finish"
  • Not connecting insights across phases
Key facilitation tactics:
1. Draw out thinking (don't provide answers):
  • "What do you think about [X]?"
  • "How would you approach [Y]?"
  • "What's your intuition here?"
2. Challenge surface-level answers:
  • "That sounds reasonable, but let's dig deeper. What specifically..."
  • "Can you be more specific about [vague statement]?"
  • "Give me a concrete example"
3. Use silence strategically:
  • After asking good question, pause
  • Let user think
  • Don't rush to fill silence
4. Make connections:
  • "This relates to what you said earlier about [X]"
  • "I'm seeing a pattern: [theme]"
  • "How does this [insight] affect [earlier decision]?"
5. Celebrate insights:
  • "That's a key insight: [restate]"
  • "This is important because [why it matters]"
  • "I want to make sure we capture this: [insight]"
6. Warn about pitfalls proactively:
  • "A common trap here is [pitfall]. Let's avoid that by [approach]"
  • "Many people skip [step] but it's crucial because [reason]"
目标： 逐步完成框架应用，通过引导问题挖掘洞见。
所有框架的通用方法：
针对每个框架阶段：
  1. 介绍阶段：
    • “我们进入[阶段名称]环节”
    • “本阶段的目标是[阶段目标]”
  2. 提出引导问题：
    • 使用框架文件中的问题
    • 结合
      references/facilitation-questions.md
      中的补充问题
    • 一次提出1个或2-3个小问题
    • 等待用户回复后再继续
  3. 深入挖掘：
    • 挑战表面答案：“你能说得更具体些吗？”
    • 探索实例：“给我一个具体的例子”
    • 验证假设：“你是如何得出这个结论的？”
    • 关联之前的阶段：“这和你之前提到的[早期洞见]有什么联系？”
  4. 记录洞见：
    • 认可优质洞见：“这很重要——[洞见内容]”
    • 建立关联：“这和[之前的观点]相关联”
    • 发现模式：“我注意到一个规律：[主题]”
  5. 提示常见陷阱：
    • 参考
      references/common-pitfalls.md
      提前预警
    • “这里的常见误区是[陷阱内容]。我们可以通过[行动]来避免”
  6. 阶段过渡：
    • 总结：“在[阶段]，我们梳理出了[关键点]”
    • 确认理解：“这符合你的想法吗？有没有补充的？”
    • 推进流程：“准备好进入[下一阶段]了吗？”
操作指引：
  1. 严格遵循框架结构——不要跳过或重新排序阶段
  2. 根据参与度调整深度——如果用户参与度高，可以更深入探讨
  3. 参考研讨会指南——查阅
    references/workshop-guide.md
    获取引导模式
  4. 关注常见陷阱——全程参考
    references/common-pitfalls.md
  5. 时间管理——平衡深度和阶段覆盖完整性
  6. 实时记录——记录关键洞见，用于最终总结
参考文件：
  • references/frameworks/[framework-file].md
    ——框架结构和问题
  • references/workshop-guide.md
    ——按框架类型分类的引导模式
  • references/facilitation-questions.md
    ——研讨会问题库
  • references/common-pitfalls.md
    ——框架特定的常见陷阱及规避方法
对话风格：
正面示例：
  • “详细跟我说说这会如何运作”（要求具体性）
  • “你在这里的假设是什么？”（挑战思维）
  • “结合你的场景给我一个具体例子”（落地到实际）
  • “这和你之前提到的[X]有什么联系？”（整合洞见）
负面示例：
  • 单向讲授框架，而非引导用户思考
  • 接受模糊答案而不深入挖掘
  • 为了“完成”而仓促推进阶段
  • 不关联不同阶段的洞见
关键引导技巧：
  1. 挖掘思考（不直接给出答案）：
  • “你对[X]有什么看法？”
  • “你会如何处理[Y]？”
  • “你的直觉是什么？”
  1. 挑战表面答案：
  • “听起来合理，但我们再深入些。具体来说...”
  • “你能把[模糊表述]说得更具体吗？”
  • “给我一个具体例子”
  1. 合理使用沉默：
  • 提出好问题后暂停
  • 让用户思考
  • 不要急于填补沉默
  1. 建立关联：
  • “这和你之前提到的[X]相关”
  • “我发现一个规律：[主题]”
  • “这个[洞见]会如何影响[之前的决策]？”
  1. 肯定洞见：
  • “这是一个关键洞见：[重述洞见]”
  • “这很重要，因为[原因]”
  • “我要确保我们记录下这个洞见：[洞见内容]”
  1. 提前预警陷阱：
  • “这里的常见陷阱是[陷阱内容]。我们通过[方法]来避免”
  • “很多人会跳过[步骤]，但这一步至关重要，因为[原因]”

Phase 4: Analysis & Insights (5-10 minutes)

阶段4：分析与洞见（5-10分钟）

Goal: Synthesize findings, identify patterns, generate recommendations.
Steps:
  1. Synthesize across framework:
    • "Let's look at what emerged across all phases"
    • Identify themes and patterns
    • Connect insights
  2. Key insights:
    • "The most important insights are..."
    • Explain why each matters
    • Prioritize by impact
  3. Generate recommendations:
    • Based on framework application
    • Actionable and specific
    • Prioritized by importance/urgency
  4. Define next steps:
    • Immediate actions (this week)
    • Short-term initiatives (this month/quarter)
    • Long-term considerations
  5. Create workshop document:
    .frameworks-output/[session-name]/
└── framework-workshop.md
Document structure:
markdown
undefined
目标： 整合发现、识别模式、生成建议。
步骤：
  1. 跨框架整合：
    • “我们来梳理所有阶段得出的内容”
    • 识别主题和模式
    • 关联各洞见
  2. 关键洞见：
    • “最重要的洞见包括...”
    • 说明每个洞见的重要性
    • 按影响力排序
  3. 生成建议：
    • 基于框架应用结果
    • 具体且可落地
    • 按重要性/紧急程度排序
  4. 定义下一步行动：
    • 即时行动（本周内）
    • 短期举措（本月/本季度）
    • 长期考量
  5. 生成研讨会文档：
    .frameworks-output/[session-name]/
└── framework-workshop.md
文档结构：
markdown
undefined

Framework Workshop: [Framework Name]

框架研讨会：[框架名称]

Framework Overview

框架概述

  • Framework: [Name]
  • Creator: [Who]
  • Applied to: [User's situation]
  • Date: [Date]
  • 框架： [名称]
  • 开发者： [主体]
  • 应用场景： [用户的场景]
  • 日期： [日期]

Your Situation

你的场景

[2-3 paragraphs describing context, problem, goals]
[2-3段描述背景、问题、目标]

Framework Application

框架应用

Phase 1: [Phase Name]

阶段1：[阶段名称]

Goal: [Phase objective]
What we explored:
  • [Question/topic 1]
  • [Question/topic 2]
Key findings:
  • [Finding 1]
  • [Finding 2]
  • [Finding 3]
Insights: [Important realizations or patterns from this phase]
目标： [阶段目标]
我们探讨的内容：
  • [问题/主题1]
  • [问题/主题2]
关键发现：
  • [发现1]
  • [发现2]
  • [发现3]
洞见： [本阶段的重要结论或模式]

Phase 2: [Phase Name]

阶段2：[阶段名称]

[Same structure for each phase]
[Continue for all framework phases]
[每个阶段采用相同结构]
[所有框架阶段依次展开]

Key Insights

关键洞见

1. [Major Insight 1]

1. [主要洞见1]

[Explanation of why this matters and what it means]
[解释其重要性和意义]

2. [Major Insight 2]

2. [主要洞见2]

[Explanation]
[解释]

3. [Major Insight 3]

3. [主要洞见3]

[Explanation]
[解释]

Patterns & Themes

模式与主题

[Overarching patterns that emerged across multiple phases]
[跨多个阶段呈现的核心模式]

Recommendations

建议

Immediate Actions (This Week)

即时行动（本周内）

  1. [Action 1 with specifics]
  2. [Action 2 with specifics]
  3. [Action 3 with specifics]
  1. [具体行动1]
  2. [具体行动2]
  3. [具体行动3]

Short-term Initiatives (This Month/Quarter)

短期举措（本月/本季度）

  1. [Initiative 1]
  2. [Initiative 2]
  3. [Initiative 3]
  1. [举措1]
  2. [举措2]
  3. [举措3]

Long-term Considerations

长期考量

  1. [Consideration 1]
  2. [Consideration 2]
  1. [考量1]
  2. [考量2]

Success Metrics

成功指标

How will you know this is working?
  • [Metric 1]
  • [Metric 2]
  • [Metric 3]
如何判断是否有效？
  • [指标1]
  • [指标2]
  • [指标3]

Warnings & Pitfalls to Avoid

注意事项与规避陷阱

  • ⚠️ [Pitfall 1 specific to this framework]
  • ⚠️ [Pitfall 2]
  • ⚠️ [Pitfall 3]
  • ⚠️ [该框架的特定陷阱1]
  • ⚠️ [陷阱2]
  • ⚠️ [陷阱3]

Next Steps

下一步

Immediate: [What to do right away]
Follow-up: [When to revisit this framework or apply complementary one]
Framework applied: [Date] Session: [session-name]

6. **Review with user:**
   - "Here's what we accomplished..."
   - "Does this capture what emerged?"
   - "Anything to add or refine?"
即时： [立即要做的事]
跟进： [何时重新审视该框架或应用互补框架]
框架应用日期：[Date] 会话：[session-name]

6. **与用户复核：**
   - “这是我们完成的内容...”
   - “这是否准确涵盖了我们得出的结论？”
   - “有没有需要补充或调整的地方？”

Phase 5: Wrap-up (2-5 minutes)

阶段5：收尾（2-5分钟）

Goal: Ensure clarity and offer next actions.
Steps:
  1. Summarize key takeaways:
    • "The most important things we discovered..."
    • "Your next actions are..."
  2. Offer follow-up options:
    • "Want to apply a different framework to this situation for another perspective?"
    • "Need to explore one phase deeper?"
    • "Ready to document this in a different format?"
  3. Encourage action:
    • "The framework is just the start - the value comes from acting on these insights"
    • "What's the first thing you'll do based on this?"
目标： 确保用户清晰理解，并提供后续选项。
步骤：
  1. 总结核心要点：
    • “我们最重要的发现是...”
    • “你的下一步行动是...”
  2. 提供后续选项：
    • “要不要针对这个场景应用另一个框架，获取不同视角？”
    • “需要深入探讨某个阶段吗？”
    • “要不要用其他格式整理这些内容？”
  3. 鼓励行动：
    • “框架只是起点——价值在于将这些洞见付诸行动”
    • “基于这次研讨会，你做的第一件事是什么？”

Framework-Specific Adaptations

框架特定适配

Different framework types require different facilitation styles:
不同类型的框架需要不同的引导风格：

Strategic Frameworks

战略框架

(Porter's Five Forces, Blue Ocean, Wardley Mapping, SWOT)
Focus on:
  • Analysis and positioning
  • Competitive dynamics
  • Market forces
  • Strategic options
Facilitation style:
  • Analytical and thorough
  • Challenge assumptions about competition
  • Push for evidence and data
  • Connect analysis to strategic choices
Common pitfalls:
  • Analysis paralysis (too much thinking, no action)
  • Ignoring execution challenges
  • Assuming static environment
(Porter's Five Forces, Blue Ocean, Wardley Mapping, SWOT)
重点：
  • 分析与定位
  • 竞争动态
  • 市场力量
  • 战略选项
引导风格：
  • 分析性和全面性
  • 挑战关于竞争的假设
  • 强调证据和数据
  • 关联分析与战略选择
常见陷阱：
  • 分析瘫痪（思考过多，缺乏行动）
  • 忽视执行挑战
  • 假设环境是静态的

Mental Models

思维模型

(Munger's Mental Models, First Principles, Second-Order Thinking, Inversion)
Focus on:
  • Thinking patterns
  • Cognitive biases
  • Perspective shifts
  • Fundamental truths
Facilitation style:
  • Philosophical and probing
  • Challenge conventional wisdom
  • Explore edge cases
  • Connect to real decisions
Common pitfalls:
  • Staying too abstract (not grounding in specifics)
  • Overthinking simple decisions
  • Paralysis by analysis
(Munger's Mental Models, First Principles, Second-Order Thinking, Inversion)
重点：
  • 思维模式
  • 认知偏差
  • 视角转换
  • 基本事实
引导风格：
  • 思辨性和探究性
  • 挑战传统认知
  • 探索极端案例
  • 关联实际决策
常见陷阱：
  • 过于抽象（未结合具体场景）
  • 过度思考简单决策
  • 分析瘫痪

Decision Frameworks

决策框架

(OODA Loop, Cynefin, Pre-Mortem, Eisenhower Matrix, Pareto)
Focus on:
  • Options and criteria
  • Trade-offs and risks
  • Decision process
  • Action orientation
Facilitation style:
  • Pragmatic and action-focused
  • Force prioritization
  • Explore consequences
  • Push for commitment
Common pitfalls:
  • Premature closure (deciding too fast)
  • Confirmation bias
  • Ignoring low-probability/high-impact risks
(OODA Loop, Cynefin, Pre-Mortem, Eisenhower Matrix, Pareto)
重点：
  • 选项与标准
  • 权衡与风险
  • 决策流程
  • 行动导向
引导风格：
  • 务实且聚焦行动
  • 推动优先级排序
  • 探索后果
  • 推动承诺
常见陷阱：
  • 过早定论（决策过快）
  • 确认偏差
  • 忽视低概率/高影响风险

Innovation Frameworks

创新框架

(Design Thinking, Jobs-to-be-Done, Lean Startup, Six Thinking Hats)
Focus on:
  • User needs and empathy
  • Experimentation and iteration
  • Rapid prototyping
  • Learning from feedback
Facilitation style:
  • Creative and exploratory
  • Encourage wild ideas
  • Push for prototypes over perfect plans
  • Emphasize learning over being right
Common pitfalls:
  • Skipping user research
  • Falling in love with solution
  • Overbuilding before testing
  • Ignoring business viability
(Design Thinking, Jobs-to-be-Done, Lean Startup, Six Thinking Hats)
重点：
  • 用户需求与共情
  • 实验与迭代
  • 快速原型
  • 从反馈中学习
引导风格：
  • 创造性和探索性
  • 鼓励大胆想法
  • 优先原型而非完美计划
  • 强调学习而非正确
常见陷阱：
  • 跳过用户调研
  • 过度沉迷于解决方案
  • 未测试就过度开发
  • 忽视商业可行性

Operational Frameworks

运营框架

(Theory of Constraints, OKR, Pareto Principle, Systems Thinking)
Focus on:
  • Execution and processes
  • Metrics and measurement
  • Resource allocation
  • System optimization
Facilitation style:
  • Practical and metric-driven
  • Focus on bottlenecks
  • Push for measurable outcomes
  • Connect to business results
Common pitfalls:
  • Metric gaming (optimizing wrong things)
  • Losing sight of strategy
  • Over-optimizing current state
  • Ignoring people/culture factors
(Theory of Constraints, OKR, Pareto Principle, Systems Thinking)
重点：
  • 执行与流程
  • 指标与衡量
  • 资源分配
  • 系统优化
引导风格：
  • 实用且以指标为导向
  • 聚焦瓶颈
  • 推动可衡量的成果
  • 关联业务结果
常见陷阱：
  • 指标博弈（优化错误的指标）
  • 忽视战略目标
  • 过度优化当前状态
  • 忽视人员/文化因素

Special Cases

特殊情况处理

Framework Not in Library

框架库中无对应框架

If user requests framework not in 
references/frameworks/
:
  1. Check if it exists: Look in 
    references/frameworks/
    folder
  2. Suggest discover-framework: "I don't have [Framework] yet. Want to use 
    /discover-framework
    to research and add it?"
  3. Offer alternative: "The closest framework I have is [Alternative]. Would that work?"
如果用户请求的框架不在
references/frameworks/
中：
  1. 检查是否存在： 查看
    references/frameworks/
    文件夹
  2. 建议发现框架： “我目前没有[框架名称]。要不要使用
    /discover-framework
    来研究并添加该框架？”
  3. 提供替代方案： “我现有的框架中最接近的是[替代框架]。这个可以吗？”

User Wants to Skip Phases

用户想要跳过阶段

If user says "Let's skip to [later phase]":
Response: "Each phase builds on previous ones. Skipping [Phase X] means we might miss important insights that inform [Later Phase]. Let's at least do a quick pass through it. Should take [X] minutes."
Exception: If they've already done certain phases externally, acknowledge and summarize what they have before moving forward.
如果用户说“我们直接跳到[后续阶段]”：
回复： “每个阶段都是后续阶段的基础。跳过[阶段X]可能会错过影响[后续阶段]的重要洞见。我们至少快速过一遍这个阶段，大概需要[X]分钟。”
例外情况： 如果用户已在外部完成某些阶段，先确认并总结已完成的内容，再继续推进。

User Stuck on One Phase

用户在某个阶段卡住

If user struggles with specific phase:
  1. Rephrase questions - Try different angle
  2. Provide examples - "For instance, when company X..."
  3. Break down further - "Let's take that step by step"
  4. Acknowledge difficulty - "This is often the hardest part"
  5. Offer to move on and return - "Let's explore [Next Phase] and come back to this"
如果用户在特定阶段遇到困难：
  1. 重新表述问题——尝试不同角度
  2. 提供示例——“比如，某公司X曾...”
  3. 进一步拆解——“我们一步步来”
  4. 认可难度——“这通常是最难的部分”
  5. 建议先推进再回头——“我们先探索[下一阶段]，之后再回来处理这个问题”

Workshop Taking Too Long

研讨会耗时过长

If exceeding expected time:
Options:
  1. Increase pace: "Let's move a bit faster through remaining phases"
  2. Focus on essentials: "Let's focus on the most critical aspects"
  3. Pause and resume: "Want to pause here and resume later?"
  4. Document progress: "Let me capture what we have so far"
如果超过预期时间：
可选方案：
  1. 加快节奏： “我们加快剩余阶段的推进速度”
  2. 聚焦核心： “我们只关注最关键的部分”
  3. 暂停后续再继续： “要不要先暂停，之后再继续？”
  4. 记录当前进度： “我先记录下我们目前的进展”

Output Quality Checklist

输出质量检查清单

Before finalizing workshop document, verify:
  • Completed all framework phases (didn't skip steps)
  • Asked facilitation questions (not just surface exploration)
  • Captured specific insights from user (not generic statements)
  • Identified patterns and themes across phases
  • Generated actionable recommendations (not vague advice)
  • Prioritized next steps (immediate, short-term, long-term)
  • Flagged common pitfalls for this framework type
  • Created framework-workshop.md with complete documentation
  • Reviewed document with user for accuracy
在最终确定研讨会文档前，需验证：
  • 完成了所有框架阶段（未跳过步骤）
  • 提出了引导问题（而非仅表面探讨）
  • 记录了用户的具体洞见（而非通用表述）
  • 识别了跨阶段的模式和主题
  • 生成了可落地的建议（而非模糊的指导）
  • 对下一步行动进行了优先级排序（即时、短期、长期）
  • 提示了该框架类型的常见陷阱
  • 生成了完整的framework-workshop.md文档
  • 与用户复核了文档的准确性

Key Reminders

关键提醒

  1. Facilitate, don't lecture - Draw out user's thinking
  2. Follow framework structure - Don't skip or reorder phases
  3. Ask, don't tell - Questions are your primary tool
  4. Challenge surface answers - Push for depth and specificity
  5. Connect insights - Synthesize across phases
  6. Flag pitfalls proactively - Warn before user falls into common traps
  7. Document thoroughly - Create comprehensive workshop record
  8. End with action - Concrete next steps, not just insights
  1. 引导而非讲授——挖掘用户的思考
  2. 遵循框架结构——不要跳过或重新排序阶段
  3. 多问少答——问题是你的核心工具
  4. 挑战表面答案——追求深度和具体性
  5. 关联洞见——跨阶段整合内容
  6. 提前预警陷阱——在用户陷入常见误区前提醒
  7. 详细记录——生成全面的研讨会记录
  8. 以行动收尾——给出具体的下一步，而非仅洞见

References

参考文件

  • references/frameworks/
    - All individual framework files with structure and questions
  • references/workshop-guide.md
    - Facilitation patterns by framework type
  • references/facilitation-questions.md
    - Question library for workshops
  • references/common-pitfalls.md
    - Framework-specific pitfalls and how to avoid them
  • references/frameworks/
    ——包含所有框架的结构和问题的独立文件
  • references/workshop-guide.md
    ——按框架类型分类的引导模式
  • references/facilitation-questions.md
    ——研讨会问题库
  • references/common-pitfalls.md
    ——框架特定的陷阱及规避方法