[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MKDS3NCT7CVH70YN4PSD99":3,"skill-same:01M6MKDS3NCT7CVH70YN4PSD99":70},{"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":23,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":46,"ownerHtmlUrl":47,"ownerBlogUrl":48,"ownerDescription":49,"updatedAt":50,"install":51,"resources":63},"01M6MKDS3NCT7CVH70YN4PSD99","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","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1566,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-work-slicing\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34],"work","skill work slicing","spec","plan","use","but","cut","blocks","true","break","when","2026-11-10 10:12:30",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":40},true,"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-work-slicing",483,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-13 02:16:32",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":40},[53,56,59],{"tool":54,"command":55},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-work-slicing",{"tool":57,"command":58},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-work-slicing",{"tool":60,"command":61},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill skill-work-slicing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-work-slicing\u002FSKILL.md",[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agents\u002Fopenai.yaml","REFERENCE","参考文档",171,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnyldn\u002Fclaude-octopus\u002Fskills\u002Fskill-work-slicing\u002Fagents\u002Fopenai.yaml",[71,79,86,93,119,144],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":78},"01M746ZWACVKMZ1BJXJZHYJSSX","migrate-to-e2e","Moves an existing Playwright, Cypress, Selenium, Appium, Detox, Maestro, or TesterArmy suite to e2e one slice at a time, with the old suite running beside the new one until each ported test is proven. Keeps a MIGRATION.md progress file so any later session resumes where the last stopped. Optionally plants a defect to show both suites catch it. Use for \u002Fmigrate-to-e2e, \"migrate our tests to e2e\", \"port these Maestro flows\", \"move our TesterArmy tests\", or when a project has an e2e config and an older suite still running.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fmigrate-to-e2e\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"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":78},"01M746ZPTAX1Q0FBKAB1CYND7E","e2e","Writes, runs, and debugs end-to-end tests for web and mobile apps with e2e, the agentic test runner, which mixes agent.act goals with exact locator assertions on a Playwright browser or an iOS or Android device. Also drives a project's running app live over the e2e MCP server to look at a screen, check a UI change, take a screenshot or record a video, and try a locator; and runs bug bashes, parallel e2e explore runs with each bug proven by a repro test. Use when a project depends on e2e or has an e2e.config.ts, when asked for end-to-end, browser, mobile, or agentic UI tests, to check a change in the running app, to QA or bug bash an app or branch, or when an e2e run fails.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fe2e\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":78},"01M746ZJN784HVHMDP9MQGCSGG","create-verification-skill","Generate a project-local verify-\u003Capp> skill on top of e2e, so any coding agent can launch the app, check it is worth driving, exercise a feature the way a user does, keep evidence, and bug bash it. Writes the skill, a feature map with one explore charter per feature, and proves it once. Use for \u002Fcreate-verification-skill, \"make a verification skill for this repo\", or when a project has no scripted way to prove UI behavior.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftester-army\u002Fe2e\u002Fskills\u002Fcreate-verification-skill\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":35},"01M716A6ETNB9B1SQ3GXZC75VR","deja-search","deja-vu memory — search the user's past AI coding sessions with the deja CLI. Holds what they already settled and never wrote into the repo (naming rules, banned or already-tried tools, required checks before merge, preferred values, who owns what). Use before your first edit in a task, before you call a change done or ready to merge, before you recommend a tool, library, design or reviewer, before re-debugging an error that may already be solved, when they say 'didn't we fix this before', 'what did we decide about X' or 'I already have that', and before telling them something on this machine does not exist.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-search\u002FSKILL.md",[],[100,101,102,103,104,105,106,107,108,109,110,34,111,112,113,114,115,116,117,118],"search","deja search","never","error","ready","memory","re","decide","fix","design","debugging","you","done","reviewer","io","change","cli","merge","past",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":35},"01M716A3J2W5SENSE9VGMXB375","deja-reflect","End-of-session reflection and memory curation with deja-vu. Review what was decided, what commands broke and what repaired them, and record durable project rules or decisions with deja remember so the next session starts with them.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fvshulcz\u002Fdeja-vu\u002Fskills\u002Fdeja-reflect\u002FSKILL.md",[],[126,127,128,114,129,130,131,132,133,134,135,136,137,138,105,139,140,141,142,143],"deja reflect","reflect","review","with","record","github","next","https","node","Rules","decisions","brew","remember","project rules","project","session","end","reflection",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":157,"publishedAt":35},"01M715T3RR4BAYSR57HPPTJ0PF","revid","Make, edit, export and post AI videos with Revid (revid.ai) through the Revid MCP server. Use whenever the user wants a short-form or long-form video made (from an idea, a script, a URL, an article, a PDF, a tweet, a product page, their own clips, or a song), wants to find what is going viral on TikTok, YouTube, Instagram or X before making something, wants to edit or re-export an existing Revid project, generate a standalone AI image or clip, make a series episode, or publish and schedule a finished video to connected social accounts. Covers setup (hosted MCP with OAuth, or an API key), the 36 tools, credits, polling and the rules for publishing. Routes to the more specific revid-* skills when one fits.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftmakersas\u002Frevid-skills\u002Fskills\u002Frevid\u002FSKILL.md",[150,153,154],{"categoryNo":151,"categoryName":152,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":155,"categoryName":156,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[146,158,159,160,161,162,163,140,164,106,165,166,167,168,34,169,170,171,172,173],"URL","Video","short-form","standalone","PDF","viral","tiktok","short","social","MCP","song","image","mcp server","schedule","api","publish"]