[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MN4JSSF0GTZAX3Q03PDS9F":3,"skill-same:01M6MN4JSSF0GTZAX3Q03PDS9F":87},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":64},"01M6MN4JSSF0GTZAX3Q03PDS9F","setup-matt-pocock-skills",null,"Sets up an `## Agent skills` block in AGENTS.md\u002FCLAUDE.md and `docs\u002Fagents\u002F` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.","arkhe-genesis\u002FArkhe-OS","arkhe-genesis","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272629719?v=4","01M6KJDTSTJD2AD5RFPVZNGYCP","Rafael Oliveira","01M6KJDTXSTA997KDK184EA55A",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"setup matt pocock skills","setup","matt pocock","labels","github","true","zoom","missing","layout","local","domain","up","use","repo","improve","markdown","first","issues","diagnose","architecture","2026-11-10 10:12:30",false,"---\nname: setup-matt-pocock-skills\ndescription: Sets up an `## Agent skills` block in AGENTS.md\u002FCLAUDE.md and `docs\u002Fagents\u002F` so the engineering skills know this repo's issue tracker (GitHub or local markdown), triage label vocabulary, and domain doc layout. Run before first use of `to-issues`, `to-prd`, `triage`, `diagnose`, `tdd`, `improve-codebase-architecture`, or `zoom-out` — or if those skills appear to be missing context about the issue tracker, triage labels, or domain docs.\ndisable-model-invocation: true\n---\n\n# Setup Matt Pocock's Skills\n\nScaffold the per-repo configuration that the engineering skills assume:\n\n- **Issue tracker** — where issues live (GitHub by default; local markdown is also supported out of the box)\n- **Triage labels** — the strings used for the five canonical triage roles\n- **Domain docs** — where `CONTEXT.md` and ADRs live, and the consumer rules for reading them\n\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.\n\n## Process\n\n### 1. Explore\n\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig` — is this a GitHub repo? Which one?\n- `AGENTS.md` and `CLAUDE.md` at the repo root — does either exist? Is there already an `## Agent skills` section in either?\n- `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` directories\n- `docs\u002Fagents\u002F` — does this skill's prior output already exist?\n- `.scratch\u002F` — sign that a local-markdown issue tracker convention is already in use\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then walk the user through the three decisions **one at a time** — present a section, get the user's answer, then move to the next. Don't dump all three at once.\n\nAssume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why these skills need it, what changes if they pick differently). Then show the choices and the default.\n\n**Section A — Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-issues`, `triage`, `to-prd`, and `qa` read from and write to it — they need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow some other workflow you describe. Pick the place you actually track work for this repo.\n\nDefault posture: these skills were designed for GitHub. If a `git remote` points at GitHub, propose that. If a `git remote` points at GitLab (`gitlab.com` or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:\n\n- **GitHub** — issues live in the repo's GitHub Issues (uses the `gh` CLI)\n- **GitLab** — issues live in the repo's GitLab Issues (uses the [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown** — issues live as files under `.scratch\u002F\u003Cfeature>\u002F` in this repo (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.) — ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose\n\n**Section B — Triage label vocabulary.**\n\n> Explainer: When the `triage` skill processes an incoming issue, it moves it through a state machine — needs evaluation, waiting on reporter, ready for an AFK agent to pick up, ready for a human, or won't fix. To do that, it needs to apply labels (or the equivalent in your issue tracker) that match strings *you've actually configured*. If your repo already uses different label names (e.g. `bug:triage` instead of `needs-triage`), map them here so the skill applies the right ones instead of creating duplicates.\n\nThe five canonical roles:\n\n- `needs-triage` — maintainer needs to evaluate\n- `needs-info` — waiting on reporter\n- `ready-for-agent` — fully specified, AFK-ready (an agent can pick it up with no human context)\n- `ready-for-human` — needs human implementation\n- `wontfix` — will not be actioned\n\nDefault: each role's string equals its name. Ask the user if they want to override any. If their issue tracker has no existing labels, the defaults are fine.\n\n**Section C — Domain docs.**\n\n> Explainer: Some skills (`improve-codebase-architecture`, `diagnose`, `tdd`) read a `CONTEXT.md` file to learn the project's domain language, and `docs\u002Fadr\u002F` for past architectural decisions. They need to know whether the repo has one global context or multiple (e.g. a monorepo with separate frontend\u002Fbackend contexts) so they look in the right place.\n\nConfirm the layout:\n\n- **Single-context** — one `CONTEXT.md` + `docs\u002Fadr\u002F` at the repo root. Most repos are this.\n- **Multi-context** — `CONTEXT-MAP.md` at the root pointing to per-context `CONTEXT.md` files (typically a monorepo).\n\n### 3. Confirm and edit\n\nShow the user a draft of:\n\n- The `## Agent skills` block to add to whichever of `CLAUDE.md` \u002F `AGENTS.md` is being edited (see step 4 for selection rules)\n- The contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Ftriage-labels.md`, `docs\u002Fagents\u002Fdomain.md`\n\nLet them edit before writing.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `CLAUDE.md` exists, edit it.\n- Else if `AGENTS.md` exists, edit it.\n- If neither exists, ask the user which one to create — don't pick for them.\n\nNever create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa) — always edit the one that's already there.\n\nIf an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout — \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n```\n\nThen write the three docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md) — GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md) — GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md) — local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md) — label mapping\n- [domain.md](.\u002Fdomain.md) — domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nTell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later — re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.\n","# Setup Matt Pocock's Skills\n\nScaffold the per-repo configuration that the engineering skills assume:\n\n- **Issue tracker** — where issues live (GitHub by default; local markdown is also supported out of the box)\n- **Triage labels** — the strings used for the five canonical triage roles\n- **Domain docs** — where `CONTEXT.md` and ADRs live, and the consumer rules for reading them\n\nThis is a prompt-driven skill, not a deterministic script. Explore, present what you found, confirm with the user, then write.\n\n## Process\n\n### 1. Explore\n\nLook at the current repo to understand its starting state. Read whatever exists; don't assume:\n\n- `git remote -v` and `.git\u002Fconfig` — is this a GitHub repo? Which one?\n- `AGENTS.md` and `CLAUDE.md` at the repo root — does either exist? Is there already an `## Agent skills` section in either?\n- `CONTEXT.md` and `CONTEXT-MAP.md` at the repo root\n- `docs\u002Fadr\u002F` and any `src\u002F*\u002Fdocs\u002Fadr\u002F` directories\n- `docs\u002Fagents\u002F` — does this skill's prior output already exist?\n- `.scratch\u002F` — sign that a local-markdown issue tracker convention is already in use\n\n### 2. Present findings and ask\n\nSummarise what's present and what's missing. Then walk the user through the three decisions **one at a time** — present a section, get the user's answer, then move to the next. Don't dump all three at once.\n\nAssume the user does not know what these terms mean. Each section starts with a short explainer (what it is, why these skills need it, what changes if they pick differently). Then show the choices and the default.\n\n**Section A — Issue tracker.**\n\n> Explainer: The \"issue tracker\" is where issues live for this repo. Skills like `to-issues`, `triage`, `to-prd`, and `qa` read from and write to it — they need to know whether to call `gh issue create`, write a markdown file under `.scratch\u002F`, or follow some other workflow you describe. Pick the place you actually track work for this repo.\n\nDefault posture: these skills were designed for GitHub. If a `git remote` points at GitHub, propose that. If a `git remote` points at GitLab (`gitlab.com` or a self-hosted host), propose GitLab. Otherwise (or if the user prefers), offer:\n\n- **GitHub** — issues live in the repo's GitHub Issues (uses the `gh` CLI)\n- **GitLab** — issues live in the repo's GitLab Issues (uses the [`glab`](https:\u002F\u002Fgitlab.com\u002Fgitlab-org\u002Fcli) CLI)\n- **Local markdown** — issues live as files under `.scratch\u002F\u003Cfeature>\u002F` in this repo (good for solo projects or repos without a remote)\n- **Other** (Jira, Linear, etc.) — ask the user to describe the workflow in one paragraph; the skill will record it as freeform prose\n\n**Section B — Triage label vocabulary.**\n\n> Explainer: When the `triage` skill processes an incoming issue, it moves it through a state machine — needs evaluation, waiting on reporter, ready for an AFK agent to pick up, ready for a human, or won't fix. To do that, it needs to apply labels (or the equivalent in your issue tracker) that match strings *you've actually configured*. If your repo already uses different label names (e.g. `bug:triage` instead of `needs-triage`), map them here so the skill applies the right ones instead of creating duplicates.\n\nThe five canonical roles:\n\n- `needs-triage` — maintainer needs to evaluate\n- `needs-info` — waiting on reporter\n- `ready-for-agent` — fully specified, AFK-ready (an agent can pick it up with no human context)\n- `ready-for-human` — needs human implementation\n- `wontfix` — will not be actioned\n\nDefault: each role's string equals its name. Ask the user if they want to override any. If their issue tracker has no existing labels, the defaults are fine.\n\n**Section C — Domain docs.**\n\n> Explainer: Some skills (`improve-codebase-architecture`, `diagnose`, `tdd`) read a `CONTEXT.md` file to learn the project's domain language, and `docs\u002Fadr\u002F` for past architectural decisions. They need to know whether the repo has one global context or multiple (e.g. a monorepo with separate frontend\u002Fbackend contexts) so they look in the right place.\n\nConfirm the layout:\n\n- **Single-context** — one `CONTEXT.md` + `docs\u002Fadr\u002F` at the repo root. Most repos are this.\n- **Multi-context** — `CONTEXT-MAP.md` at the root pointing to per-context `CONTEXT.md` files (typically a monorepo).\n\n### 3. Confirm and edit\n\nShow the user a draft of:\n\n- The `## Agent skills` block to add to whichever of `CLAUDE.md` \u002F `AGENTS.md` is being edited (see step 4 for selection rules)\n- The contents of `docs\u002Fagents\u002Fissue-tracker.md`, `docs\u002Fagents\u002Ftriage-labels.md`, `docs\u002Fagents\u002Fdomain.md`\n\nLet them edit before writing.\n\n### 4. Write\n\n**Pick the file to edit:**\n\n- If `CLAUDE.md` exists, edit it.\n- Else if `AGENTS.md` exists, edit it.\n- If neither exists, ask the user which one to create — don't pick for them.\n\nNever create `AGENTS.md` when `CLAUDE.md` already exists (or vice versa) — always edit the one that's already there.\n\nIf an `## Agent skills` block already exists in the chosen file, update its contents in-place rather than appending a duplicate. Don't overwrite user edits to the surrounding sections.\n\nThe block:\n\n```markdown\n## Agent skills\n\n### Issue tracker\n\n[one-line summary of where issues are tracked]. See `docs\u002Fagents\u002Fissue-tracker.md`.\n\n### Triage labels\n\n[one-line summary of the label vocabulary]. See `docs\u002Fagents\u002Ftriage-labels.md`.\n\n### Domain docs\n\n[one-line summary of layout — \"single-context\" or \"multi-context\"]. See `docs\u002Fagents\u002Fdomain.md`.\n```\n\nThen write the three docs files using the seed templates in this skill folder as a starting point:\n\n- [issue-tracker-github.md](.\u002Fissue-tracker-github.md) — GitHub issue tracker\n- [issue-tracker-gitlab.md](.\u002Fissue-tracker-gitlab.md) — GitLab issue tracker\n- [issue-tracker-local.md](.\u002Fissue-tracker-local.md) — local-markdown issue tracker\n- [triage-labels.md](.\u002Ftriage-labels.md) — label mapping\n- [domain.md](.\u002Fdomain.md) — domain doc consumer rules + layout\n\nFor \"other\" issue trackers, write `docs\u002Fagents\u002Fissue-tracker.md` from scratch using the user's description.\n\n### 5. Done\n\nTell the user the setup is complete and which engineering skills will now read from these files. Mention they can edit `docs\u002Fagents\u002F*.md` directly later — re-running this skill is only necessary if they want to switch issue trackers or restart from scratch.\n",{"name":5,"description":7,"disable-model-invocation":44},true,"main","74cd3c4137064fdcde71ed9fe5c4bff58921d899","components\u002Fskills\u002Fsetup-matt-pocock-skills",0,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS","https:\u002F\u002Fgithub.com\u002Farkhe-genesis","2026-11-08 09:08:55",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":44},[54,57,60],{"tool":55,"command":56},"npx","npx skills add arkhe-genesis\u002FArkhe-OS --skill setup-matt-pocock-skills",{"tool":58,"command":59},"bunx","bunx skills add arkhe-genesis\u002FArkhe-OS --skill setup-matt-pocock-skills",{"tool":61,"command":62},"pnpm","pnpm dlx skills add arkhe-genesis\u002FArkhe-OS --skill setup-matt-pocock-skills","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fsetup-matt-pocock-skills\u002FSKILL.md",[65,71,75,79,83],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"domain.md","REFERENCE","参考文档",1986,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fdomain.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"issue-tracker-github.md",1065,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-github.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"issue-tracker-gitlab.md",1545,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-gitlab.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"issue-tracker-local.md",838,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Fissue-tracker-local.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"triage-labels.md",1045,"https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Fcomponents\u002Fskills\u002Fsetup-matt-pocock-skills\u002Ftriage-labels.md",[88,110,127,149,173,192],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":39},"01M6MN97RPP1Q9BG489WHW70R8","career-ops","AI job search command center -- evaluate offers, generate CVs, scan portals, track applications","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.ai-integrations\u002Fvscode\u002F.claude\u002Fskills\u002Fcareer-ops\u002FSKILL.md",[],[95,96,97,98,99,100,101,24,102,103,104,105,106,107,108,109],"ops","career","career ops","track","applications","evaluate","mode","command center","cvs","scan","command","offers","Job Search","search","generate",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":39},"01M6MN93GFX8W9J1PCKDKZVD3N","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[117,25,31,118,119,120,121,122,24,123,124,125,126],"zoom out","how","context","code","it","perspective","re","you","with","understand",{"skillNo":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":131,"categories":132,"keywords":138,"publishedAt":39},"01M6MN8Y2ETBC91BGREF4D39JH","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, or build a new skill.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[133],{"categoryNo":134,"categoryName":135,"taxonomyType":136,"taxonomyTypeDesc":137},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[139,140,141,125,142,143,144,145,146,31,147,148],"write","write a skill","progressive disclosure","resources","new agent","structure","new skill","build","user","create",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":156,"publishedAt":39},"01M6MN8RWE2V2PPFVPD0G8FHKF","triage","Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Ftriage\u002FSKILL.md",[155],{"categoryNo":134,"categoryName":135,"taxonomyType":136,"taxonomyTypeDesc":137},[151,157,158,148,159,160,161,162,163,164,165,31,36,166,167,168,169,170,171,172],"bugs","state machine","requests","machine","feature","roles","issue workflow","manage","issue","state","for","feature requests","prepare","triage issues","workflow","review",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":184,"publishedAt":39},"01M6MN8KVDBD28672WMER7HPXM","to-prd","Turn the current conversation context into a PRD and publish it to the project issue tracker. Use when user wants to create a PRD from the current context.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fto-prd\u002FSKILL.md",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":182,"taxonomyTypeDesc":183},"01JBSEEDCAT000000000000031","产品经理","PROFESSION","适用职业",[185,186,31,147,119,187,148,165,188,121,189,190,191],"to prd","prd","publish","issue tracker","project","conversation","tracker",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":39},"01M6MN8E9CGYVWVDDR0NJEFDBB","to-issues","Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.","https:\u002F\u002Fgithub.com\u002Farkhe-genesis\u002FArkhe-OS\u002Fblob\u002Fmain\u002Ftools\u002F.agents\u002Fskills\u002Fto-issues\u002FSKILL.md",[],[36,199,200,189,201,202,188,203,204,191,165,205,31,147,206,207,208,186,148],"to issues","spec","down","break","break down","tickets","implementation","work","convert","plan"]