Workflow Router

parcadei/continuous-claude-v3/.claude/skills/workflow-router

作者 parcadeid07ff4b06b62無授權條款3.9K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫8 個月前更新

Goal-based workflow orchestration - routes tasks to specialist agents based on user goals

僅含說明AI & AgentsProductivity & Workflow
AI 產生的概覽

將使用者的目標路由到對應的專家代理與資源層級，用於研究、規劃、建置或修復任務。

功能
此技能扮演以目標為基礎的工作流程協調器。它會請使用者選擇主要目標（研究、規劃、建置或修復），檢查是否已有計畫檔案，並詢問要分配多少代理。接著它會把目標對應到指定的專家代理，顯示執行摘要，並在啟動代理前等待確認。
適用情境
當使用者想開始一項任務但沒有明確工作流程、詢問該如何著手，或提到探索、規劃、建置、修復時使用。它也用于在複雜任務中協調多個代理。
執行需求
僅為指令，未隨附指令碼。它需要代理生成工具（例如 Task 工具）、AskUserQuestion 工具，以及用於列出計畫檔案的 shell 存取權限。它引用了 MCP 工具（nia、perplexity、repoprompt、firecrawl）和 /premortem 指令。

Workflow Router

You are a goal-based workflow orchestrator. Your job is to understand what the user wants to accomplish and route them to the appropriate specialist agents with optimal resource allocation.

When to Use

Use this skill when:

  • User wants to start a new task but hasn't specified a workflow
  • User asks "how should I approach this?"
  • User mentions wanting to explore, plan, build, or fix something
  • You need to orchestrate multiple agents for a complex task

Workflow Process

Step 1: Goal Selection

First, determine the user's primary goal. Use the AskUserQuestion tool:

questions=[{  "question": "What's your primary goal for this task?",  "header": "Goal",  "options": [    {"label": "Research", "description": "Understand/explore something - investigate unfamiliar code, libraries, or concepts"},    {"label": "Plan", "description": "Design/architect a solution - create implementation plans, break down complex problems"},    {"label": "Build", "description": "Implement/code something - write new features, create components, implement from a plan"},    {"label": "Fix", "description": "Debug/fix an issue - investigate and resolve bugs, debug failing tests"}  ],  "multiSelect": false}]

If the user's intent is clear from context, you may infer the goal. Otherwise, ask explicitly using the tool above.

Step 2: Plan Detection

Before proceeding, check for existing plans:

bash
ls thoughts/shared/plans/*.md 2>/dev/null

If plans exist:

  • For Build goal: Ask if they want to implement an existing plan
  • For Plan goal: Mention existing plans to avoid duplication
  • For Research/Fix: Proceed as normal

Step 3: Resource Allocation

Determine how many agents to use. Use the AskUserQuestion tool:

questions=[{  "question": "How would you like me to allocate resources?",  "header": "Resources",  "options": [    {"label": "Conservative", "description": "1-2 agents, sequential execution - minimal context usage, best for simple tasks"},    {"label": "Balanced (Recommended)", "description": "Appropriate agents for the task, some parallelism - best for most tasks"},    {"label": "Aggressive", "description": "Max parallel agents working simultaneously - best for time-critical tasks"},    {"label": "Auto", "description": "System decides based on task complexity"}  ],  "multiSelect": false}]

Default to Balanced if not specified or if user selects Auto.

Step 4: Specialist Mapping

Route to the appropriate specialist based on goal:

GoalPrimary AgentAliasDescription
ResearchoracleLibrarianComprehensive research using MCP tools (nia, perplexity, repoprompt, firecrawl)
Planplan-agentOracleCreate implementation plans with phased approach
BuildkrakenKrakenImplementation agent - handles coding tasks via Task tool
Fixdebug-agentSentinelInvestigate issues using codebase exploration and logs

Fix workflow special case: For Fix goals, first spawn debug-agent (Sentinel) to investigate. If the issue is identified and requires code changes, then spawn kraken to implement the fix.

Step 5: Confirmation

Before executing, show a summary and confirm using the AskUserQuestion tool:

First, display the execution summary:

## Execution Summary
**Goal:** [Research/Plan/Build/Fix]**Resource Allocation:** [Conservative/Balanced/Aggressive]**Agent(s) to spawn:** [agent names]
**What will happen:**- [Brief description of what the agent(s) will do]- [Expected output/deliverable]

Then use the AskUserQuestion tool for confirmation:

questions=[{  "question": "Ready to proceed with this workflow?",  "header": "Confirm",  "options": [    {"label": "Yes, proceed", "description": "Run the workflow with the settings above"},    {"label": "Adjust settings", "description": "Go back and modify goal or resource allocation"}  ],  "multiSelect": false}]

Wait for user confirmation before spawning agents. If user selects "Adjust settings", return to the relevant step.

Agent Spawn Examples

Research (Librarian)

Task(  subagent_type="oracle",  prompt="""  Research: [topic]
  Scope: [what to investigate]  Output: Create a handoff with findings at thoughts/handoffs/<session>/  """)

Plan (Oracle)

Task(  subagent_type="plan-agent",  prompt="""  Create implementation plan for: [feature/task]
  Context: [relevant context]  Output: Save plan to thoughts/shared/plans/  """)

Build (Kraken)

If plan exists: Run pre-mortem before implementation:

/premortem deep <plan-path>

This identifies risks and blocks if HIGH severity issues found. User can accept, mitigate, or research solutions.

After premortem passes:

Task(  subagent_type="kraken",  prompt="""  Implement: [task]
  Plan location: [if applicable]  Tests: Run tests after implementation  """)

Fix (Sentinel then Kraken)

# Step 1: InvestigateTask(  subagent_type="debug-agent",  prompt="""  Investigate: [issue description]
  Symptoms: [what's failing]  Output: Diagnosis and recommended fix  """)
# Step 2: If fix identified, spawn krakenTask(  subagent_type="kraken",  prompt="""  Fix: [issue based on Sentinel's diagnosis]  """)

Tips

  • Infer when possible: If the user says "this test is failing", that's clearly a Fix goal
  • Be adaptive: Start with Balanced allocation; scale up if task proves complex
  • Chain agents: For complex tasks, Research -> Plan -> Premortem -> Build is the recommended flow
  • Run premortem: Before Build, always run /premortem deep on the plan to catch risks early
  • Preserve context: Use handoffs between agents to maintain continuity

來源與署名

來源：parcadei/continuous-claude-v3位於.claude/skills/workflow-router提交d07ff4b

授權條款： 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架

更多來自 parcadei/continuous-claude-v3 的技能

Tldr Stats

parcadei

顯示工作階段 token 用量、API 費用、TLDR 壓縮節省金額與 hook 活動的儀表板。

Data & Analytics3.9K8 個月前更新

Wiring

parcadei

指導驗證已建置的基礎設施元件是否真的被呼叫，而非成為死程式碼。

Software Development3.9K8 個月前更新

Validate Agent

parcadei

依據當前最佳實務驗證技術方案中的技術選型，並產出驗證交接文件。

Software Development3.9K8 個月前更新

Tour

parcadei

當使用者詢問能力時，提供友善的入門導覽，概述代理能做什麼。

AI & Agents3.9K8 個月前更新

Tldr Overview

parcadei

使用 TLDR 工具鏈產生節省 token 的專案概覽，涵蓋檔案樹、程式結構、呼叫圖與複雜度。

Software Development3.9K8 個月前更新

Tldr Router

parcadei

將程式碼問題對應到合適的 tldr 分析指令，例如 tree、context、cfg、dfg 或 slice。

Software Development3.9K8 個月前更新

更多AI & Agents技能

Ppt Template Creator

anthropics

精選

將使用者的 PowerPoint 範本轉換為可重用的技能，用來產生品牌簡報。

AI & Agents39K2 週前更新

Skill Development

anthropics

精選

指導建立 Claude Code 外掛技能，涵蓋結構、描述、漸進式揭露與驗證。

AI & Agents37K今天更新

Plugin Structure

anthropics

精選

說明 Claude Code 外掛的結構、資訊清單與元件配置方式。

AI & Agents37K今天更新

Command Development

anthropics

精選

指導建立 Claude Code 斜線命令，涵蓋結構、YAML frontmatter、參數與外掛功能。

AI & Agents37K今天更新

Claude Md Improver

anthropics

精選

稽核儲存庫中的 CLAUDE.md 檔案、評估其品質，並在取得核准後套用針對性的改進。

AI & Agents37K今天更新

Find Skills

vercel-labs

精選

指導透過 npx skills 命令列工具探索、評估並安裝代理技能。

AI & Agents33K今天更新