[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7F554CMJBTCM7FEP9P3Y2CM":3,"skill-same:01M7F554CMJBTCM7FEP9P3Y2CM":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":45},"01M7F554CMJBTCM7FEP9P3Y2CM","skill-work-slicing",null,"Break a plan or spec into vertical slices that each declare what blocks them — use when work is agreed but not yet cut into fileable pieces","lza6\u002FArmor-piercing-system-prompts","lza6","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F128880206?v=4","01M7EB3K7WPX5T28EJ2NVHE6EG","Chinese-tingfeng","01M7EB3K97E1KQ16QWKJMFNGX8",11,"MIT","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-work-slicing\u002FSKILL.md",[],[],"2026-11-16 10:05:34",false,"---\nname: skill-work-slicing\ndescription: \"Break a plan or spec into vertical slices that each declare what blocks them — use when work is agreed but not yet cut into fileable pieces\"\ndisable-model-invocation: true\n---\n\n> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Work Slicing\n\nTurn a plan, spec, or the conversation so far into a set of tickets. Each one is\na **vertical slice** — a narrow but complete path through every layer — and each\ndeclares the tickets that block it.\n\nThis is the step between \"we know what we are building\" and \"someone can pick up\na piece of it\". It does not decide anything: if decisions are still open, run\n`skill-pressure-test` first.\n\nBefore slicing, map unresolved decision records and their dependencies. Each\nrecord names its question, required evidence, owner, resolution, and unblocked\nimplementation. A dependency cycle withholds ready status until it is recut.\nInvalidated decisions reopen affected work rather than leaving stale completion.\n\nAdapted from `to-tickets` in\n[mattpocock\u002Fskills](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills) (MIT), retargeted at\nthis repo's trackers.\n\n## When To Use\n\n- A plan or spec exists and needs cutting into fileable work.\n- A tracking epic is too big to claim and needs children.\n- Several people or sessions will work in parallel and need boundaries.\n\n## When Not To Use\n\n- Decisions are still open. Slicing unresolved work produces tickets that get\n  reopened. Use `skill-pressure-test`.\n- The work fits one session. File one ticket, or none.\n- You want parallel *execution* across agents right now, with worktrees and\n  waves. That is `\u002Focto:parallel`, which decomposes into work packages it then\n  runs. This produces tracker state for humans and future sessions.\n\n## Inputs\n\nThe plan, spec, or conversation. Optionally a parent epic id to hang the slices\nunder.\n\n## Workflow\n\n### 1. Slice vertically\n\nEach slice cuts a narrow but complete path through every layer it touches —\nschema, API, UI, tests. It is **not a horizontal** slice of one layer.\n\n- A completed slice is demoable or verifiable on its own.\n- Each is sized to fit one fresh context window.\n- \"Add the database columns\" is horizontal and untestable alone. \"Store and\n  display the user's timezone, end to end\" is vertical.\n\nThe first slice through a new area is the tracer bullet: thin, complete, and\nproves the path exists before anything is built out along it.\n\n### 2. Declare what blocks what\n\nFor every slice, name the slices that must close first. Only real ordering\nconstraints — not preference, not tidiness. Two slices that merely touch the same\nfile are not blocked on each other; two where one cannot be verified until the\nother exists are.\n\nCycles mean the slicing is wrong, not that the tracker needs a workaround. Recut.\n\n### 3. File them\n\nThis repo has two trackers and they are not interchangeable:\n\n- **`bd` (beads) is the system of record** for work. `bd create --parent=\u003Cid>`\n  makes a child; `bd dep add \u003Cissue> \u003Cdepends-on>` makes a blocking edge;\n  `bd ready` lists what is takeable — open, unblocked, and not in progress.\n- **GitHub issues** are the public surface, via `gh`. Use them when the work is\n  externally visible or a contributor needs to see it.\n\nPut the detail in the ticket body, not in the parent. The parent indexes; the\nticket holds.\n\nUse the tracker's atomic claim operation and read ownership back before editing a\nslice. If the tracker cannot claim atomically, use one integrator and do not treat\nan assignee read followed by a write as a lock. Never overwrite another owner's\nclaim.\n\n### 4. When bd will not accept writes\n\n`bd` is periodically **write-blocked** by pending Dolt schema migrations, and the\nrepository rule is explicit: **do not run the migration** unless you are the\nsingle designated migrator, because migrating a second clone forks the schema\nirrecoverably.\n\nWhen writes are blocked, do not pretend the work was filed and do not silently\ndrop it. Instead:\n\n1. Emit the **ready-to-run `bd create` and `bd dep add` commands**, complete and\n   in dependency order, so they can be run unmodified once writes return.\n2. Write them into the plan or a roadmap note under `docs\u002Froadmaps\u002F`, which is\n   the practice this repo already follows.\n3. Say plainly, in the output, that nothing was filed and why.\n\n## Provider Or Data Priority\n\n1. The plan or spec as written.\n2. The repository, to check whether a slice is already partly built.\n3. The user, for sizing and priority. Do not invent priorities.\n\n## Stop Or Checkpoint Rules\n\n- Stop and recut if any slice cannot be verified on its own.\n- Stop if the blocking graph has a cycle.\n- Stop before filing if more than about ten slices come out of one plan — that\n  usually means the plan is really several, and filing them all buries the first.\n- Confirm the slice list with the user before filing anything. Filing is visible\n  to others and awkward to undo.\n\n## Output Contract\n\n1. **Slice list** — title, one-line scope, and what it blocks on.\n2. **Order** — which slices are takeable now, and which wait.\n3. **Filed or not filed** — ids and links if filed; if not, the exact commands\n   and the reason they were not run.\n4. **Left unsliced** — anything in the plan too vague to cut, stated as such\n   rather than forced into a ticket.\n\n## Verification\n\n- Every slice is demoable or verifiable alone.\n- No slice is a single layer's worth of work.\n- The blocking graph is acyclic and every edge is a real constraint.\n- If bd was unavailable, the emitted commands run unmodified — check the parent\n  ids and the dependency order.\n","> **Host: Codex CLI** — This skill was designed for Claude Code and adapted for Codex.\n> Cross-reference commands use installed skill names in Codex rather than `\u002Focto:*` slash commands.\n> Use the active Codex shell and subagent tools. Do not claim a provider, model, or host subagent is available until the current session exposes it.\n> For host tool equivalents, see `skills\u002Fblocks\u002Fcodex-host-adapter.md`.\n\n\n# Work Slicing\n\nTurn a plan, spec, or the conversation so far into a set of tickets. Each one is\na **vertical slice** — a narrow but complete path through every layer — and each\ndeclares the tickets that block it.\n\nThis is the step between \"we know what we are building\" and \"someone can pick up\na piece of it\". It does not decide anything: if decisions are still open, run\n`skill-pressure-test` first.\n\nBefore slicing, map unresolved decision records and their dependencies. Each\nrecord names its question, required evidence, owner, resolution, and unblocked\nimplementation. A dependency cycle withholds ready status until it is recut.\nInvalidated decisions reopen affected work rather than leaving stale completion.\n\nAdapted from `to-tickets` in\n[mattpocock\u002Fskills](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills) (MIT), retargeted at\nthis repo's trackers.\n\n## When To Use\n\n- A plan or spec exists and needs cutting into fileable work.\n- A tracking epic is too big to claim and needs children.\n- Several people or sessions will work in parallel and need boundaries.\n\n## When Not To Use\n\n- Decisions are still open. Slicing unresolved work produces tickets that get\n  reopened. Use `skill-pressure-test`.\n- The work fits one session. File one ticket, or none.\n- You want parallel *execution* across agents right now, with worktrees and\n  waves. That is `\u002Focto:parallel`, which decomposes into work packages it then\n  runs. This produces tracker state for humans and future sessions.\n\n## Inputs\n\nThe plan, spec, or conversation. Optionally a parent epic id to hang the slices\nunder.\n\n## Workflow\n\n### 1. Slice vertically\n\nEach slice cuts a narrow but complete path through every layer it touches —\nschema, API, UI, tests. It is **not a horizontal** slice of one layer.\n\n- A completed slice is demoable or verifiable on its own.\n- Each is sized to fit one fresh context window.\n- \"Add the database columns\" is horizontal and untestable alone. \"Store and\n  display the user's timezone, end to end\" is vertical.\n\nThe first slice through a new area is the tracer bullet: thin, complete, and\nproves the path exists before anything is built out along it.\n\n### 2. Declare what blocks what\n\nFor every slice, name the slices that must close first. Only real ordering\nconstraints — not preference, not tidiness. Two slices that merely touch the same\nfile are not blocked on each other; two where one cannot be verified until the\nother exists are.\n\nCycles mean the slicing is wrong, not that the tracker needs a workaround. Recut.\n\n### 3. File them\n\nThis repo has two trackers and they are not interchangeable:\n\n- **`bd` (beads) is the system of record** for work. `bd create --parent=\u003Cid>`\n  makes a child; `bd dep add \u003Cissue> \u003Cdepends-on>` makes a blocking edge;\n  `bd ready` lists what is takeable — open, unblocked, and not in progress.\n- **GitHub issues** are the public surface, via `gh`. Use them when the work is\n  externally visible or a contributor needs to see it.\n\nPut the detail in the ticket body, not in the parent. The parent indexes; the\nticket holds.\n\nUse the tracker's atomic claim operation and read ownership back before editing a\nslice. If the tracker cannot claim atomically, use one integrator and do not treat\nan assignee read followed by a write as a lock. Never overwrite another owner's\nclaim.\n\n### 4. When bd will not accept writes\n\n`bd` is periodically **write-blocked** by pending Dolt schema migrations, and the\nrepository rule is explicit: **do not run the migration** unless you are the\nsingle designated migrator, because migrating a second clone forks the schema\nirrecoverably.\n\nWhen writes are blocked, do not pretend the work was filed and do not silently\ndrop it. Instead:\n\n1. Emit the **ready-to-run `bd create` and `bd dep add` commands**, complete and\n   in dependency order, so they can be run unmodified once writes return.\n2. Write them into the plan or a roadmap note under `docs\u002Froadmaps\u002F`, which is\n   the practice this repo already follows.\n3. Say plainly, in the output, that nothing was filed and why.\n\n## Provider Or Data Priority\n\n1. The plan or spec as written.\n2. The repository, to check whether a slice is already partly built.\n3. The user, for sizing and priority. Do not invent priorities.\n\n## Stop Or Checkpoint Rules\n\n- Stop and recut if any slice cannot be verified on its own.\n- Stop if the blocking graph has a cycle.\n- Stop before filing if more than about ten slices come out of one plan — that\n  usually means the plan is really several, and filing them all buries the first.\n- Confirm the slice list with the user before filing anything. Filing is visible\n  to others and awkward to undo.\n\n## Output Contract\n\n1. **Slice list** — title, one-line scope, and what it blocks on.\n2. **Order** — which slices are takeable now, and which wait.\n3. **Filed or not filed** — ids and links if filed; if not, the exact commands\n   and the reason they were not run.\n4. **Left unsliced** — anything in the plan too vague to cut, stated as such\n   rather than forced into a ticket.\n\n## Verification\n\n- Every slice is demoable or verifiable alone.\n- No slice is a single layer's worth of work.\n- The blocking graph is acyclic and every edge is a real constraint.\n- If bd was unavailable, the emitted commands run unmodified — check the parent\n  ids and the dependency order.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","d69096e239f2a89aabc2cd078c47664a9d3b1e11","05-技能与代理开发\u002Fskill-work-slicing",3,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts","https:\u002F\u002Fgithub.com\u002Flza6","个人vx：Tf00798\r\n个人✈：@TFGY999","2026-10-08 14:29:22",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":24},[35,38,41],{"tool":36,"command":37},"npx","npx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-work-slicing",{"tool":39,"command":40},"bunx","bunx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-work-slicing",{"tool":42,"command":43},"pnpm","pnpm dlx skills add lza6\u002FArmor-piercing-system-prompts --skill skill-work-slicing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-work-slicing\u002FSKILL.md",[46],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",171,"https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F05-技能与代理开发\u002Fskill-work-slicing\u002Fagents\u002Fopenai.yaml",[53,60,65,72,79,86],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"publishedAt":19},"01M7FFG485KY83TD6HSC4YPCMC","obsidian-clipper-template-creator","Guide for creating templates for the Obsidian Web Clipper. Use when you want to create a new clipping template, understand available variables, or format clipped content.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator\u002FSKILL.md",[],[],{"skillNo":61,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7FFG0T6AZ0STEJPSB3CX84K","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobsidian-clipper-template-creator-antigravity-awesome-skills-main\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7FFFY0QEM14SKWPDYGMXM2P","python-api","Programmatic Object-Detection-Metrics API guidance for BoundingBox, BoundingBoxes, Evaluator, enums, coordinate conversion, AP\u002FmAP semantics, and source-style import diagnostics.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Fpython-api\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7FFFVZQZ2GJ0C0TGP7JHD20","file-evaluation","Folder-based PASCAL VOC AP\u002FmAP evaluation from ground-truth and detection text files.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002Fsub-skills\u002Ffile-evaluation\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7FFFSFNYSE77SJ6PE1CK2DA","object-detection-metrics","Guides legacy Object-Detection-Metrics PASCAL VOC AP\u002FmAP evaluation from detection text folders and direct Python API classes.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fobject-detection-metrics\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7FFFP0GCK1RVXBCPQ8APBMT","nx-workspace-patterns","Configure and optimize Nx monorepo workspaces. Use when setting up Nx, configuring project boundaries, optimizing build caching, or implementing affected commands.","https:\u002F\u002Fgithub.com\u002Flza6\u002FArmor-piercing-system-prompts\u002Fblob\u002Fmain\u002F07-后端与架构\u002Fnx-workspace-patterns\u002FSKILL.md",[],[]]