[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DAS9HMBZXR1XMBWNQQS9S1":3,"skill-same:01M6DAS9HMBZXR1XMBWNQQS9S1":92},{"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":50,"commitSha":51,"skillDirectory":52,"forksCount":13,"repositoryHtmlUrl":53,"repositoryHomepageUrl":6,"ownerHtmlUrl":54,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":55,"install":56,"resources":69},"01M6DAS9HMBZXR1XMBWNQQS9S1","beads-writer",null,"Use when creating or decomposing Beads issues for a project backlog, including new features, bugs, epics, backlog grooming, or converting vague asks into actionable Beads work in a Beads-backed repository.","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\u002Fsubskills\u002Fbeads-writer\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"beads writer","beads","writer","with","backlog grooming","can","vague","when","inspect","actionable","for","bugs","creating issues","use","issues","backlog","project","codex","openai codex","work","2026-11-10 10:12:30",false,"---\nname: beads-writer\ndescription: Use when creating or decomposing Beads issues for a project backlog, including new features, bugs, epics, backlog grooming, or converting vague asks into actionable Beads work in a Beads-backed repository.\nmetadata:\n  owner: tze\n  authors:\n    - tze\n    - OpenAI Codex\n  status: active\n  last_reviewed: \"2026-11-06\"\ncompatibility: Requires a Beads-backed repository with the `bd` CLI available. Assumes the agent can inspect the target project workspace before creating issues.\n---\n\n# Beads Writer\n\nCreate high-quality beads issues through repo-grounded research and deliberate field selection. This skill is a routing layer over the Beads operating model described in [`..\u002F..\u002F..\u002F..\u002F..\u002FREADME.md`](..\u002F..\u002F..\u002F..\u002F..\u002FREADME.md): issue writing should reinforce that workflow, not compete with it.\n\nWrite a concise current packet grounded in the proportional governing contract from work-allocation so a fresh owner can act without the creation chat. Tracking and delivery granularity differ: related existing beads may share one package while retaining their own acceptance.\n\n## Use This Skill When\n\n- A user asks to create one or more beads issues for a feature, bug, task, or backlog item\n- A user wants a vague ask decomposed into actionable beads or an epic with child beads\n- A discovered issue needs a proper bead instead of a quick title-only stub\n- A backlog-grooming pass needs better scope, dependencies, or acceptance criteria\n\n## Do Not Use This Skill When\n\n- The work already exists as a well-formed bead and should now be implemented: use `beads-worker`\n- The task is to review a whole repository or generate a roadmap from audit findings: use `th-projects` (project-review or project-direction subskills)\n- The task is exhaustive spec-versus-code reconciliation rather than issue writing: use `th-projects` (spec-concretization subskill)\n\n## Core Rules\n\n- Ground every bead in the target repo's actual code, naming, issue graph, and constraints before writing it.\n- Prefer one bead per testable outcome. Split unrelated acceptance criteria.\n- Apply the shared\n  [`th-projects` work-allocation contract](..\u002F..\u002F..\u002Fth-projects\u002Freferences\u002Fwork-allocation.md)\n  before creating or decomposing implementation work.\n- Keep accepted outcomes finite and visibly partial until mandatory acceptance is met.\n- Use one cross-child closeout path when needed; an existing outcome checklist or report may suffice. Do not create recursive reconciliation generations or split to meet a child-count quota.\n- Use `bd create`, not `bd q`, when you need a real description.\n- Do not pass dependency flags to `bd create`; create first, then wire with `bd dep add`.\n- Reconcile against the existing backlog before creating: `bd search` the\n  surface and title terms; attach, supersede, or reopen an existing bead\n  before filing a new one. Audit-derived batches follow\n  [`th-engineering\u002Fsubskills\u002Fgreenfield-parity\u002Freferences\u002Fidempotent-audit.md`](..\u002F..\u002F..\u002Fth-engineering\u002Fsubskills\u002Fgreenfield-parity\u002Freferences\u002Fidempotent-audit.md)\n  (ledger, audit-key, convergence record) so re-runs file nothing twice.\n- Stamp an execution-complexity label on every bead at creation:\n  `complexity:low`, `complexity:medium`, `complexity:high`, or\n  `complexity:epic`. The coordinator maps this label straight to a worker\n  model tier unless the design\u002Fspecification override or Reconciliation Floor\n  in `..\u002Fbeads-coordinator\u002Freferences\u002Fruntime-and-safety.md` applies. Calibrate\n  honestly: `low` is docs\u002Fconfig\u002Ftest-only or single-file mechanical work with\n  no design judgment; when in doubt between two tiers, pick the lower — the\n  coordinator escalates on evidence.\n- Keep non-lane work out of the dispatch queue with one of two labels, which\n  `rank_ready_work.py` excludes:\n  - `no-dispatch` for tracking or meta beads, such as a trial log, a decision\n    record, or an owner checklist.\n  - `scope:local-state` for work on gitignored state that exists only in the\n    main checkout (`.beads\u002F` leftovers, caches, local databases), which no\n    worktree reaches. Split a mixed bead so the tracked-file part stays\n    ordinary lane work; the owner does the local-state part, or names a\n    looper for it.\n\n## Read Order\n\n| File | Read when | Content |\n|------|-----------|---------|\n| [`references\u002Fworkflow.md`](references\u002Fworkflow.md) | Every real use of this skill | Research-first workflow, decomposition rules, creation sequence, and verification flow |\n| [`..\u002F..\u002F..\u002Fth-projects\u002Freferences\u002Fwork-allocation.md`](..\u002F..\u002F..\u002Fth-projects\u002Freferences\u002Fwork-allocation.md) | Shaping implementation boundaries or dispatch packets | Proportional governing contracts, cohesive delivery boundaries, current packets, and readiness |\n| [`references\u002Ffields-and-examples.md`](references\u002Ffields-and-examples.md) | Crafting issue text or choosing fields | Field schema, type\u002Fpriority guidance, and example beads |\n| [`references\u002Freconciliation-beads.md`](references\u002Freconciliation-beads.md) | Writing or checking an epic | Finite outcome closeout, optional closeout-bead contract, and evidence prompt |\n| [`references\u002Fquality-checklist.md`](references\u002Fquality-checklist.md) | Before finalizing or after creating beads | Final checklist, persistence checks, and anti-patterns |\n\n## Trigger Sanity Check\n\n- Should trigger: \"Break this feature request into beads and make sure each child has enough context for a fresh worker.\"\n- Should not trigger: \"Implement bead `bd-123` in its assigned worktree.\"\n\n## Resources\n\n### references\u002F\n- `workflow.md` — Primary execution flow for research, decomposition, creation, and verification.\n- `fields-and-examples.md` — Field schema, type selection guide, priority calibration table, and exemplary beads.\n- `reconciliation-beads.md` — Finite outcome closeout and an optional verification prompt.\n- `quality-checklist.md` — Final review checklist, persistence checks, and anti-patterns to remove.\n","# Beads Writer\n\nCreate high-quality beads issues through repo-grounded research and deliberate field selection. This skill is a routing layer over the Beads operating model described in [`..\u002F..\u002F..\u002F..\u002F..\u002FREADME.md`](..\u002F..\u002F..\u002F..\u002F..\u002FREADME.md): issue writing should reinforce that workflow, not compete with it.\n\nWrite a concise current packet grounded in the proportional governing contract from work-allocation so a fresh owner can act without the creation chat. Tracking and delivery granularity differ: related existing beads may share one package while retaining their own acceptance.\n\n## Use This Skill When\n\n- A user asks to create one or more beads issues for a feature, bug, task, or backlog item\n- A user wants a vague ask decomposed into actionable beads or an epic with child beads\n- A discovered issue needs a proper bead instead of a quick title-only stub\n- A backlog-grooming pass needs better scope, dependencies, or acceptance criteria\n\n## Do Not Use This Skill When\n\n- The work already exists as a well-formed bead and should now be implemented: use `beads-worker`\n- The task is to review a whole repository or generate a roadmap from audit findings: use `th-projects` (project-review or project-direction subskills)\n- The task is exhaustive spec-versus-code reconciliation rather than issue writing: use `th-projects` (spec-concretization subskill)\n\n## Core Rules\n\n- Ground every bead in the target repo's actual code, naming, issue graph, and constraints before writing it.\n- Prefer one bead per testable outcome. Split unrelated acceptance criteria.\n- Apply the shared\n  [`th-projects` work-allocation contract](..\u002F..\u002F..\u002Fth-projects\u002Freferences\u002Fwork-allocation.md)\n  before creating or decomposing implementation work.\n- Keep accepted outcomes finite and visibly partial until mandatory acceptance is met.\n- Use one cross-child closeout path when needed; an existing outcome checklist or report may suffice. Do not create recursive reconciliation generations or split to meet a child-count quota.\n- Use `bd create`, not `bd q`, when you need a real description.\n- Do not pass dependency flags to `bd create`; create first, then wire with `bd dep add`.\n- Reconcile against the existing backlog before creating: `bd search` the\n  surface and title terms; attach, supersede, or reopen an existing bead\n  before filing a new one. Audit-derived batches follow\n  [`th-engineering\u002Fsubskills\u002Fgreenfield-parity\u002Freferences\u002Fidempotent-audit.md`](..\u002F..\u002F..\u002Fth-engineering\u002Fsubskills\u002Fgreenfield-parity\u002Freferences\u002Fidempotent-audit.md)\n  (ledger, audit-key, convergence record) so re-runs file nothing twice.\n- Stamp an execution-complexity label on every bead at creation:\n  `complexity:low`, `complexity:medium`, `complexity:high`, or\n  `complexity:epic`. The coordinator maps this label straight to a worker\n  model tier unless the design\u002Fspecification override or Reconciliation Floor\n  in `..\u002Fbeads-coordinator\u002Freferences\u002Fruntime-and-safety.md` applies. Calibrate\n  honestly: `low` is docs\u002Fconfig\u002Ftest-only or single-file mechanical work with\n  no design judgment; when in doubt between two tiers, pick the lower — the\n  coordinator escalates on evidence.\n- Keep non-lane work out of the dispatch queue with one of two labels, which\n  `rank_ready_work.py` excludes:\n  - `no-dispatch` for tracking or meta beads, such as a trial log, a decision\n    record, or an owner checklist.\n  - `scope:local-state` for work on gitignored state that exists only in the\n    main checkout (`.beads\u002F` leftovers, caches, local databases), which no\n    worktree reaches. Split a mixed bead so the tracked-file part stays\n    ordinary lane work; the owner does the local-state part, or names a\n    looper for it.\n\n## Read Order\n\n| File | Read when | Content |\n|------|-----------|---------|\n| [`references\u002Fworkflow.md`](references\u002Fworkflow.md) | Every real use of this skill | Research-first workflow, decomposition rules, creation sequence, and verification flow |\n| [`..\u002F..\u002F..\u002Fth-projects\u002Freferences\u002Fwork-allocation.md`](..\u002F..\u002F..\u002Fth-projects\u002Freferences\u002Fwork-allocation.md) | Shaping implementation boundaries or dispatch packets | Proportional governing contracts, cohesive delivery boundaries, current packets, and readiness |\n| [`references\u002Ffields-and-examples.md`](references\u002Ffields-and-examples.md) | Crafting issue text or choosing fields | Field schema, type\u002Fpriority guidance, and example beads |\n| [`references\u002Freconciliation-beads.md`](references\u002Freconciliation-beads.md) | Writing or checking an epic | Finite outcome closeout, optional closeout-bead contract, and evidence prompt |\n| [`references\u002Fquality-checklist.md`](references\u002Fquality-checklist.md) | Before finalizing or after creating beads | Final checklist, persistence checks, and anti-patterns |\n\n## Trigger Sanity Check\n\n- Should trigger: \"Break this feature request into beads and make sure each child has enough context for a fresh worker.\"\n- Should not trigger: \"Implement bead `bd-123` in its assigned worktree.\"\n\n## Resources\n\n### references\u002F\n- `workflow.md` — Primary execution flow for research, decomposition, creation, and verification.\n- `fields-and-examples.md` — Field schema, type selection guide, priority calibration table, and exemplary beads.\n- `reconciliation-beads.md` — Finite outcome closeout and an optional verification prompt.\n- `quality-checklist.md` — Final review checklist, persistence checks, and anti-patterns to remove.\n",{"name":5,"metadata":43,"description":7,"compatibility":49},{"owner":44,"status":45,"authors":46,"last_reviewed":48},"tze","active",[44,47],"OpenAI Codex","2026-11-06","Requires a Beads-backed repository with the `bd` CLI available. Assumes the agent can inspect the target project workspace before creating issues.","main","ac0f8a90dbdbae93825f4db9614ade0d6872c26d","skills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-writer","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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add tzeusy-org\u002Fai-bootstrap --skill beads-writer",{"tool":62,"command":63},"bunx","bunx skills add tzeusy-org\u002Fai-bootstrap --skill beads-writer",{"tool":65,"command":66},"pnpm","pnpm dlx skills add tzeusy-org\u002Fai-bootstrap --skill beads-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-writer\u002FSKILL.md",true,[70,76,80,84,88],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"agents\u002Fopenai.yaml","REFERENCE","参考文档",313,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-writer\u002Fagents\u002Fopenai.yaml",{"path":77,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Ffields-and-examples.md",7300,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-writer\u002Freferences\u002Ffields-and-examples.md",{"path":81,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":82,"sourceHtmlUrl":83},"references\u002Fquality-checklist.md",2895,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-writer\u002Freferences\u002Fquality-checklist.md",{"path":85,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Freconciliation-beads.md",3508,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-writer\u002Freferences\u002Freconciliation-beads.md",{"path":89,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fworkflow.md",5376,"https:\u002F\u002Fgithub.com\u002Ftzeusy-org\u002Fai-bootstrap\u002Fblob\u002Fmain\u002Fskills\u002Fpersonal\u002Fbeads-orchestration\u002Fsubskills\u002Fbeads-writer\u002Freferences\u002Fworkflow.md",[93,118,144,159,178,189],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[100,101,102,103,104,31,105,106,107,108,45,109,110,111,112,113,114,115,116,117],"user run","user","run","docker","logs","host","as","triggers","permission","time","log","artifacts","session","password","access","secrets","risk","brief",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":134,"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",[124,129],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",{"categoryNo":130,"categoryName":131,"taxonomyType":132,"taxonomyTypeDesc":133},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[135,136,137,138,37,139,45,140,141,31,142,143],"requesting code review","code","review","code review","requirements","upstream","superpowers","verify","tasks",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":152,"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",[150,151],{"categoryNo":125,"categoryName":126,"taxonomyType":127,"taxonomyTypeDesc":128},{"categoryNo":130,"categoryName":131,"taxonomyType":132,"taxonomyTypeDesc":133},[153,136,137,138,45,140,154,141,31,155,156,157,158],"receiving code review","implementation","code review feedback","technical","feedback","verification",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"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",[],[166,167,168,169,31,170,37,171,172,173,141,174,175,176,45,140,177,154],"branch","development","finishing a development branch","integrate","decide","how","cleanup","pr","merge","tests","structured","options",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":184,"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",[],[185,186,187,137,188,45,140,154,141,31,112],"plans","executing plans","plan","execute",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"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",[],[196,197,198,31,141,140,199,45,200,143,201],"parallel agents","parallel","dispatching parallel agents","state","dependencies","shared"]