跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

router

When unsure which TeamWorkflow skill applies, or orienting a new task or repository, find the right planning, research, building, review, or recovery workflow. Reuse recorded project bindings and working mode.

timharris707 · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add timharris707/skills --skill router

技能说明


name: router description: "When unsure which TeamWorkflow skill applies, or orienting a new task or repository, find the right planning, research, building, review, or recovery workflow. Reuse recorded project bindings and working mode."

Team-workflow router

Read the Codex desktop binding when this workflow needs harness mechanics, model routing, or recovery.

One entry point for the team-workflow pack. The pack is a portable discipline for running tracked, multi-session, agent-assisted development: pressure-test an idea, build it in parallel lanes, ship it reviewed and merged. The table below names every skill and its moment. Everything repo-specific lives in, or is pointed at from, one binding doc seeded by the setup skill; every skill defers decisions to the decider, the role that doc names.

First use in a repo: read an existing binding when the task needs the pack. Run setup when the user requests installation or a missing binding actually gates tracked work; a bounded question or review can proceed read-only. Where the binding doc records working mode lead, the human works from the orchestrator seat: a new task invokes orchestrate and follows its startup checklist, and this table is what that seat runs, not a menu for the human.

The main flow

Most work travels one route: idea → grill → map → tickets → lanes → review → merge. An idea is pressure-tested in grilling; when real fog surfaces, decision-map charts and works it until nothing gating is undecided (no fog means skipping the map entirely); to-tickets turns what was decided into tracer-bullet items; orchestrate routes those items into parallel lanes, each building under implement's discipline; adversarial-review tries to break each change before it merges. prototype and research are detours off any point of the route, taken when a question needs seeing or reading rather than deciding, and handoff preserves the current task across checkpoints and compaction.

On-ramps merge onto that route rather than starting a new one: ingest turns a recording or media URL into evidence plus a recommendation for where it enters the flow (tickets, a grilling session, strategy for the decider); research findings and returned questionnaires flow back to the stage that owns them: the map ticket, the driving ticket, or the grilling session that spawned them; wizard clears the human-only steps a lane stalls on and hands the flow back.

The skills

SkillReach for it when
setupBind or refresh a repo using recorded decisions, then ask about new or changed bindings, including the working mode (lead from the orchestrator seat, or read code and pick skills). Audit actual installed skills, continuity targets, and duplicate personal copies.
domain-memoryThe repo's institutional memory needs writing or reading: a grilling just closed, a review disposition landed, the decider corrected a wrong assumption, or a session is starting and wants the settled terms and decisions. One store, two artifacts: a small domain glossary plus supersede-never-edit decision records, written as side effects of work at the memory home the binding names; consolidation and backfill happen only by decider disposition.
grillingAn idea or plan is half-formed and nobody has pressure-tested it. Interviews the decider in rounds over a design tree, where the frontier is every decision whose prerequisites are settled, until nothing load-bearing is still assumed. Facts are the agent's job; decisions are the decider's. Run it before charting a map or writing a spec off a conversation.
decision-mapThe work is genuinely foggy: open questions gate each other and nobody can spec it in one sitting. Charts a map (destination, clusters, two ledgers), files gate-decision tickets, and runs briefed decision rounds with the decider. Not for work you could already spec: a map with nothing undecided is overhead.
prototypeThe question is "how should this look / behave / feel in action" and discussion or static artifacts can't settle it. Throwaway code on a prototype/<name> branch: UI variants on the live route, or a terminal UI or single shareable HTML file over a pure logic module; the verdict is the deliverable and the winner is re-implemented properly.
researchA question is answerable from primary sources and should run fire-and-report. Autonomous investigation ending in a cited findings file, and a questionnaire when the missing facts are human-held.
codebase-reviewThe codebase itself needs review: a spec is about to land in an area, enough lanes have merged since the last look, or lanes report the code fighting them. A read-only lane: lens-named finders, a built-in skeptic that kills unproven candidates, a plain-markdown report on the tracker, and a disposition loop where the decider adopts, rejects into rejection memory, or defers every survivor. Zero survivors is a success verdict, not a failure.
to-ticketsThe decision is made and the work needs to be on the board. Turns a plan, a closed decision map, or a pressure-tested conversation into tracer-bullet items: issue-as-spec bodies filed in one pass, blocking edges wired in a second. Fi
阅读完整来源 ↗