القائمة
适用于用户说"继续/推进"需判断当前节点、review/gate 刚完成需恢复编排、route/stage/profile 不清、工件证据冲突、需判断是否进入 hotfix/increment 的场景。不适用于新会话 family discovery（→ using-hf-workflow）。
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Use when starting an existing-code bug audit on a repository or large directory tree. First detects project language + architecture (e.g. C/C++ embedded SOA, Python web service, frontend SPA), proposes a tailored review checklist (scenario-specific bug categories) for user confirmation, then slices the codebase into modules within a per-module token budget. Produces plan.json with profile + review_checklist + modules that downstream audit-reviewer consumes module-by-module. Not for PR diff review (use hf-code-review) or for actually finding bugs (use audit-reviewer).
Use as the FINAL stage of the code-audit pipeline. Reads confirmed.json (output of audit-verifier) and renders a self-contained single-file HTML report (always) and optionally an Excel workbook. The HTML contains summary stats by severity/category/module, filterable finding cards with code snippets and audit trails (reviewer + verifier). Not for emitting findings (use audit-reviewer) or verifying findings (use audit-verifier).
Use when scanning an existing-code module for bugs and emitting finding drafts. Reads source files within one module from the plan.json produced by audit-planner, walks files line-by-line, emits findings/<module>.json with file path, line numbers, category, severity, confidence, code snippet evidence, and reasoning. The set of allowed finding categories is sourced from plan.json's review_checklist (scenario preset such as c-cpp-embedded-soa / python-web-service / frontend-spa / generic) rather than a fixed taxonomy — keep findings scoped to the user-confirmed checklist. This is the PRIMARY (first-stage) reviewer in the two-agent confirmation pipeline; downstream audit-verifier independently confirms each finding. Not for PR diff review (use hf-code-review) or for verifying findings (use audit-verifier).
Use as the SECOND-STAGE independent confirmer in the two-agent code-audit pipeline. Reads finding drafts produced by audit-reviewer and independently re-examines each one against the actual source code, writes verifications/<module>.json with status (confirmed/rejected/upgrade/downgrade/needs_more_evidence), reason, and evidence_check. Operates with FRESH context — does not see reviewer's internal reasoning beyond what is recorded in the finding's description+evidence fields, to enable independent judgement. Not for emitting new findings (use audit-reviewer) or rendering the report (use audit-reporter).
Use when hf-test-driven-dev finishes GREEN on a frontend-touching active task whose spec declares a UI surface, and fresh browser runtime evidence (screenshot / console log / network trace) is required for downstream gates. Not for issuing verdicts (gates do that), not for replacing hf-test-review's test-quality review, not for backend-only tasks.
适用于 test review 通过后评审代码质量、用户要求 code review 的场景。不适用于评审测试（→ hf-test-review）、写/修代码（→ hf-test-driven-dev）、阶段不清（→ hf-workflow-router）。
استنادا إلى تصنيف SOC المهني
| name | hf-workflow-router |
| description | 适用于用户说"继续/推进"需判断当前节点、review/gate 刚完成需恢复编排、route/stage/profile 不清、工件证据冲突、需判断是否进入 hotfix/increment 的场景。不适用于新会话 family discovery（→ using-hf-workflow）。 |
HF workflow family 的 runtime authority。负责根据最新证据决定：Workflow Profile、Execution Mode、Workspace Isolation、canonical 节点、是否切支线、review dispatch、恢复编排。
using-hf-workflow 负责 public entry / family discovery；本 skill 负责 runtime routing / recovery。
本 skill 融合以下已验证方法。每个方法在 Workflow 中有对应的落地步骤。
| 方法 | 核心原则 | 来源 | 落地步骤 |
|---|---|---|---|
| Finite State Machine (FSM) Routing | 将 workflow 阶段建模为有限状态机，每条转移边由工件状态证据驱动 | 项目化实践（工作流路由通用方法） | 步骤 7 — 决定 canonical 节点 |
| Evidence-Based Decision Making | 所有路由判断基于磁盘工件证据（而非聊天记忆），对证据冲突采用保守策略 | 项目化实践（HF 核心约定） | 步骤 2 — 读取证据；步骤 6 — 归一化 handoff |
| Escalation Pattern | Profile 升级遵循渐进增强——从 lightweight 到 standard 到 full | 项目化实践（渐进增强策略） | 步骤 4 — 决定 Workflow Profile |
适用：
hf-hotfix 或 hf-increment不适用 → 先走 using-hf-workflow：
/hf-* 意图Direct invoke 信号：reviewer 返回 reroute_via_router=true、证据冲突需权威路由。
若是 public entry discovery → 回到 using-hf-workflow。否则（恢复编排、profile 判断、消费 review/gate 结论、evidence conflict、切支线）继续。
只读路由所需的最少内容：项目级路径约定（若项目已声明）、用户请求、工件状态、顶层导航（档 2 优先 docs/index.md，档 0/1 用仓库根 README.md，缺失时扫 features/ 兜底）、features/<active>/progress.md、features/<active>/reviews/ 与 features/<active>/verification/ 等 review/verification artifacts。不先做大范围代码探索。read-on-presence：docs/ 中未启用的可选资产缺失不阻塞路由。证据冲突时按未批准处理、选择更上游节点、必要时升级 profile。
优先于普通主链推进：紧急缺陷修复 → hf-hotfix；需求变更/范围调整 → hf-increment。
主线路径在 step 4 决策 Profile 前，先查 ExperienceIndex 看过去同类 cycle 走过的路径。这是 advisory only，不改 step 4 的 authoritative 决策。
触发条件:
.garage/experience/records/ 有文件)调用:
garage recall workflow --task-type <X> --problem-domain <Y> --json
<X> / <Y> 取自当前 cycle 的初步意图判断 (step 2 已读出的工件状态 + 用户请求)。当任一不确定时也可单独传 --problem-domain 或 --task-type，至少一项非空。
Handoff 块附 advisory 段 (仅当返回的 threshold_met=true 且 advisories 非空):
Historical advisory: based on N similar cycles, the typical path is
<seq>. Top lessons: <lesson-1>; <lesson-2>.
advisory only — 用户可改
省略条件 (handoff 块不附 advisory 段, 与 F009/F010 既有行为一致):
threshold_met=false)--skill-id 过滤后所有 record 贡献空序列与 step 4 (Profile) 的关系: advisory 是历史经验摘要, 不影响 Profile 选择本身. step 4 仍按项目级强制规则 → 沿用已有 profile → 按证据选择. advisory 中如果显示历史路径耗时 / 常见 lessons, router 可在 handoff 块内一同传递供下游参考, 但不替代 evidence-based decision.
与 user-pact (5) "你做主" 的关系 (INV-F14-3): advisory 不是 directive. 用户随时可在 handoff 后改路径; 用户也可显式 garage recall workflow --rebuild-cache 重算; 或在 platform.json 设 workflow_recall.enabled: false 完全关掉.
详细 advisory 块格式 + JSON schema + 何时省略 + advisory 与 authoritative routing 的关系: references/recall-integration.md.
由 router 决定，不允许下游自行声称。
| Profile | 适用场景 |
|---|---|
full | 无已批准规格/设计、架构/接口/数据模型变化、高风险模块 |
standard | 已批准规格+设计，中等复杂度扩展或 bugfix |
lightweight | 纯文档/配置/样式变化，或低风险单文件 bugfix |
判定：先执行 项目级强制规则（若项目已声明） → 沿用已有 profile → 按证据选择 → 冲突选更重。只允许升级，不允许降级。
详细规则：references/profile-selection-guide.md
进入 design stage 时，router 还需判断是否激活 hf-ui-design 这个 conditional peer skill。
| 证据 | 决策 |
|---|---|
| 规格声明 UI surface / 可见页面 / 交互 / UX NFR / a11y / i18n / 响应式 | 激活 hf-ui-design，与 hf-design 并行 |
| 规格为 API-only / 脚本 / CLI / 数据管道 / 纯后端 | 不激活，design stage 只走 hf-design 单节点 |
| 规格含糊或证据冲突 | 回 hf-specify 补齐 UI surface 声明，不自行判定 |
激活后按 Design Execution Mode（parallel / architecture-first / ui-first）决定起草顺序；默认 parallel。此字段与 Execution Mode（interactive / auto）正交，不混写。
详细规则：references/ui-surface-activation.md
与 Profile 正交，不混写成复合值。归一化顺序：用户显式要求 → 项目级默认 → 已有值 → 默认 interactive。
interactive：approval step 等待用户auto：按 policy 写 approval record 后自动继续auto 不删除 review、gate 或 approval 节点详细规则：references/execution-semantics.md
可选 coordination state。读取 feature progress.md（默认 features/<active>/progress.md）已有值 + 项目约定 + 当前请求类型。
决策：已有 worktree-active 且路径一致 → 沿用；进入 hf-test-driven-dev 且命中 full/standard/代码修改/脏状态 → worktree-required；仅 lightweight+干净 → in-place。不静默降级。
参考：hf-test-driven-dev/references/worktree-isolation.md（实现侧权威指南）；若 项目声明项目等价路径，优先遵循。要点摘要：Workspace Isolation ∈ in-place / worktree-required / worktree-active；worktree-required 必须在进入实现前完成 worktree provisioning；worktree-active 下游节点必须复用 Worktree Path，不得静默退回主工作区；review dispatch 携带 Worktree Path / Worktree Branch；closeout 不擅自删除 worktree，只记录 disposition。
Next Action Or Recommended Skill 是受控字段。若已有显式 handoff：检查能否归一化 → 是否与最新 evidence 一致 → 是否在当前 profile 合法集合内。全部满足才采用；否则忽略，回退到迁移表。
路由原则：支线优先于主链 → review/gate 恢复优先于实现 → 缺失上游优先于下游 → 冲突选更保守 → task reselection 优先于 finalize。
迁移表：references/profile-node-and-transition-map.md
v0.6 新增（spec FR-002 / FR-003 / FR-010 / FR-015；详见 references/profile-node-and-transition-map.md "v0.6 新增" 段 + references/workflow-shared-conventions.md "v0.6 新增 progress.md schema" 段）：
tasks.progress.json（按 hf-test-driven-dev/references/tasks-progress-schema.md）恢复 task 内 RED-N / GREEN-N / REFACTOR-N 步级进度，不仅节点级category_hint 字段（SHOULD）：handoff JSON 可选携带 category 提示（visual-engineering / deep / quick / ultrabrain），下游 host 不消费时直接忽略wisdom_summary 注入：选下一 active task 前从 notepads/ 读近 N=3 task 摘要注入下游 handoff（≤ 1500 token）## Wisdom Delta 与 ## Fast Lane Decisions 段：详见 references/workflow-shared-conventions.md若结论无法映射到唯一节点，重新路由，不自行补脑。
读取最新结论 → 确认 Profile/Mode → 检查 handoff → 按 router authority 判定。
关键分支：
hf-test-driven-dev GREEN 后：若当前 task / 代码影响面触碰前端运行面（route、App 根组件、UI provider、API client、Vite proxy/env、表单、浏览器存储等），且工件已声明 runtime surface / DoD → 激活 hf-browser-testing；若代码事实触碰运行面但 spec / tasks 未声明 → 回上游补工件，不静默跳过conclusion=通过 + needs_human_confirmation=true：interactive 等待/auto 写 record 再继续hf-test-driven-dev；无剩余 task → hf-finalize；候选不唯一 → hard stop参考：references/review-dispatch-protocol.md、references/reviewer-return-contract.md
不在父会话内联 review。构造最小 review request，带入 Workspace Isolation 上下文，派发独立 subagent，消费结构化 summary。
路由结论不是独立用户交互：非暂停点 → 同一轮进入目标 skill；review 节点 → 立刻派发；approval step → 按 Mode 处理；task reselection → 同一轮继续。只有 hard stop 才等待。
参考：references/execution-semantics.md
最小输出：Current Stage、Workflow Profile、Execution Mode、Workspace Isolation、Target Skill。Evidence 足够时用紧凑格式（加 1-2 条决定性 Why）。不回放未命中分支、不复述 authority 说明。
runtime canonical 写法统一：hf-workflow-router、reroute_via_router。
using-hf-workflow 写进 runtime handoffauto 理解成"不写 approval record"| 文件 | 用途 |
|---|---|
references/profile-selection-guide.md | Profile 判定详细规则 |
references/profile-node-and-transition-map.md | 各 profile 合法节点与迁移表 |
references/execution-semantics.md | Execution Mode、暂停点、连续执行 |
references/review-dispatch-protocol.md | reviewer subagent 派发协议 |
references/reviewer-return-contract.md | reviewer 返回结果契约 |
references/routing-evidence-guide.md | 路由证据收集指南 |
references/routing-evidence-examples.md | 路由判定示例 |
references/ui-surface-activation.md | UI surface 激活条件、Design Execution Mode、联合 design approval 规则 |
references/recall-integration.md | F014 Workflow Recall（step 3.5）：advisory 块格式、JSON schema、省略条件 |
| 借口 | 反驳 / Hard rule |
|---|---|
| "用户喊 /build 就跳过 router 直接到 hf-test-driven-dev。" | Workflow stop rule: 命令是 bias 不是 bypass；必须读 on-disk artifacts 决定真实下一步。 |
| "上游证据不全，我替默认一下走下去。" | Hard Gates (soul.md): router 不替用户做方向 / 取舍；缺 evidence → reroute 回上游或停下抛回。 |
| "FSM 里没列的边角场景我自己加跳转。" | Workflow stop rule: 路径必须落在 references/profile-node-and-transition-map.md；新增跳转需走 ADR / increment，不在 runtime 拍。 |
hf-workflow-router 与 reroute_via_router