AgentSkillsCN

interleaving-rule

当任务既需要深入理解问题，又需快速提出可行的解决方案时（例如应对突发事件、权衡利弊、明确验收标准、判断是否可满足需求），可将问题分析与方案构思穿插进行。若一味坚持“先剖析问题，再提出解决方案”的僵化模式，不仅会延误及时的缓解措施，还可能掩盖关键的运行细节，从而影响需求的有效性。

SKILL.md
--- frontmatter
name: interleaving-rule
description: Interleave problem understanding and candidate solutions when the task needs both (incidents, tradeoffs, acceptance criteria, satisfiability). Use when rigid “problem first, solution later” separation would block timely mitigations or hide operational detail needed for valid requirements.

Interleaving Rule

Rules

  1. •You may interleave, but label everything:
    • •NEED: the underlying requirement/goal
    • •CONSTRAINT: time/budget/legal/ops constraints
    • •OPTION: candidate mitigation/design
    • •RISK: downside or failure mode
    • •VALIDATION: how to verify
  2. •Maintain traceability:
    • •Each OPTION must cite which NEED/CONSTRAINT it addresses.
  3. •Keep solution sketches lightweight:
    • •Use “candidate” language; avoid committing to architecture unless requested.

Prompt snippet (copy/paste)

text
You MAY interleave problem understanding and candidate mitigations, but label items as:
NEED / CONSTRAINT / OPTION / RISK / VALIDATION.
Maintain traceability (which NEED/CONSTRAINT drove each OPTION).