Back to Details

agently-triggerflow

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Agently TriggerFlow

Agently TriggerFlow

Use this skill when the solution clearly needs orchestration semantics rather than one request family.
The user does not need to say TriggerFlow or Agently. Scenario language such as resumable approval flow, branching automation, output-fan-out refactor, mixed sync/async pipeline, process-clarity refactor, or draft-review-revise pipeline should still route here once orchestration is clearly the owner layer.
当解决方案明确需要编排语义而非单一请求系列时，使用此技能。
用户无需提及TriggerFlow或Agently。当编排明确为核心层级时，诸如可恢复审批流、分支自动化、输出扇出重构、同步/异步混合流水线、流程清晰性重构或草稿-评审-修订流水线等场景描述，仍应导向此处。

Native-First Rules

原生优先规则

  • prefer TriggerFlow for explicit multi-stage quality loops, branching, concurrency, waiting/resume, restart-safe execution, output-fan-out performance refactors, process-clarity refactors, or mixed sync/async orchestration
  • keep workflow stages visible instead of hiding nested request loops
  • combine with 
    agently-model-response
    when one workflow step must reuse one model result as text, parsed data, metadata, or partial updates
  • combine with 
    agently-output-control
    when downstream branches need stable structured fields or required keys
  • 对于明确的多阶段质量循环、分支处理、并发执行、等待/恢复、可重启安全执行、输出扇出性能重构、流程清晰性重构或同步/异步混合编排，优先使用TriggerFlow
  • 保持工作流阶段可见，而非隐藏嵌套请求循环
  • 当某个工作流步骤需要将模型结果作为文本、解析后的数据、元数据或部分更新内容重复使用时，结合
    agently-model-response
    使用
  • 当下游分支需要稳定的结构化字段或必填键时，结合
    agently-output-control
    使用

Anti-Patterns

反模式

  • do not invent a custom event bus or state machine before checking TriggerFlow
  • do not hide draft/judge/revise or similar loops inside one opaque helper
  • 在未确认TriggerFlow的情况下，不要自定义事件总线或状态机
  • 不要将草稿/评审/修订或类似循环隐藏在某个不透明的辅助工具中

Read Next

后续阅读

  • references/overview.md
  • references/overview.md