[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DARJ7CHSR44491W6D6PCEP":3,"skill-same:01M6DARJ7CHSR44491W6D6PCEP":112},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":52,"commitSha":53,"skillDirectory":54,"forksCount":13,"repositoryHtmlUrl":55,"repositoryHomepageUrl":6,"ownerHtmlUrl":56,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":57,"install":58,"resources":71},"01M6DARJ7CHSR44491W6D6PCEP","beads-orchestration",null,"Use for any Beads (`bd`) issue workflow in a Beads-backed repository — coordinating unattended execution of ready issues through long-lived worker lanes (finishing started epics first, alone or with several coordinators on one backlog), running a self-paced coordinator-free lane under `\u002Floop` (one of several tmux panes), implementing a cohesive delivery package in a worktree, handling PR-review follow-up tasks, reconciling stale worker\u002FPR\u002Fworktree state, or creating and decomposing backlog issues. Route to exactly one subskill per task.","tzeusy-org\u002Fai-bootstrap","tzeusy-org","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141543652?v=4","01M6DAM1AP09H27BYGFY9QCNPB","01M6DAM1F4R187EK11XDN9JZKH",0,"MIT","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"orchestration","beads","beads orchestration","git worktree","route","self","review","issue workflow","tasks","coordinator","implementing","workflow","free","loop","uv","worker","issues","up","openai codex","ready","2026-11-10 10:12:30",false,"---\nname: beads-orchestration\ndescription: Use for any Beads (`bd`) issue workflow in a Beads-backed repository — coordinating unattended execution of ready issues through long-lived worker lanes (finishing started epics first, alone or with several coordinators on one backlog), running a self-paced coordinator-free lane under `\u002Floop` (one of several tmux panes), implementing a cohesive delivery package in a worktree, handling PR-review follow-up tasks, reconciling stale worker\u002FPR\u002Fworktree state, or creating and decomposing backlog issues. Route to exactly one subskill per task.\nmetadata:\n  owner: tze\n  authors:\n    - tze\n    - OpenAI Codex\n    - Claude Fable 5.1\n    - Claude Opus 5.5\n  status: active\n  last_reviewed: \"2026-11-06\"\ncompatibility: Requires bd (beads) CLI v1.3+, git, and a Beads-backed repository. Execution subskills additionally require gh (authenticated), jq, python3, uv, and git worktree support.\n---\n\n# Beads Orchestration\n\nSuperskill router for the Beads issue-execution fleet. Six subskills live under\n`subskills\u002F`; each is a complete standard skill package (own `SKILL.md`,\n`references\u002F`, `scripts\u002F`). Subskills are **not** installed in the global skill\ncatalog — discover them lazily from this package, and load **at most one**\nsubskill body per task (the coordinator may additionally point dispatched\nworkers at a second one; the workers load it themselves; a looper loads the\none execution subskill its mode runs).\n\n## Discover subskills\n\n```bash\nPKG=\"$(dirname \"\u003Cabsolute-path-to-this-SKILL.md>\")\"\nfind \"$PKG\u002Fsubskills\" -maxdepth 2 -name SKILL.md\nrg -n \"^name:|^description:\" \"$PKG\"\u002Fsubskills\u002F*\u002FSKILL.md\n```\n\nResolve every bundled `scripts\u002F` and `references\u002F` path from the absolute\nlocation of the `SKILL.md` the runtime loaded. A dispatched worker's cwd is its\nworktree in the target repository, not this package, so a bare relative path\nresolves against the wrong tree.\n\n## Routing table\n\n| Task intent | Subskill | Typical trigger |\n|---|---|---|\n| Run the unattended loop: rank ready issues finish-first, claim, dispatch workers, reconcile outcomes; one or several coordinators per tracker. Owns lifecycle writes for its dispatched owners. | [subskills\u002Fbeads-coordinator\u002FSKILL.md](subskills\u002Fbeads-coordinator\u002FSKILL.md) | \"while true, tackle the next issue\", \"keep N workers processing the backlog\", \"run a second coordinator on the same backlog\" |\n| Run this session as one self-paced lane with no central coordinator: implement mode claims, works, verifies, and retains a bounded outcome through packages and corrections; review mode independently reviews packages and reports to their owners. Several loopers share one tracker. | [subskills\u002Fbeads-looper\u002FSKILL.md](subskills\u002Fbeads-looper\u002FSKILL.md) | \"\u002Floop through the ready queue\", \"run this pane as a beads lane\", \"be the review lane for the other panes\" |\n| Implement one cohesive delivery package (one or several beads); requires anchor ISSUE_ID and WORKTREE_PATH. | [subskills\u002Fbeads-worker\u002FSKILL.md](subskills\u002Fbeads-worker\u002FSKILL.md) | Dispatched with a worker contract for one delivery package |\n| Process one `pr-review-task` bead: triage threads, report corrections to the implementation lane, attest exact-head merge readiness. | [subskills\u002Fbeads-pr-reviewer-worker\u002FSKILL.md](subskills\u002Fbeads-pr-reviewer-worker\u002FSKILL.md) | Dispatched with a `pr-review-task` bead for an open GitHub PR |\n| Reconcile stale worker state, PR-review bookkeeping, and orphaned worktrees before dispatching new work. | [subskills\u002Fbeads-cleanup\u002FSKILL.md](subskills\u002Fbeads-cleanup\u002FSKILL.md) | Coordinator preflight; recovery after a crashed loop; \"clean up stale beads state\" |\n| Create or decompose backlog issues: features, bugs, epics, grooming, vague ask → actionable beads. | [subskills\u002Fbeads-writer\u002FSKILL.md](subskills\u002Fbeads-writer\u002FSKILL.md) | \"file beads for X\", \"break this epic down\", backlog grooming |\n\n## Routing rules\n\n- **Coordinator vs. looper vs. worker**: if the request is to *process the\n  backlog*, route to the coordinator — never start implementing issues\n  yourself — unless it asks for a self-paced lane, a `\u002Floop`, one of several\n  independent panes, or no central coordinator: route that to the looper,\n  which is its own coordinator for one lane. Route to a\n  worker subskill only when a coordinator\u002Foperator has already supplied the\n  worker contract (ISSUE_ID, WORKTREE_PATH).\n- **Cleanup is a preflight, not a loop**: the coordinator invokes it before its\n  first cycle; route to it directly only for explicit recovery\u002Faudit asks.\n- **Writer is standalone**: backlog creation needs no worktrees and no\n  coordinator; it never dispatches execution.\n- **Fallback**: if the task is Beads-adjacent but none of the rows fit (e.g.\n  one-off `bd` queries, project prioritization), do not load a subskill — use\n  plain `bd` commands or a dedicated skill such as `th-projects`\n  (project-direction subskill).\n\n## Delivery model\n\nExecution defaults to persistent bounded-outcome owners using the existing looper;\ncoordinated runs use the same model with a small allocation\u002Frecovery controller.\nRead [references\u002Fdelivery-model.md](references\u002Fdelivery-model.md) for package units,\nbranch choice, claims, review, evidence and recovery. This replaces per-bead\nbranch\u002FPR\u002Freview ceremonies; it does not bypass repository integration policy.\n\n## Shared invariants (all subskills)\n\n- During an execution run, the coordinator is the **sole mutation authority**\n  for canonical lifecycle state (`bd create\u002Fupdate\u002Fdep\u002Fclose`); dispatched\n  workers and cleanup report instead of mutating. With several coordinators,\n  each mutates only the beads it holds, under its own `--actor` id. A looper is\n  a coordinator for exactly the beads it holds. The standalone beads-writer\n  may create\u002Fupdate\u002Fdepend backlog items during explicit authoring before\n  dispatch, but hands mutation authority to the coordinator once execution\n  starts.\n- Implementation worktrees use `.worktrees\u002Fparallel-agents\u002F\u003Canchor>` on\n  `agent\u002F\u003Canchor>`; independent review snapshots use `review\u002F\u003Creview-id>`.\n- `.beads\u002F` is Dolt-backed and gitignored — never commit it to code branches.\n- **Build artifacts follow the package.** Reuse one target across package commits.\n  Retain receipts needed for evidence\u002Frecovery, then delete retired build targets\n  after verified completion or published handoff. A PR opening or one member\n  closing is not permission to delete unfinished or unpublished package work.\n- bd has no `--rig` flag: target another project with `bd -C \u003Cpath> …`.\n- **Execute the governing contract.** Use the proportional\n  [work-allocation contract](..\u002Fth-projects\u002Freferences\u002Fwork-allocation.md#governing-contract)\n  to establish scope and acceptance; a formal spec is required only where the\n  work or repository requires one. Respect existing doctrine\u002Fspecs and route\n  unresolved scope, architecture, trust, or authorization through its real gate.\n- **Finish outcomes before starting new ones.** The coordinator ranks ready\n  work so a pool of lanes completes a few epics instead of half-building many\n  (`subskills\u002Fbeads-coordinator\u002Fscripts\u002Frank_ready_work.py`). Reports count\n  merged outcomes and name partial ones; bead, PR, and commit counts are\n  activity, not delivery.\n- **Decide, don't defer.** Engineering-judgment choices are resolved\n  autonomously per [`references\u002Fdecision-autonomy.md`](references\u002Fdecision-autonomy.md);\n  blocking on a human is reserved for its hard-gate list. Load that file before\n  filing or reconciling any decision-shaped blocker.\n- **Spend tokens like money; cache first.** All subskills follow\n  [`references\u002Ftoken-efficiency.md`](references\u002Ftoken-efficiency.md). Lanes\n  over fan-out: one long-lived session works through a chain of beads that\n  share context, one at a time, rides autocompaction, and keeps its cache warm,\n  instead of spawning a fresh cold worker per bead. Tracking beads retain individual claims\u002Facceptance; a package shares branch, PR\n  and independent review. Also: project JSON through `jq`, route gate\n  output to files, run targeted tests before the full gate's one run per tree\n  (in the tier the repo's test-scope policy assigns it), and keep one\n  model per lane. Load it once per session before the first `bd`\u002F`gh` query\n  loop.\n- **Quality gates travel with the work.** `beads-worker` and\n  `beads-pr-reviewer-worker` share\n  [`references\u002Fcraft-and-care-gate.md`](references\u002Fcraft-and-care-gate.md)\n  (the repo-defined execution-quality bar) and\n  [`references\u002Ftest-growth-gate.md`](references\u002Ftest-growth-gate.md) (one gate\n  species per behavior, a `Tests: +a ~b -c` delta in every PR). Load them at\n  the subskill's first edit or first finding, not at dispatch.\n- **Finish on a report, not a question.** A dispatched subskill ends only in\n  its defined report (a terminal status, or the shaping writer's returned bead\n  text), never mid-task on a plan, a promise, or a \"shall I\". It decides what\n  `references\u002Fdecision-autonomy.md` lets it decide; only an external or\n  hard-gated blocker is reported as blocked. The coordinator ends at its\n  frontier stop, an owner stop, or a tracker fault it cannot recover. Every\n  report is written for a reader who has not seen the session.\n- **The owner's instructions outrank skill defaults.** A direct instruction\n  from the human owner or operator (not a dispatching agent), or the target\n  repo's `AGENTS.md` \u002F `CLAUDE.md`, overrides this package's defaults: lane\n  count, routing, cadence, model tier. It does not lift mutation authority,\n  worktree isolation, exact-head review, or the hard gates in\n  `references\u002Fdecision-autonomy.md`. When one of those pauses work, name the\n  rule and its file in the report.\n\n## When `bd` itself misbehaves\n\nOn any unexpected `bd` error (connection failures, unknown flags, refused\nmutations, weird exit states), consult\n[`references\u002Fknown-errors.md`](references\u002Fknown-errors.md) **before**\ndebugging from scratch — it catalogs known errors, deprecations, and\nworkarounds. Search it instead of reading it whole: run\n`rg -i -n '\u003Cdistinctive error text>' \u003Cthis package>\u002Freferences\u002Fknown-errors.md`,\nthen read only the matching section (fall back to skimming the headers via\n`rg -n '^##' …` if the search misses). If you hit a rough edge that is not\nlisted, append an entry after resolving it: that file is this skill's\npersistent memory, and an unrecorded fix gets re-debugged by the next session.\n","# Beads Orchestration\n\nSuperskill router for the Beads issue-execution fleet. Six subskills live under\n`subskills\u002F`; each is a complete standard skill package (own `SKILL.md`,\n`references\u002F`, `scripts\u002F`). Subskills are **not** installed in the global skill\ncatalog — discover them lazily from this package, and load **at most one**\nsubskill body per task (the coordinator may additionally point dispatched\nworkers at a second one; the workers load it themselves; a looper loads the\none execution subskill its mode runs).\n\n## Discover subskills\n\n```bash\nPKG=\"$(dirname \"\u003Cabsolute-path-to-this-SKILL.md>\")\"\nfind \"$PKG\u002Fsubskills\" -maxdepth 2 -name SKILL.md\nrg -n \"^name:|^description:\" \"$PKG\"\u002Fsubskills\u002F*\u002FSKILL.md\n```\n\nResolve every bundled `scripts\u002F` and `references\u002F` path from the absolute\nlocation of the `SKILL.md` the runtime loaded. A dispatched worker's cwd is its\nworktree in the target repository, not this package, so a bare relative path\nresolves against the wrong tree.\n\n## Routing table\n\n| Task intent | Subskill | Typical trigger |\n|---|---|---|\n| Run the unattended loop: rank ready issues finish-first, claim, dispatch workers, reconcile outcomes; one or several coordinators per tracker. Owns lifecycle writes for its dispatched owners. | [subskills\u002Fbeads-coordinator\u002FSKILL.md](subskills\u002Fbeads-coordinator\u002FSKILL.md) | \"while true, tackle the next issue\", \"keep N workers processing the backlog\", \"run a second coordinator on the same backlog\" |\n| Run this session as one self-paced lane with no central coordinator: implement mode claims, works, verifies, and retains a bounded outcome through packages and corrections; review mode independently reviews packages and reports to their owners. Several loopers share one tracker. | [subskills\u002Fbeads-looper\u002FSKILL.md](subskills\u002Fbeads-looper\u002FSKILL.md) | \"\u002Floop through the ready queue\", \"run this pane as a beads lane\", \"be the review lane for the other panes\" |\n| Implement one cohesive delivery package (one or several beads); requires anchor ISSUE_ID and WORKTREE_PATH. | [subskills\u002Fbeads-worker\u002FSKILL.md](subskills\u002Fbeads-worker\u002FSKILL.md) | Dispatched with a worker contract for one delivery package |\n| Process one `pr-review-task` bead: triage threads, report corrections to the implementation lane, attest exact-head merge readiness. | [subskills\u002Fbeads-pr-reviewer-worker\u002FSKILL.md](subskills\u002Fbeads-pr-reviewer-worker\u002FSKILL.md) | Dispatched with a `pr-review-task` bead for an open GitHub PR |\n| Reconcile stale worker state, PR-review bookkeeping, and orphaned worktrees before dispatching new work. | [subskills\u002Fbeads-cleanup\u002FSKILL.md](subskills\u002Fbeads-cleanup\u002FSKILL.md) | Coordinator preflight; recovery after a crashed loop; \"clean up stale beads state\" |\n| Create or decompose backlog issues: features, bugs, epics, grooming, vague ask → actionable beads. | [subskills\u002Fbeads-writer\u002FSKILL.md](subskills\u002Fbeads-writer\u002FSKILL.md) | \"file beads for X\", \"break this epic down\", backlog grooming |\n\n## Routing rules\n\n- **Coordinator vs. looper vs. worker**: if the request is to *process the\n  backlog*, route to the coordinator — never start implementing issues\n  yourself — unless it asks for a self-paced lane, a `\u002Floop`, one of several\n  independent panes, or no central coordinator: route that to the looper,\n  which is its own coordinator for one lane. Route to a\n  worker subskill only when a coordinator\u002Foperator has already supplied the\n  worker contract (ISSUE_ID, WORKTREE_PATH).\n- **Cleanup is a preflight, not a loop**: the coordinator invokes it before its\n  first cycle; route to it directly only for explicit recovery\u002Faudit asks.\n- **Writer is standalone**: backlog creation needs no worktrees and no\n  coordinator; it never dispatches execution.\n- **Fallback**: if the task is Beads-adjacent but none of the rows fit (e.g.\n  one-off `bd` queries, project prioritization), do not load a subskill — use\n  plain `bd` commands or a dedicated skill such as `th-projects`\n  (project-direction subskill).\n\n## Delivery model\n\nExecution defaults to persistent bounded-outcome owners using the existing looper;\ncoordinated runs use the same model with a small allocation\u002Frecovery controller.\nRead [references\u002Fdelivery-model.md](references\u002Fdelivery-model.md) for package units,\nbranch choice, claims, review, evidence and recovery. This replaces per-bead\nbranch\u002FPR\u002Freview ceremonies; it does not bypass repository integration policy.\n\n## Shared invariants (all subskills)\n\n- During an execution run, the coordinator is the **sole mutation authority**\n  for canonical lifecycle state (`bd create\u002Fupdate\u002Fdep\u002Fclose`); dispatched\n  workers and cleanup report instead of mutating. With several coordinators,\n  each mutates only the beads it holds, under its own `--actor` id. A looper is\n  a coordinator for exactly the beads it holds. The standalone beads-writer\n  may create\u002Fupdate\u002Fdepend backlog items during explicit authoring before\n  dispatch, but hands mutation authority to the coordinator once execution\n  starts.\n- Implementation worktrees use `.worktrees\u002Fparallel-agents\u002F\u003Canchor>` on\n  `agent\u002F\u003Canchor>`; independent review snapshots use `review\u002F\u003Creview-id>`.\n- `.beads\u002F` is Dolt-backed and gitignored — never commit it to code branches.\n- **Build artifacts follow the package.** Reuse one target across package commits.\n  Retain receipts needed for evidence\u002Frecovery, then delete retired build targets\n  after verified completion or published handoff. A PR opening or one member\n  closing is not permission to delete unfinished or unpublished package work.\n- bd has no `--rig` flag: target another project with `bd -C \u003Cpath> …`.\n- **Execute the governing contract.** Use the proportional\n  [work-allocation contract](..\u002Fth-projects\u002Freferences\u002Fwork-allocation.md#governing-contract)\n  to establish scope and acceptance; a formal spec is required only where the\n  work or repository requires one. Respect existing doctrine\u002Fspecs and route\n  unresolved scope, architecture, trust, or authorization through its real gate.\n- **Finish outcomes before starting new ones.** The coordinator ranks ready\n  work so a pool of lanes completes a few epics instead of half-building many\n  (`subskills\u002Fbeads-coordinator\u002Fscripts\u002Frank_ready_work.py`). Reports count\n  merged outcomes and name partial ones; bead, PR, and commit counts are\n  activity, not delivery.\n- **Decide, don't defer.** Engineering-judgment choices are resolved\n  autonomously per [`references\u002Fdecision-autonomy.md`](references\u002Fdecision-autonomy.md);\n  blocking on a human is reserved for its hard-gate list. Load that file before\n  filing or reconciling any decision-shaped blocker.\n- **Spend tokens like money; cache first.** All subskills follow\n  [`references\u002Ftoken-efficiency.md`](references\u002Ftoken-efficiency.md). Lanes\n  over fan-out: one long-lived session works through a chain of beads that\n  share context, one at a time, rides autocompaction, and keeps its cache warm,\n  instead of spawning a fresh cold worker per bead. Tracking beads retain individual claims\u002Facceptance; a package shares branch, PR\n  and independent review. Also: project JSON through `jq`, route gate\n  output to files, run targeted tests before the full gate's one run per tree\n  (in the tier the repo's test-scope policy assigns it), and keep one\n  model per lane. Load it once per session before the first `bd`\u002F`gh` query\n  loop.\n- **Quality gates travel with the work.** `beads-worker` and\n  `beads-pr-reviewer-worker` share\n  [`references\u002Fcraft-and-care-gate.md`](references\u002Fcraft-and-care-gate.md)\n  (the repo-defined execution-quality bar) and\n  [`references\u002Ftest-growth-gate.md`](references\u002Ftest-growth-gate.md) (one gate\n  species per behavior, a `Tests: +a ~b -c` delta in every PR). Load them at\n  the subskill's first edit or first finding, not at dispatch.\n- **Finish on a report, not a question.** A dispatched subskill ends only in\n  its defined report (a terminal status, or the shaping writer's returned bead\n  text), never mid-task on a plan, a promise, or a \"shall I\". It decides what\n  `references\u002Fdecision-autonomy.md` lets it decide; only an external or\n  hard-gated blocker is reported as blocked. The coordinator ends at its\n  frontier stop, an owner stop, or a tracker fault it cannot recover. Every\n  report is written for a reader who has not seen the session.\n- **The owner's instructions outrank skill defaults.** A direct instruction\n  from the human owner or operator (not a dispatching agent), or the target\n  repo's `AGENTS.md` \u002F `CLAUDE.md`, overrides this package's defaults: lane\n  count, routing, cadence, model tier. It does not lift mutation authority,\n  worktree isolation, exact-head review, or the hard gates in\n  `references\u002Fdecision-autonomy.md`. When one of those pauses work, name the\n  rule and its file in the report.\n\n## When `bd` itself misbehaves\n\nOn any unexpected `bd` error (connection failures, unknown flags, refused\nmutations, weird exit states), consult\n[`references\u002Fknown-errors.md`](references\u002Fknown-errors.md) **before**\ndebugging from scratch — it catalogs known errors, deprecations, and\nworkarounds. Search it instead of reading it whole: run\n`rg -i -n '\u003Cdistinctive error text>' \u003Cthis package>\u002Freferences\u002Fknown-errors.md`,\nthen read only the matching section (fall back to skimming the headers via\n`rg -n '^##' …` if the search misses). If you hit a rough edge that is not\nlisted, append an entry after resolving it: that file is this skill's\npersistent memory, and an unrecorded fix gets re-debugged by the next session.\n",{"name":5,"metadata":43,"description":7,"compatibility":51},{"owner":44,"status":45,"authors":46,"last_reviewed":50},"tze","active",[44,47,48,49],"OpenAI Codex","Claude Fable 5.1","Claude Opus 5.5","2026-11-06","Requires bd (beads) CLI v1.3+, git, and a Beads-backed repository. Execution subskills additionally require gh (authenticated), jq, python3, uv, and git worktree support.","main","255e91995b1a1c1178f024d1e29fbe8f93b618c9","skills\u002Fpersonal\u002Fbeads-orchestration","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap","https:\u002F\u002Fgithub.com\u002Ftzeusy-org","2026-11-10 23:17:25",{"source":8,"skillName":5,"commands":59,"prompt":69,"zipAvailable":70},[60,63,66],{"tool":61,"command":62},"npx","npx skills add tzeusy-org\u002Fai-bootstrap --skill beads-orchestration",{"tool":64,"command":65},"bunx","bunx skills add tzeusy-org\u002Fai-bootstrap --skill beads-orchestration",{"tool":67,"command":68},"pnpm","pnpm dlx skills add tzeusy-org\u002Fai-bootstrap --skill beads-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002FSKILL.md",true,[72,78,82,86,90,94,98,102,108],{"path":73,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":76,"sourceHtmlUrl":77},"agents\u002Fopenai.yaml","REFERENCE","参考文档",261,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fagents\u002Fopenai.yaml",{"path":79,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Fcraft-and-care-gate.md",1394,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Freferences\u002Fcraft-and-care-gate.md",{"path":83,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Fdecision-autonomy.md",6174,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Freferences\u002Fdecision-autonomy.md",{"path":87,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fdelivery-model.md",15492,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Freferences\u002Fdelivery-model.md",{"path":91,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fknown-errors.md",140971,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Freferences\u002Fknown-errors.md",{"path":95,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":96,"sourceHtmlUrl":97},"references\u002Ftest-growth-gate.md",4025,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Freferences\u002Ftest-growth-gate.md",{"path":99,"resourceType":74,"resourceTypeDesc":75,"sizeBytes":100,"sourceHtmlUrl":101},"references\u002Ftoken-efficiency.md",4735,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Freferences\u002Ftoken-efficiency.md",{"path":103,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":106,"sourceHtmlUrl":107},"scripts\u002Fdelivery_package.py","SCRIPT","脚本",17054,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fscripts\u002Fdelivery_package.py",{"path":109,"resourceType":104,"resourceTypeDesc":105,"sizeBytes":110,"sourceHtmlUrl":111},"tests\u002Ftest_delivery_package.py",20822,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Ftests\u002Ftest_delivery_package.py",[113,139,164,179,198,209],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":38},"01M6DAZD21TWH2ET70V9FF75CQ","user-run","Use when a step needs privileges this session lacks (docker, sudo, another user's checkout or secrets, host access) and the owner must run it as tze. Writes a reviewable \u002Fhome\u002Forca\u002F.tmp\u002F\u003Cslug>\u002Frun.sh that impersonates tze (USER_TO_IMPERSONATE overrides), tees timestamped logs plus latest.log and collects artifacts there; Claude presents it with a risk and time brief, then continues from the logs. Triggers: \"I'll run it for you\", \"permission denied on docker.sock\", \"needs sudo\", \"sudo: a password is required\", \"run as tze\", \"\u002Fuser-run\".","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fuser-run\u002FSKILL.md",[],[120,121,122,123,124,125,126,127,128,129,45,130,131,132,133,134,135,136,137,138],"user run","user","run","docker","logs","use","host","as","triggers","permission","time","log","artifacts","session","password","access","secrets","risk","brief",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":155,"publishedAt":38},"01M6DAZAHTCBAD2WF0GAHWPST8","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Frequesting-code-review\u002FSKILL.md",[145,150],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":151,"categoryName":152,"taxonomyType":153,"taxonomyTypeDesc":154},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[156,157,24,158,159,160,45,161,162,125,163,26],"requesting code review","code","code review","work","requirements","upstream","superpowers","verify",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":172,"publishedAt":38},"01M6DAZ7CJ82D81XZB2YHVVY48","receiving-code-review","Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Freceiving-code-review\u002FSKILL.md",[170,171],{"categoryNo":146,"categoryName":147,"taxonomyType":148,"taxonomyTypeDesc":149},{"categoryNo":151,"categoryName":152,"taxonomyType":153,"taxonomyTypeDesc":154},[173,157,24,158,45,161,174,162,125,175,176,177,178],"receiving code review","implementation","code review feedback","technical","feedback","verification",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":38},"01M6DAZ4ER76ADXJ9KRFP7V3Q9","finishing-a-development-branch","Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Ffinishing-a-development-branch\u002FSKILL.md",[],[186,187,188,189,125,190,159,191,192,193,162,194,195,196,45,161,197,174],"branch","development","finishing a development branch","integrate","decide","how","cleanup","pr","merge","tests","structured","options",{"skillNo":199,"name":200,"nameZh":6,"description":201,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":202,"categories":203,"keywords":204,"publishedAt":38},"01M6DAYZFWWW2YPKP89QNQR96H","executing-plans","Use when you have a written implementation plan to execute in a separate session with review checkpoints","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Fexecuting-plans\u002FSKILL.md",[],[205,206,207,24,208,45,161,174,162,125,133],"plans","executing plans","plan","execute",{"skillNo":210,"name":211,"nameZh":6,"description":212,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":213,"categories":214,"keywords":215,"publishedAt":38},"01M6DAYWM2YQHYCK7C35K1D29J","dispatching-parallel-agents","Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies","https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fth-workflow\u002Fsubskills\u002Fdispatching-parallel-agents\u002FSKILL.md",[],[216,217,218,125,162,161,219,45,220,26,221],"parallel agents","parallel","dispatching parallel agents","state","dependencies","shared"]