[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77S3NK6KC59ND1J2JSXFDW3":3,"skill-same:01M77S3NK6KC59ND1J2JSXFDW3":44},{"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":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":43},"01M77S3NK6KC59ND1J2JSXFDW3","slice-issues",null,"Slice GitHub parent issues into reviewable real sub-issues. Use when Codex is asked to split, slice, decompose, refine, or plan a GitHub issue into child issues, sub-issues, implementation slices, or reviewable follow-up issues before implementation work begins.","docs-as-code-toolkit\u002Farchitecture-knowledge-toolkit","docs-as-code-toolkit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F273816461?v=4","01M77S1546130CS9RH10VAW9DT","01M77S1559YEN3JKTVX724CJ8K",4,"MIT","https:\u002F\u002Fgithub.com\u002Fdocs-as-code-toolkit\u002Farchitecture-knowledge-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fslice-issues\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: slice-issues\ndescription: Slice GitHub parent issues into reviewable real sub-issues. Use when Codex is asked to split, slice, decompose, refine, or plan a GitHub issue into child issues, sub-issues, implementation slices, or reviewable follow-up issues before implementation work begins.\n---\n\n# Slice Issues\n\n## Overview\n\nUse this workflow to decompose a GitHub issue into reviewable implementation\nslices before code changes begin. Prefer real GitHub sub-issues over textual\ntask lists so the backlog remains traceable and each slice can have its own\nacceptance criteria, branch, PR, and verification.\n\nThis skill is GitHub-specific but engine-independent. Keep runtime-specific\nintegration details in `adapters\u002F`.\n\n## Required Reading\n\n- `..\u002Freferences\u002Fissue-labels.md` before creating child issues, to set each\n  slice's issue type and labels so the backlog and any project board can filter\n  them.\n\n## Workflow\n\n1. Identify the parent issue number or URL.\n2. Read the parent issue body and comments before slicing.\n3. Check existing open issues to avoid duplicate slices.\n4. Decide whether the work should be split into sub-issues or kept in one PR\n   with clearly separated commits.\n5. For each sliced task, create a child issue with GitHub's sub-issue support,\n   setting its type and labels per `..\u002Freferences\u002Fissue-labels.md`. Use exactly\n   one type representation — a native issue type **or** a `type:` label, never\n   both:\n\n   ```sh\n   # Org repos with native issue types:\n   gh issue create --parent \u003Cparent> --title \"\u003Ctitle>\" --body-file \u003Cfile> \\\n     --type \u003CType> --label \"\u003Carea>,\u003Cgrouping>\"\n\n   # Personal repos (native issue types unavailable) — carry the type as a label:\n   gh issue create --parent \u003Cparent> --title \"\u003Ctitle>\" --body-file \u003Cfile> \\\n     --label \"\u003Ctype-label>,\u003Carea>,\u003Cgrouping>\"\n   ```\n\n   A slice is normally a `user-story` (a reviewable slice of value) or a `task`\n   (technical work with no direct user value). Use `--body-file` instead of\n   `--body` when the body is multi-line or contains Markdown that would be\n   awkward to quote safely.\n6. Comment on the parent issue with the created child issue links and the\n   recommended implementation order.\n7. Report the created child issues and any fallback used.\n\n## Slicing Rules\n\n- Make each child issue independently reviewable and small enough for one\n  focused PR.\n- Give each child issue a clear goal, scope, and acceptance criteria.\n- Give each child issue an explicit type and labels per\n  `..\u002Freferences\u002Fissue-labels.md` — exactly one type representation (a native\n  issue type or a `type:` label) plus `area:` and any project grouping such as a\n  roadmap phase — so it can be triaged onto a project board\n  without re-reading the body. Do not encode workflow status in labels; that\n  belongs to the board.\n- Preserve the parent issue as the coordination point.\n- Prefer dependency order over arbitrary numbering.\n- Keep implementation work out of the slicing step unless the user explicitly\n  asks to continue into implementation.\n- If a slice is only documentation, validation, generator behavior, or example\n  refresh work, make that boundary explicit in the title and acceptance\n  criteria.\n\n## Fallback\n\nUse body links or Markdown task lists only when GitHub sub-issue creation is\nunavailable or rejected by the CLI\u002FAPI.\n\nWhen fallback is used:\n\n- Include the exact command that failed.\n- Include the exact error returned by the CLI\u002FAPI.\n- Add the fallback links or task list to the parent issue.\n- State in the final report that real sub-issues could not be created.\n\n## Relationship To Issue Implementation\n\nAfter slicing is complete, use `..\u002Fimplement-issue-workflow\u002FSKILL.md` for each\nchild issue that needs implementation, branch, commit, push, and pull request\nwork.\n","# Slice Issues\n\n## Overview\n\nUse this workflow to decompose a GitHub issue into reviewable implementation\nslices before code changes begin. Prefer real GitHub sub-issues over textual\ntask lists so the backlog remains traceable and each slice can have its own\nacceptance criteria, branch, PR, and verification.\n\nThis skill is GitHub-specific but engine-independent. Keep runtime-specific\nintegration details in `adapters\u002F`.\n\n## Required Reading\n\n- `..\u002Freferences\u002Fissue-labels.md` before creating child issues, to set each\n  slice's issue type and labels so the backlog and any project board can filter\n  them.\n\n## Workflow\n\n1. Identify the parent issue number or URL.\n2. Read the parent issue body and comments before slicing.\n3. Check existing open issues to avoid duplicate slices.\n4. Decide whether the work should be split into sub-issues or kept in one PR\n   with clearly separated commits.\n5. For each sliced task, create a child issue with GitHub's sub-issue support,\n   setting its type and labels per `..\u002Freferences\u002Fissue-labels.md`. Use exactly\n   one type representation — a native issue type **or** a `type:` label, never\n   both:\n\n   ```sh\n   # Org repos with native issue types:\n   gh issue create --parent \u003Cparent> --title \"\u003Ctitle>\" --body-file \u003Cfile> \\\n     --type \u003CType> --label \"\u003Carea>,\u003Cgrouping>\"\n\n   # Personal repos (native issue types unavailable) — carry the type as a label:\n   gh issue create --parent \u003Cparent> --title \"\u003Ctitle>\" --body-file \u003Cfile> \\\n     --label \"\u003Ctype-label>,\u003Carea>,\u003Cgrouping>\"\n   ```\n\n   A slice is normally a `user-story` (a reviewable slice of value) or a `task`\n   (technical work with no direct user value). Use `--body-file` instead of\n   `--body` when the body is multi-line or contains Markdown that would be\n   awkward to quote safely.\n6. Comment on the parent issue with the created child issue links and the\n   recommended implementation order.\n7. Report the created child issues and any fallback used.\n\n## Slicing Rules\n\n- Make each child issue independently reviewable and small enough for one\n  focused PR.\n- Give each child issue a clear goal, scope, and acceptance criteria.\n- Give each child issue an explicit type and labels per\n  `..\u002Freferences\u002Fissue-labels.md` — exactly one type representation (a native\n  issue type or a `type:` label) plus `area:` and any project grouping such as a\n  roadmap phase — so it can be triaged onto a project board\n  without re-reading the body. Do not encode workflow status in labels; that\n  belongs to the board.\n- Preserve the parent issue as the coordination point.\n- Prefer dependency order over arbitrary numbering.\n- Keep implementation work out of the slicing step unless the user explicitly\n  asks to continue into implementation.\n- If a slice is only documentation, validation, generator behavior, or example\n  refresh work, make that boundary explicit in the title and acceptance\n  criteria.\n\n## Fallback\n\nUse body links or Markdown task lists only when GitHub sub-issue creation is\nunavailable or rejected by the CLI\u002FAPI.\n\nWhen fallback is used:\n\n- Include the exact command that failed.\n- Include the exact error returned by the CLI\u002FAPI.\n- Add the fallback links or task list to the parent issue.\n- State in the final report that real sub-issues could not be created.\n\n## Relationship To Issue Implementation\n\nAfter slicing is complete, use `..\u002Fimplement-issue-workflow\u002FSKILL.md` for each\nchild issue that needs implementation, branch, commit, push, and pull request\nwork.\n",{"name":5,"description":7},"main","209607df178aba11b58f76b19e45d58af0d44f52","skills\u002Fslice-issues",2,"https:\u002F\u002Fgithub.com\u002Fdocs-as-code-toolkit\u002Farchitecture-knowledge-toolkit","https:\u002F\u002Fgithub.com\u002Fdocs-as-code-toolkit","2026-11-10 03:36:06",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":42},[32,35,38],{"tool":33,"command":34},"npx","npx skills add docs-as-code-toolkit\u002Farchitecture-knowledge-toolkit --skill slice-issues",{"tool":36,"command":37},"bunx","bunx skills add docs-as-code-toolkit\u002Farchitecture-knowledge-toolkit --skill slice-issues",{"tool":39,"command":40},"pnpm","pnpm dlx skills add docs-as-code-toolkit\u002Farchitecture-knowledge-toolkit --skill slice-issues","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fdocs-as-code-toolkit\u002Farchitecture-knowledge-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fslice-issues\u002FSKILL.md",true,[],[45,52,59,66,73,80],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M77S3RY6VQPBNM5JA06GWSCF","traceability-review","Review explicit architecture traceability metadata for gaps, inconsistencies, unsupported claims, stale links, dangling references, and metamodel violations. Use when Codex needs to inspect artifact relations, validate ADR-to-risk or quality-scenario coverage, propose relation updates, or produce an evidence-backed traceability review report.","https:\u002F\u002Fgithub.com\u002Fdocs-as-code-toolkit\u002Farchitecture-knowledge-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Ftraceability-review\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M77S3GN6ZDB3WM0ACCWV03EV","risk","Create proposed architecture risk artifacts and analyze their traceability to ADRs, quality scenarios, requirements, components, controls, and evidence. Use when Codex needs to identify, draft, update, prioritize, or review architecture risks, separate risks from issues and decisions, propose mitigations, or produce a risk impact report without deciding acceptance.","https:\u002F\u002Fgithub.com\u002Fdocs-as-code-toolkit\u002Farchitecture-knowledge-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Frisk\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M77S3CH6QB0Y11BV002AS7PY","quality-scenario","Create proposed quality scenarios and analyze their traceability to quality objectives, ADRs, risks, requirements, architecture artifacts, and code evidence. Use when Codex needs to draft or update measurable quality scenarios, inspect existing arc42 Chapter 10 quality requirements, derive scenarios from source evidence without inventing targets, propose metadata relations, or produce a quality scenario impact report.","https:\u002F\u002Fgithub.com\u002Fdocs-as-code-toolkit\u002Farchitecture-knowledge-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fquality-scenario\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M77S394HQDDQKQFPQKP8V0XW","presentation","Create or update docs-as-code presentation material as AsciiDoc reveal.js decks rendered with docs-toolbox. Use when Codex needs to prepare talks, meetup or conference proposals, speaker notes, demo scripts, event-specific artifacts under talks\u002F, or slide decks that must remain repository-native rather than PowerPoint or Google Slides files.","https:\u002F\u002Fgithub.com\u002Fdocs-as-code-toolkit\u002Farchitecture-knowledge-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fpresentation\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M77S34KBA1J2VV3QHK9JFV3N","pr-review","Review GitHub pull requests and proposed branch changes for correctness, regressions, missing tests, documentation-contract violations, traceability gaps, and reviewability. Use when an AI assistant is asked to review a PR, review pull request changes, inspect a PR branch before merge, or produce PR review comments.","https:\u002F\u002Fgithub.com\u002Fdocs-as-code-toolkit\u002Farchitecture-knowledge-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fpr-review\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M77S30N3KDD8EWKXNS9FVJ9C","post-merge-sync","Synchronize a local checkout after a pull request has been integrated: verify a clean worktree, switch to the base branch, fast-forward from the remote, confirm the PR changes are present, and clean up local and remote PR branches when safe. Use when an agent is asked to clean up after an integrated PR or return the repository to the latest base branch.","https:\u002F\u002Fgithub.com\u002Fdocs-as-code-toolkit\u002Farchitecture-knowledge-toolkit\u002Fblob\u002Fmain\u002Fskills\u002Fpost-merge-sync\u002FSKILL.md",[],[]]