菜单
List work-items from the beads-backed work-items store, optionally filtered by lane, origin, gap id, or spec-commitment hint. Use when the user asks what work exists or wants the store enumerated. Read-only.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/thewoolleyman/livespec-orchestrator-beads-fabro --skill livespec-orchestrator-beads-fabro-list-work-items命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Detect specification-to-implementation gaps, then file a gap-tied work-item per gap with per-gap user consent. Use when the user wants detected gaps turned into tracked work. Mutating: it writes one record per consented gap.
Detect implementation-to-specification drift and hand each finding off to the propose-change operation with user consent. Use when the implementation has moved ahead of the spec and the spec must catch up. Mutating: it files proposed changes the user approves.
File an implementation-side work item directly from free-form user intent — a bug, a refactor, a tactical task. Use when the user wants something recorded in the work-items store that no gap or drift detection produced. Mutating: it writes a record after the user consents.
基于 SOC 职业分类
正在显示 SKILL.md
| name | livespec-orchestrator-beads-fabro-list-work-items |
| description | List work-items from the beads-backed work-items store, optionally filtered by lane, origin, gap id, or spec-commitment hint. Use when the user asks what work exists or wants the store enumerated. Read-only. |
| allowed-tools | bash |
This file is the thin pi binding of the list-work-items operation of the
livespec-orchestrator-beads-fabro plugin, per
this repository's SPECIFICATION/contracts.md (the pi skill surface contract). It carries pi-runtime
mechanics ONLY. The behavior lives in the plugin's reference wrapper
scripts/bin/list_work_items.py; this binding resolves the plugin root and
dispatches to it, adding no operation behavior of its own.
pi's skill namespace is flat — a skill name admits no colon — so this
plugin's namespace is carried by the unabbreviated livespec-orchestrator-beads-fabro- name
prefix rather than by the /livespec-orchestrator-beads-fabro:list-work-items form the Claude and Codex
surfaces use. The operation, its flags, and its output are identical
across all three runtimes.
$PLUGIN_ROOT)The ordered algorithm is realized ONCE, by this package's
lib/resolve-plugin-root.sh, and MUST NOT be restated inline here.
Twelve independently-maintained inline copies of a resolution rule are
kept in agreement only by copying, and that is exactly how one
positional defect came to live in every binding of a sibling Driver at
once.
<skill-dir> below is the directory holding THIS SKILL.md — you read
this file from disk, so you know its absolute path; the resolver sits
two levels up, beside the bindings tree.
PLUGIN_ROOT="$(bash "<skill-dir>/../../lib/resolve-plugin-root.sh" .)" || exit 1
echo "$PLUGIN_ROOT"
The resolver searches, in order: the LIVESPEC_ORCH_PLUGIN_ROOT
override; the governed project's own plugin directory when that checkout
IS this plugin (dogfooding); the project-scope pi package clone under
.pi/git/github.com/thewoolleyman/livespec-orchestrator-beads-fabro/; and the user-scope clone
under ~/.pi/agent/git/github.com/thewoolleyman/livespec-orchestrator-beads-fabro/.
On failure the resolver writes its own diagnostic to stderr and exits 1.
STOP and surface that diagnostic verbatim. Do not improvise a path, and
do not run an install command the diagnostic did not ask for — under a
non-interactive pi run (-p, --mode json, --mode rpc) a failure is
frequently pi's project-trust gate silently ignoring project packages
rather than a missing install.
python3 "$PLUGIN_ROOT/scripts/bin/list_work_items.py" "$@"
The supported flags are the wrapper's own; pass through whatever the user supplied and let the wrapper validate them. A usage error exits 2 and a precondition failure exits 3 — surface either verbatim rather than retrying with guessed arguments.
Surface the wrapper's stdout verbatim. Do NOT re-interpret, re-summarize, or re-rank it: every listing, ranking, filtering, and formatting decision belongs to the wrapper, which is the same code the Claude and Codex surfaces call.