worktrail-help
Show the Worktrail front-door commands and accepted positional arguments. Use when the user asks how to invoke worktrail-go, wants the available handoff, spec, pr, repo, or route forms, invokes worktrail-go with help or with a bare noun, or asks how to answer a filed product decision (worktrail-decision).
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- worktrail-help
- description
- Show the Worktrail front-door commands and accepted positional arguments. Use when the user asks how to invoke worktrail-go, wants the available handoff, spec, pr, repo, or route forms, invokes worktrail-go with help or with a bare noun, or asks how to answer a filed product decision (worktrail-decision).
- allowed-tools
- Read
03 SKILL.md 正文
Worktrail command help
Display this concise command reference. Do not start work, claim a brief, or run the dashboard merely because help was requested.
Client command names
Use the command exposed by the host client:
| Client | Front door |
|---|---|
| Claude Code | /worktrail-go |
| Codex | $worktrail:worktrail-go |
The help skill itself is available as /worktrail-help in Claude Code or
$worktrail:worktrail-help in Codex.
Accepted forms
This block is generated from the parser's own form registry
(worktrail-go-parse --forms) and pinned by
tests/router/test_parse_invocation.py, so it cannot drift from what the front
door actually accepts. Regenerate it rather than editing it by hand.
<front-door> dashboard and interactive picker
<front-door> help [topic] show this reference
<front-door> <repo> show active work for a repository
<front-door> handoff new <focus> capture a new handoff brief
<front-door> handoff list list queued handoff briefs
<front-door> handoff start <id> claim or resume a queued handoff
<front-door> handoff auto auto-pick one ranked queue brief
<front-door> handoff drain [max-items] [repo] drain multiple items in fresh contexts
<front-door> spec new <request> plan a new feature
<front-door> spec implement <id> execute a specification
<front-door> spec continue [<id>] resume in-flight work
<front-door> spec fix <request> defect repair (Route F)
<front-door> spec explore <idea> idea discovery (Route A)
<front-door> spec route <A-J> [<id>] force a route
<front-door> pr fix PR / CI repair
<front-door> decision list list open product decisions awaiting an answer
<front-door> decision answer <decision-id> answer a filed decision interactively
<front-door> <brief-id> claim or resume a queued handoff (same as handoff start)
<front-door> <free text> * classify and route any other request
* not a parsed form -- reaches the route classifier as free text
Every <noun> <verb> form takes an optional leading <repo> to scope it, e.g. <front-door> <repo> spec implement <id>.
Compatibility spellings, still accepted and read as the form shown:
<front-door> auto = <front-door> handoff auto
<front-door> drain [max-items] [repo] = <front-door> handoff drain [max-items] [repo]
<front-door> handoff:<id> = <front-door> handoff start <id>
<front-door> new <request> = <front-door> spec new <request>
<front-door> implement [spec] <id> = <front-door> spec implement <id>
<front-door> continue [<id>] = <front-door> spec continue [<id>]
<front-door> fix <request> = <front-door> spec fix <request>
<front-door> brainstorm <idea> = <front-door> spec explore <idea>
<front-door> spec brainstorm <idea> = <front-door> spec explore <idea>
<front-door> route:<A-J> [<id>] = <front-door> spec route <A-J> [<id>]
<front-door> pr = <front-door> pr fix
The grammar is <front-door> [<repo>] <noun> <verb> [args] with four nouns:
handoff (the work queue), spec (spec-driven work), pr (an open pull
request), and decision (the human-decision queue). Forms are listed in the
order the parser checks them, so an earlier line wins over a later one. A noun typed without a recognised verb shows this
reference for that noun instead of being routed as free text.
Two bare shortcuts sit outside the noun-verb shape on purpose: <brief-id>
(the same as handoff start <id>) and <repo>. <brief-id> is a Worktrail
queue handoff identifier, such as 20260726-140500. A specification
identifier is deterministic when used with spec implement <id> or
spec route <A-J> <id>. A bare spec name may instead be interpreted through
the dashboard picker.
handoff auto runs one queue item. handoff drain runs multiple items with
fresh contexts. The standalone drain skill is intentionally not user-facing.
The compatibility spellings are permanent, not deprecated: nothing that worked
before the noun-verb grammar stops working. handoff:<id> in particular stays
the internal dispatch spelling between worktrail-go and its executor; the
front-door spelling is handoff start <id> or the bare <brief-id>.
Answering a filed decision
An unattended run that hits a genuine product decision files a record instead
of guessing, then blocks the brief until you answer. <front-door> decision list shows what is open, and <front-door> decision answer <decision-id>
walks you through that record's Question/Background/Options interactively and
records your answer. The bare <front-door> dashboard surfaces the same open
decisions as a picker category. Full interactive procedure:
../worktrail-go/references/answer-decision.md.
For non-interactive use (e.g. scripting an answer), the underlying CLI is still available directly:
worktrail-decision list everything open/answered/resolved
worktrail-decision answer <id> --answer "..." record your answer
The blocked brief unblocks automatically once you answer; the next drain pass
picks it back up. Full filing/resuming procedure:
../worktrail-go/references/decision-queue.md.
04 同仓库更多 Skills
worktrail-sdd-workflow
Internal SDD workflow executor invoked by /go only. Do not call directly. Executes classified routes A–J: feature planning, implementation (parallel orchestration, PR generation), defect repair, refactoring, spec changes, investigation, and workflow evolution.
worktrail-routing-config
Configure Worktrail's agent routing table (`~/.worktrail/routing.yaml`, or a repo-local `routing:` policy block) — which harness/model executes each role and tier, and how fallback between them works. Use when the operator wants to add or remove a harness/adapter (claude/codex/opencode), add a model to an existing harness (e.g. adding a DeepSeek model to opencode), pin or change who does code review, add a new tier or purpose mapping, change the default tier, or is confused about which harness actually served a spawn (e.g. "why did this use Codex when I only configured Claude"). Trigger phrases: "routing.yaml", "add a harness", "disable a harness", "add an adapter", "remove an adapter", "add a model", "add deepseek to opencode", "change the reviewer", "pin the reviewer", "routing tiers", "routing targets", "default_tier", "independent reviewer", "why did codex get called". This skill is about *editing the config file*; it does not cover `/go`'s own dispatch mechanics (see `worktrail-go`'s SKILL.md Phase 7 for how `tier_for()`/`select_cell()` resolve it at runtime).
worktrail-repo-init
Bootstrap a new repo, or migrate an existing single-branch repo, onto the workspace's repo-standards doctrine (~/rules/CLAUDE.repo.md): the AGENTS.md-is-truth/CLAUDE.md-imports-it split, a dev/prd, dev/stg/prd, or main-only (trunk) branch model with matching GitHub rulesets, an OpenSpec scaffold, an auto-merge workflow, and a seeded .worktrail/policy.yaml. Trigger phrases: "onboard this repo", "apply repo standards", "initialize repo standards", "set up this repo like the rest of the fleet", "bring this repo into line with the repo standards doctrine".
worktrail-handoff
Capture a discovered problem, gap, tech debt, or deferred work into a local work queue so a future agent session can pick it up cold. Use mid-session whenever you set work aside instead of doing it now — a fix you judge out of scope for this PR, work that belongs in a follow-up or a separate/later PR, an item you're deferring, or something worth fixing you won't tackle now — so the outstanding item isn't lost without derailing current work; can be called multiple times per session. Trigger phrases: "defer this", "item deferred", "out of scope for this PR", "follow-up work", "leave for another PR", "capture for later", "outstanding item". This skill captures only. Picking a brief back up is the front door's job: worktrail-go <brief-id>.
worktrail-go
Use when the user invokes worktrail-go, asks to pick up queued work, resume active specs, implement or fix a spec, route engineering work, or orient across repositories. Renders the orientation dashboard, classifies free-text requests, claims/resumes handoff briefs, and dispatches SDD work without requiring the user to know sdd-workflow. Grammar: worktrail-go [REPO] <noun> <verb>, nouns handoff / spec / pr / decision. Triggers: worktrail-go, worktrail-go help, worktrail-go spec fix, worktrail-go spec implement, worktrail-go spec route F, worktrail-go handoff new, worktrail-go handoff auto, worktrail-go decision answer, worktrail-go BRIEF-ID, bare worktrail-go, multi-repo orientation.
openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.