escalation-router

Original：🇨🇳 Chinese

Translated

Determine the escalation path (Researcher vs. Human) and format the appropriate handoff. Used when the fix-engine has exhausted retry attempts.

1installs

Sourceblueif16/amazing-claude-code-plugins

Added on2026-02-23

NPX Install

npx skill4agent add blueif16/amazing-claude-code-plugins escalation-router

SKILL.md Content (Chinese)

View Translation Comparison →

Escalation Router

Owner: Sub-coordinators only

Responsibilities

Analyze the complexity of the error_report
Decision: solvable by Researcher or requires Human intervention
Format the handoff for the selected path
Send status signal to the main coordinator

Decision Criteria

Route to Researcher:

The error is a technical/knowledge gap (missing library usage, API confusion)
Similar issues exist online (searchable)
No architectural decisions required

Route to Human:

Ambiguous requirements (unclear PRD)
Architectural trade-offs needed
Blocked by external dependencies (API keys, services)
Researcher has failed

Researcher Handoff

yaml

research_request:
  problem_summary: "邮箱验证返回500而非400"
  error_report: {来自fix-engine的完整error_report}
  search_hints:
    - "express错误处理中间件"
    - "验证库自定义错误"
  constraints:
    - 不得更改API契约
    - 必须保留现有测试

Human Handoff

Signal the documenter sub-agent to generate a PRD, then:

Signal to main coordinator: WAITING
Reason: human_intervention_required
Handoff document: ./handoff-prd-{section-id}.md