卡壳问题解决调度Skill WhenStuck-Problem-SolvingDispatch

这是一个问题解决技能调度工具,帮助用户在遇到卡壳时,根据症状选择合适的问题解决技术。适用于软件开发、编程和其他需要高效问题解决的场景。关键词:问题解决、调度、卡壳、技术选择、效率提升、软件开发。

其他 0 次安装 0 次浏览 更新于 3/17/2026

name: 卡壳问题解决调度 description: 根据卡壳类型调度正确的问题解决技术 when_to_use: 当卡壳且不确定针对特定卡壳类型应用哪种问题解决技术时使用 version: 1.1.0

卡壳问题解决调度

概述

不同类型的卡壳需要不同的技术。这个技能帮助您快速识别使用哪种问题解决技能。

核心原则: 匹配卡壳症状到技术。

快速调度

digraph stuck_dispatch {
    rankdir=TB;
    node [shape=box, style=rounded];

    stuck [label="You're Stuck", shape=ellipse, style=filled, fillcolor=lightblue];

    complexity [label="Same thing implemented 5+ ways?
Growing special cases?
Excessive if/else?"];
    innovation [label="Can't find fitting approach?
Conventional solutions inadequate?
Need breakthrough?"];
    patterns [label="Same issue in different places?
Feels familiar across domains?
Reinventing wheels?"];
    assumptions [label="Solution feels forced?
'This must be done this way'?
Stuck on assumptions?"];
    scale [label="Will this work at production?
Edge cases unclear?
Unsure of limits?"];
    bugs [label="Code behaving wrong?
Test failing?
Unexpected output?"];

    stuck -> complexity;
    stuck -> innovation;
    stuck -> patterns;
    stuck -> assumptions;
    stuck -> scale;
    stuck -> bugs;

    complexity -> simp [label="yes"];
    innovation -> collision [label="yes"];
    patterns -> meta [label="yes"];
    assumptions -> invert [label="yes"];
    scale -> scale_skill [label="yes"];
    bugs -> debug [label="yes"];

    simp [label="skills/problem-solving/
simplification-cascades", shape=box, style="rounded,filled", fillcolor=lightgreen];
    collision [label="skills/problem-solving/
collision-zone-thinking", shape=box, style="rounded,filled", fillcolor=lightgreen];
    meta [label="skills/problem-solving/
meta-pattern-recognition", shape=box, style="rounded,filled", fillcolor=lightgreen];
    invert [label="skills/problem-solving/
inversion-exercise", shape=box, style="rounded,filled", fillcolor=lightgreen];
    scale_skill [label="skills/problem-solving/
scale-game", shape=box, style="rounded,filled", fillcolor=lightgreen];
    debug [label="skills/debugging/
systematic-debugging", shape=box, style="rounded,filled", fillcolor=lightyellow];
}

卡壳类型 → 技术

卡壳方式 使用此技能
复杂度螺旋上升 - 同一事物以5种以上方式实现,特殊案例增多 skills/problem-solving/simplification-cascades
需要创新 - 常规解决方案不足,找不到合适方法 skills/problem-solving/collision-zone-thinking
重复模式 - 不同地方出现相同问题,重复造轮子 skills/problem-solving/meta-pattern-recognition
受假设强制 - “必须这样做”,无法质疑前提 skills/problem-solving/inversion-exercise
规模不确定性 - 能在生产中工作吗?边界情况不明确? skills/problem-solving/scale-game
代码损坏 - 行为错误,测试失败,意外输出 skills/debugging/systematic-debugging
多个独立问题 - 可以并行调查 skills/collaboration/dispatching-parallel-agents
根本原因未知 - 症状清晰,原因隐藏 skills/debugging/root-cause-tracing

过程

  1. 识别卡壳类型 - 哪个症状与上表匹配?
  2. 加载该技能 - 阅读具体技术
  3. 应用技术 - 跟随其过程
  4. 如果仍卡壳 - 尝试不同技术或组合

技术组合

有些问题需要多种技术:

  • 简化 + 元模式:找到模式,然后简化所有实例
  • 碰撞 + 反转:强制隐喻,然后反转其假设
  • 规模 + 简化:极端情况揭示可消除内容

记住

  • 匹配症状到技术
  • 一次一个技术
  • 如果第一个无效,组合使用
  • 记录尝试内容