Skip to content

CCDawn/briefbound-skills / skills/engineering/briefbound-router

briefbound-router

Verified

Use when Chinese-first active intent discovery, local context probing, user calibration before downstream skill selection, owner/workflow routing, continuation, permission inference, or multi-thread/conflict coordination is needed.

references/capability-routing.md

View on GitHub
# Briefbound Router Capability Routing

只在请求主要依赖专用工具、外部服务或文件制品时读取。以下 owner 必须先出现在本轮 Available skills;缺失时使用表中 fallback,不为普通任务临时安装插件。

## 路由表

| 用户目标 | Preferred owner(可用时) | 角色与 fallback |
|---|---|---|
| GitHub 仓库、issue、PR 元信息与一般分诊 | `github:github` | primary;缺失时用 `gh`/git 做最窄读取 |
| 处理 PR review comments | `github:gh-address-comments` | primary;不要退化成重新做整份 PR review |
| GitHub Actions/PR checks 失败 | `github:gh-fix-ci` | primary,`briefbound-bug-review` 仅承接已定位的代码缺陷 |
| 提交、push、创建 draft PR | `github:yeet` | primary;远程写入仍遵守授权和 scope;随后由 Briefbound Router 执行 `Post-PR Closeout Gate` |
| 操作或检查 in-app Browser | `browser:control-in-app-browser` | 工具 owner;UI/bug owner 保留行为判断与最终结论 |
| OpenAI API、Codex、ChatGPT 使用与最新官方说明 | `openai-docs` | primary;只采用官方来源 |
| 生成或编辑位图资产 | `imagegen` | primary;UI/Visual owner 提供用途和验收边界 |
| 架构/流程/时序/数据图解及 Mermaid、draw.io、Excalidraw 重绘 | `briefbound-diagram-design` | 独立制图 primary;报告/PPT 内图解 support;PNG 格式本身不触发 imagegen,用户指定的工具优先 |
| Figma 通用读写 | `figma:figma-use` | 每次 `use_figma` 前置;按任务叠加下面一个最具体 Figma skill |
| 代码页面生成 Figma 设计 | `figma:figma-generate-design` | 与 `figma:figma-use` 配合,不路由普通前端实现 |
| Figma 设计系统/组件库 | `figma:figma-generate-library` | Design System 判断契约,Figma skill 执行制品写入 |
| Figma 图表、FigJam、Slides、motion、SwiftUI | 对应 `figma:*` 专项 | 只选当前动作需要的一个专项,不加载整套 Figma skills |
| 创建/编辑 Word 文档 | `documents:documents` | primary,遵循渲染验证 |
| PDF 阅读、生成或版面检查 | `pdf:pdf` | primary,视觉版面必须渲染验证 |
| Excel/CSV/独立表格制品 | `spreadsheets:Spreadsheets` | primary;已打开 Excel 会话用 `spreadsheets:excel-live-control` |
| PowerPoint/Slides 演示文稿 | `presentations:Presentations` | primary |
| `.openai/hosting.json` 项目或 Sites 建站 | `sites:sites-building` | primary;发布随后使用 `sites:sites-hosting` |
| 明确要求操作 Windows 应用 | `computer-use:computer-use` | 工具 owner;可用 CLI/API 时优先更稳定的专用能力 |
| 无任务目标的纯闲聊、陪聊 | `briefbound-pengyou` | primary;出现任务目标即回到上表或当前代码 owner |
| 逆向分析、反编译二进制/Electron/JS/.NET/固件/网站、版本比对与运行时取证 | `briefbound-reverse-engineer` | primary;正向开发不进入 |

## 组合规则

- **汇报主动配图**:调研/审查/分析/跨阶段汇报若涉及至少三个关联组件、阶段或角色,或重点是流程、时序、数据流、依赖、因果、状态及数值比较,且图能降低理解成本,则加 `briefbound-diagram-design` support;事实充分时直接生成一张中文总览图。简单状态、单结论、短列表、重复表达或用户拒图时跳过;不编造,删减改变结论则先校准。
- 专项工具拥有“如何操作”,Briefbound owner 拥有“做什么、范围、判断和验收”。同一动作只设一个 primary;工具只是支撑时不重复输出第二份流程。
- PR + UI 运行验证:`briefbound-pr-review` primary,Browser/UI Review 最多一个 support。CI 修复请求则 `github:gh-fix-ci` primary。
- UI 设计并实现仍由 UI/Visual owner 贯穿;Browser、Figma、Imagegen 是按需能力,不产生新阶段。
- 文件制品请求直接命中对应 artifact owner,不先进入 Planning;只有内容、结构或高风险取舍仍未对齐时才回 Briefbound Router。
- 多动作请求按依赖动态组合,例如“修 CI 后 push 并开 PR”依次使用 CI owner、当前代码 owner、发布 owner,不同时加载全部 skill。
- 用户已明确说“修复/处理/实现”时,诊断完成后可在原 scope 内直接实施;专项 owner 的“先检查再修复”是执行顺序,不是再次索要许可。`push`、发布、破坏性操作、权限或范围扩大仍是独立授权边界。
- Preferred owner 不可用时说明能力缺口并使用最低充分 fallback;需要安装指定插件时才进入安装流程。

## 无专项 skill 的软件任务

后端/API、数据库查询与普通 schema 修改、CLI、构建配置、依赖更新、常规测试、容器和一般部署脚本默认由当前代码 owner 直接完成,不因“技能包没有同名 skill”而进入 Planning 或安装新工具。出现真实设计分叉/迁移/发布风险才用 Planning;已有故障用 Bug Review;整仓健康审计用 Project Review;外部复用会改变架构时才用 Feature Reuse Research。

性能症状有明确对象时归 Bug Review;整仓性能结构审计归 Project Review。安全、权限、数据删除和生产发布不靠通用包装 skill 降低风险,沿当前最具体 owner 执行,并保留 Briefbound Router 的授权、迁移和验证闸门。
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall