[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71E39102CMBVS2FZ2EGPMTB":3,"skill-same:01M71E39102CMBVS2FZ2EGPMTB":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":18,"publishedAt":35,"linkOnly":36,"markdownContent":37,"markdownBody":38,"frontMatter":39,"refName":41,"commitSha":42,"skillDirectory":43,"forksCount":44,"repositoryHtmlUrl":45,"repositoryHomepageUrl":6,"ownerHtmlUrl":46,"ownerBlogUrl":47,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M71E39102CMBVS2FZ2EGPMTB","to-tickets",null,"Break a plan or PRD into vertical-slice tickets with dependency order. Triggers: \"break into tickets\", \"vertical slices\".","indigoai-us\u002Fhq-core","indigoai-us","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F122242446?v=4","01M71DTQ5NGD10GT1Z7E6XKWC5","HQ","01M71DTQ6BKSYYBNC9RAKT3YDK",94,"MIT","https:\u002F\u002Fgithub.com\u002Findigoai-us\u002Fhq-core\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fto-tickets\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34],"tickets","to tickets","slice","triggers","gh","Bash","with","order","plan","dependency","break","read","write","edit","grep","prd","2026-11-10 10:12:30",false,"---\nname: to-tickets\ndescription: \"Break a plan or PRD into vertical-slice tickets with dependency order. Triggers: \\\"break into tickets\\\", \\\"vertical slices\\\".\"\nallowed-tools: Read, Write, Edit, Grep, Glob, Bash(gh:*), AskUserQuestion\n---\n\n# To Tickets\n\nBreak a plan, spec, or conversation into a set of **tickets** — tracer-bullet vertical slices, each declaring the tickets that **block** it (the dependency order to execute them in).\n\nThis is distinct from `\u002Fprd`. `\u002Fprd` emits a single `prd.json` PRD artifact (source of truth consumed by `\u002Frun-project` and `\u002Fexecute-task`). `\u002Fto-tickets` emits a set of **dependency-ordered tickets** — each an independently-executable, demoable vertical slice with explicit blocking edges — written as one markdown file per ticket under `workspace\u002F`, or as GitHub issues when the company works on GitHub. Reach for `\u002Fto-tickets` when you already have a plan (from a conversation, a spec, or an existing `prd.json`) and want it sliced into a graph of grab-and-go tickets rather than a formal PRD document.\n\nPattern adapted from [mattpocock\u002Fskills](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills) (skills\u002Fengineering\u002Fto-tickets), upstream commit 391a270; tracker-agnostic (workspace\u002F markdown default), HQ company-context and cross-references added.\n\n## Step 0 — Resolve company context\n\nSame pattern as `\u002Fdiagnose`, `\u002Finvestigate`, and `\u002Fbrainstorm`:\n\n1. Honour explicit `[company]` argument\n2. Fall back to `workspace\u002Fthreads\u002Fhandoff.json` `.company`\n3. Fall back to cwd inference via `companies\u002Fmanifest.yaml`\n4. Last resort: ask via `AskUserQuestion`\n\nLoad the GLOSSARY-style domain glossary if the target repo has one (`\u003Crepo>\u002FGLOSSARY.md`). Check ADRs in the area being touched (`\u003Crepo>\u002Fdocs\u002Fadr\u002F`). Ticket titles and descriptions should use the project's domain glossary vocabulary and respect those ADRs.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation context. If the user passes a reference (a spec path, a `prd.json`, an issue number or URL) as an argument, fetch it and read its full body and comments. If the source is a `prd.json`, treat its user stories as raw material to re-slice into tracer bullets — do not just copy them over one-to-one.\n\n### 2. Explore the codebase (optional)\n\nIf you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\nLook for opportunities to prefactor the code to make the implementation easier. \"Make the change easy, then make the easy change.\"\n\n### 3. Draft vertical slices\n\nBreak the work into **tracer bullet** tickets.\n\n\u003Cvertical-slice-rules>\n\n- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer\n- A completed slice is demoable or verifiable on its own\n- Each slice is sized to fit in a single fresh context window\n- Any prefactoring should be done first\n\n\u003C\u002Fvertical-slice-rules>\n\nGive each ticket its **blocking edges** — the other tickets that must complete before it can start. A ticket with no blockers can start immediately.\n\n**Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change — rename a column, retype a shared symbol — whose **blast radius** fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as **expand–contract**. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket — green is promised only there.\n\n### 4. Quiz the user\n\nPresent the proposed breakdown as a numbered list. For each ticket, show:\n\n- **Title**: short descriptive name\n- **Blocked by**: which other tickets (if any) must complete first\n- **What it delivers**: the end-to-end behaviour this ticket makes work\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Are the blocking edges correct — does each ticket only depend on tickets that genuinely gate it?\n- Should any tickets be merged or split further?\n\nIterate until the user approves the breakdown.\n\n### 5. Publish the tickets\n\nPublish the approved tickets. The tickets are the same either way — only the shape of the blocking edges changes.\n\n- **Default: workspace markdown** → write one file per ticket under `workspace\u002Freports\u002Ftickets-\u003Cslug>\u002F\u003CNN>-\u003Cslug>.md`, numbered from `01` in dependency order (blockers first), where `\u003Cslug>` is the feature slug. Each file's \"Blocked by\" lists the numbers\u002Ftitles it depends on. Use the per-ticket file template below — one ticket per file, never a single combined file.\n- **Optional: GitHub issues** (when the company works on GitHub — check `companies\u002F{co}\u002Fmanifest.yaml` `repos[]`, or the user asks for issues) → publish one issue per ticket via `gh issue create -R \u003Cowner>\u002F\u003Crepo>` in dependency order (blockers first) so each ticket's blocking edges can reference real issue numbers. Use the platform's native blocking \u002F sub-issue relationship where it has one; otherwise set each ticket's \"Blocked by\" to the blocking issue references. Always anchor `gh` to an explicit `-R owner\u002Frepo`.\n\nWork the **frontier**: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.\n\nDo NOT close or modify any parent issue.\n\n\u003Cworkspace-ticket-template>\n\n# \u003CNN> — \u003CTicket title>\n\n**What to build:** the end-to-end behaviour this ticket makes work, from the user's perspective — not a layer-by-layer implementation list.\n\n**Blocked by:** the numbers\u002Ftitles of the tickets that gate this one, or \"None — can start immediately\".\n\n- [ ] Acceptance criterion 1\n- [ ] Acceptance criterion 2\n\n\u003C\u002Fworkspace-ticket-template>\n\n\u003Cissue-template>\n\n## Parent\n\nA reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).\n\n## What to build\n\nThe end-to-end behaviour this ticket makes work, from the user's perspective — not layer-by-layer implementation.\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n\n## Blocked by\n\n- A reference to each blocking ticket, or \"None — can start immediately\".\n\n\u003C\u002Fissue-template>\n\nIn either form, avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.\n\nWork the frontier one ticket at a time with `\u002Fexecute-task` (single story) or `\u002Frun-project` (multi-ticket orchestration), clearing context between tickets.\n\n## Cross-references\n\n- HQ `\u002Fprd` — when you need the formal `prd.json` PRD artifact instead of a dependency-ordered ticket set. `\u002Fto-tickets` can consume a `prd.json` as source and re-slice it into tracer bullets.\n- HQ `\u002Fexecute-task` — execute one approved ticket end-to-end in a fresh context. This is the frontier-clearing companion to `\u002Fto-tickets`.\n- HQ `\u002Frun-project` — orchestrate execution across a multi-ticket set, respecting the blocking edges.\n- HQ `\u002Fwayfinder` — orient on where in a plan\u002Fgraph a piece of work sits before or after slicing.\n- Pattern source: [mattpocock\u002Fskills](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills) (skills\u002Fengineering\u002Fto-tickets), upstream commit 391a270.\n","# To Tickets\n\nBreak a plan, spec, or conversation into a set of **tickets** — tracer-bullet vertical slices, each declaring the tickets that **block** it (the dependency order to execute them in).\n\nThis is distinct from `\u002Fprd`. `\u002Fprd` emits a single `prd.json` PRD artifact (source of truth consumed by `\u002Frun-project` and `\u002Fexecute-task`). `\u002Fto-tickets` emits a set of **dependency-ordered tickets** — each an independently-executable, demoable vertical slice with explicit blocking edges — written as one markdown file per ticket under `workspace\u002F`, or as GitHub issues when the company works on GitHub. Reach for `\u002Fto-tickets` when you already have a plan (from a conversation, a spec, or an existing `prd.json`) and want it sliced into a graph of grab-and-go tickets rather than a formal PRD document.\n\nPattern adapted from [mattpocock\u002Fskills](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills) (skills\u002Fengineering\u002Fto-tickets), upstream commit 391a270; tracker-agnostic (workspace\u002F markdown default), HQ company-context and cross-references added.\n\n## Step 0 — Resolve company context\n\nSame pattern as `\u002Fdiagnose`, `\u002Finvestigate`, and `\u002Fbrainstorm`:\n\n1. Honour explicit `[company]` argument\n2. Fall back to `workspace\u002Fthreads\u002Fhandoff.json` `.company`\n3. Fall back to cwd inference via `companies\u002Fmanifest.yaml`\n4. Last resort: ask via `AskUserQuestion`\n\nLoad the GLOSSARY-style domain glossary if the target repo has one (`\u003Crepo>\u002FGLOSSARY.md`). Check ADRs in the area being touched (`\u003Crepo>\u002Fdocs\u002Fadr\u002F`). Ticket titles and descriptions should use the project's domain glossary vocabulary and respect those ADRs.\n\n## Process\n\n### 1. Gather context\n\nWork from whatever is already in the conversation context. If the user passes a reference (a spec path, a `prd.json`, an issue number or URL) as an argument, fetch it and read its full body and comments. If the source is a `prd.json`, treat its user stories as raw material to re-slice into tracer bullets — do not just copy them over one-to-one.\n\n### 2. Explore the codebase (optional)\n\nIf you have not already explored the codebase, do so to understand the current state of the code. Ticket titles and descriptions should use the project's domain glossary vocabulary, and respect ADRs in the area you're touching.\n\nLook for opportunities to prefactor the code to make the implementation easier. \"Make the change easy, then make the easy change.\"\n\n### 3. Draft vertical slices\n\nBreak the work into **tracer bullet** tickets.\n\n\u003Cvertical-slice-rules>\n\n- Each slice cuts a narrow but COMPLETE path through every layer (schema, API, UI, tests) — vertical, NOT a horizontal slice of one layer\n- A completed slice is demoable or verifiable on its own\n- Each slice is sized to fit in a single fresh context window\n- Any prefactoring should be done first\n\n\u003C\u002Fvertical-slice-rules>\n\nGive each ticket its **blocking edges** — the other tickets that must complete before it can start. A ticket with no blockers can start immediately.\n\n**Wide refactors are the exception to vertical slicing.** A **wide refactor** is one mechanical change — rename a column, retype a shared symbol — whose **blast radius** fans across the whole codebase, so a single edit breaks thousands of call sites at once and no vertical slice can land green. Don't force it into a tracer bullet; sequence it as **expand–contract**. First expand: add the new form beside the old so nothing breaks. Then migrate the call sites over in batches sized by blast radius (per package, per directory), each batch its own ticket blocked by the expand, keeping CI green batch to batch because the old form still exists. Finally contract: delete the old form once no caller remains, in a ticket blocked by every migrate batch. When even the batches can't stay green alone, keep the sequence but let them share an integration branch that all block a final integrate-and-verify ticket — green is promised only there.\n\n### 4. Quiz the user\n\nPresent the proposed breakdown as a numbered list. For each ticket, show:\n\n- **Title**: short descriptive name\n- **Blocked by**: which other tickets (if any) must complete first\n- **What it delivers**: the end-to-end behaviour this ticket makes work\n\nAsk the user:\n\n- Does the granularity feel right? (too coarse \u002F too fine)\n- Are the blocking edges correct — does each ticket only depend on tickets that genuinely gate it?\n- Should any tickets be merged or split further?\n\nIterate until the user approves the breakdown.\n\n### 5. Publish the tickets\n\nPublish the approved tickets. The tickets are the same either way — only the shape of the blocking edges changes.\n\n- **Default: workspace markdown** → write one file per ticket under `workspace\u002Freports\u002Ftickets-\u003Cslug>\u002F\u003CNN>-\u003Cslug>.md`, numbered from `01` in dependency order (blockers first), where `\u003Cslug>` is the feature slug. Each file's \"Blocked by\" lists the numbers\u002Ftitles it depends on. Use the per-ticket file template below — one ticket per file, never a single combined file.\n- **Optional: GitHub issues** (when the company works on GitHub — check `companies\u002F{co}\u002Fmanifest.yaml` `repos[]`, or the user asks for issues) → publish one issue per ticket via `gh issue create -R \u003Cowner>\u002F\u003Crepo>` in dependency order (blockers first) so each ticket's blocking edges can reference real issue numbers. Use the platform's native blocking \u002F sub-issue relationship where it has one; otherwise set each ticket's \"Blocked by\" to the blocking issue references. Always anchor `gh` to an explicit `-R owner\u002Frepo`.\n\nWork the **frontier**: any ticket whose blockers are all done. For a purely linear chain that means top to bottom.\n\nDo NOT close or modify any parent issue.\n\n\u003Cworkspace-ticket-template>\n\n# \u003CNN> — \u003CTicket title>\n\n**What to build:** the end-to-end behaviour this ticket makes work, from the user's perspective — not a layer-by-layer implementation list.\n\n**Blocked by:** the numbers\u002Ftitles of the tickets that gate this one, or \"None — can start immediately\".\n\n- [ ] Acceptance criterion 1\n- [ ] Acceptance criterion 2\n\n\u003C\u002Fworkspace-ticket-template>\n\n\u003Cissue-template>\n\n## Parent\n\nA reference to the parent issue on the tracker (if the source was an existing issue, otherwise omit this section).\n\n## What to build\n\nThe end-to-end behaviour this ticket makes work, from the user's perspective — not layer-by-layer implementation.\n\n## Acceptance criteria\n\n- [ ] Criterion 1\n- [ ] Criterion 2\n\n## Blocked by\n\n- A reference to each blocking ticket, or \"None — can start immediately\".\n\n\u003C\u002Fissue-template>\n\nIn either form, avoid specific file paths or code snippets — they go stale fast. Exception: if a prototype produced a snippet that encodes a decision more precisely than prose can (state machine, reducer, schema, type shape), inline it and note briefly that it came from a prototype. Trim to the decision-rich parts — not a working demo, just the important bits.\n\nWork the frontier one ticket at a time with `\u002Fexecute-task` (single story) or `\u002Frun-project` (multi-ticket orchestration), clearing context between tickets.\n\n## Cross-references\n\n- HQ `\u002Fprd` — when you need the formal `prd.json` PRD artifact instead of a dependency-ordered ticket set. `\u002Fto-tickets` can consume a `prd.json` as source and re-slice it into tracer bullets.\n- HQ `\u002Fexecute-task` — execute one approved ticket end-to-end in a fresh context. This is the frontier-clearing companion to `\u002Fto-tickets`.\n- HQ `\u002Frun-project` — orchestrate execution across a multi-ticket set, respecting the blocking edges.\n- HQ `\u002Fwayfinder` — orient on where in a plan\u002Fgraph a piece of work sits before or after slicing.\n- Pattern source: [mattpocock\u002Fskills](https:\u002F\u002Fgithub.com\u002Fmattpocock\u002Fskills) (skills\u002Fengineering\u002Fto-tickets), upstream commit 391a270.\n",{"name":5,"description":7,"allowed-tools":40},"Read, Write, Edit, Grep, Glob, Bash(gh:*), AskUserQuestion","main","205cf61728a27ef15e9153aa38df5856fc8d82f5",".claude\u002Fskills\u002Fto-tickets",18,"https:\u002F\u002Fgithub.com\u002Findigoai-us\u002Fhq-core","https:\u002F\u002Fgithub.com\u002Findigoai-us","https:\u002F\u002Fhqforwork.com\u002F","The AI Context Layer for Teams","2026-11-09 23:36:37",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add indigoai-us\u002Fhq-core --skill to-tickets",{"tool":56,"command":57},"bunx","bunx skills add indigoai-us\u002Fhq-core --skill to-tickets",{"tool":59,"command":60},"pnpm","pnpm dlx skills add indigoai-us\u002Fhq-core --skill to-tickets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Findigoai-us\u002Fhq-core\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fto-tickets\u002FSKILL.md",true,[64],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"agents\u002Fopenai.yaml","REFERENCE","参考文档",128,"https:\u002F\u002Fgithub.com\u002Findigoai-us\u002Fhq-core\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fto-tickets\u002Fagents\u002Fopenai.yaml",[71,89,119,143,154,164],{"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":35},"01M71E4MQ04WPK1EVDS7VKJ3E8","social-graphic","Generate 1080x1080 HTML social graphics for HQ update posts.","https:\u002F\u002Fgithub.com\u002Findigoai-us\u002Fhq-core\u002Fblob\u002Fmain\u002Fcore\u002Fworkers\u002Fpublic\u002Fsocial-strategist\u002Fskills\u002Fsocial-graphic\u002FSKILL.md",[],[78,79,24,80,32,31,30,81,82,83,84,85,86,87,88],"social","social graphic","html","update","generate","graphics","browser","open","agent-browser","for","posts",{"skillNo":90,"name":86,"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":102,"publishedAt":35},"01M71E4H33K4P5H5M7ENPTMFSC","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction.","https:\u002F\u002Fgithub.com\u002Findigoai-us\u002Fhq-core\u002Fblob\u002Fmain\u002Fcore\u002Fworkers\u002Fpublic\u002Fqa-tester\u002Fskills\u002Fagent-browser\u002FSKILL.md",[94,99],{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000008","测试与质量","SCENARIO","使用场景",{"categoryNo":100,"categoryName":101,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000023","Skill与智能体开发",[103,84,104,105,106,107,24,108,109,110,111,112,85,113,86,114,115,116,117,118],"agent browser","click","ai agents","app","scrape","when","apps","actions","extracting","take a screenshot","testing","programmatic","browser automation","website","cli","interaction",{"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},"01M71E4FDBD7J8Y45JJ9KMMYGN","work-mesh","Work Mesh Live — automatic presence via hq mesh daemon; context reconcile\u002Forganize; manual session task-status, blocked, and note only.","https:\u002F\u002Fgithub.com\u002Findigoai-us\u002Fhq-core\u002Fblob\u002Fmain\u002Fcore\u002Fskills\u002Fwork-mesh\u002FSKILL.md",[],[126,127,128,24,129,130,131,132,133,134,135,136,137,138,30,139,140,141,142],"work mesh","work","mesh","status","context","note","live","presence","automatic","reconcile","only","organize","task","session","manual","daemon","via",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":149,"publishedAt":35},"01M71E4EGHNAAGWAPV6KGBMQ9W","review","Parity worker review skill (materialization fixture).","https:\u002F\u002Fgithub.com\u002Findigoai-us\u002Fhq-core\u002Fblob\u002Fmain\u002Fcore\u002Fscripts\u002Ftests\u002Ffixtures\u002Fagent-session\u002Fworker-materialization\u002Fparity-worker\u002Fskills\u002Freview\u002FSKILL.md",[],[145,150,151,152,153],"review skill","fixture","parity","worker",{"skillNo":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"publishedAt":35},"01M71E4D1FZDJPDC15DRERKX8Y","run","Run or list HQ workers (parity fixture).","https:\u002F\u002Fgithub.com\u002Findigoai-us\u002Fhq-core\u002Fblob\u002Fmain\u002Fcore\u002Fscripts\u002Ftests\u002Ffixtures\u002Fagent-session\u002Fskills\u002Frun\u002FSKILL.md",[],[156,161,162,152,163,151],"parity fixture","workers","list",{"skillNo":165,"name":166,"nameZh":6,"description":167,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":168,"categories":169,"keywords":170,"publishedAt":35},"01M71E4BF4MV5SEWZJZ4T1QPQW","handoff","Preserve session state for a follow-up agent (parity fixture).","https:\u002F\u002Fgithub.com\u002Findigoai-us\u002Fhq-core\u002Fblob\u002Fmain\u002Fcore\u002Fscripts\u002Ftests\u002Ffixtures\u002Fagent-session\u002Fskills\u002Fhandoff\u002FSKILL.md",[],[166,161,171,172,139,173,87,152,174,175,151],"up","preserve","session state","follow-up","state"]