[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A4PB7PQEGA73WCN8XCPVCY":3,"skill-same:01M7A4PB7PQEGA73WCN8XCPVCY":75},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":13,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":29,"install":30,"resources":42},"01M7A4PB7PQEGA73WCN8XCPVCY","dispatch-work",null,"Use only when explicitly authorized to run a published ready ticket DAG through moving parallel Take Ticket frontiers and aggregate synthesis. Excludes planning, per-ticket implementation or review, tracker and PR topology changes, and release work.","jhonDoe15\u002Fskills","jhonDoe15","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F62393042?v=4","01M7A4NRG3NB5KYTSSMMGHHAMC","01M7A4NRGQHAAQA7Q7Q3RRVGAS",0,"MIT","https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdispatch-work\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: dispatch-work\ndescription: Use only when explicitly authorized to run a published ready ticket DAG through moving parallel Take Ticket frontiers and aggregate synthesis. Excludes planning, per-ticket implementation or review, tracker and PR topology changes, and release work.\ndisable-model-invocation: true\n---\n\n# Dispatch Work\n\nRun one authorized published ticket DAG through concurrent Take Ticket\nlifecycles. Compute and advance the DAG frontier whenever an authoritative\nticket completion arrives; never impose a fixed stage barrier.\n\n## Required authority and inputs\n\nRequire all of:\n\n- explicit dispatch authorization whose source can be retained;\n- one published ready DAG with a stable source identity, tickets, and direct\n  dependency edges plus any collision metadata;\n- repository and tracker boundaries for each ticket; and\n- canonical `take-ticket` and `take-it-offline` dependencies.\n\nA plan, ready-plan artifact, issue list, or publication request does not grant\ndispatch authority. If authorization is absent or ambiguous, stop before any\nticket lifecycle starts. If the DAG is unpublished, not ready, internally\ninconsistent, cyclic, or lacks a stable identity, stop before execution.\n\nLoad `take-ticket` and `take-it-offline` by their exact canonical Skill names\nbefore dispatch. If either is absent or unavailable, stop before ticket work\nwith the applicable exact message:\n\n- `Missing internal dependency \"take-ticket\"`\n- `Missing internal dependency \"take-it-offline\"`\n\nNever select a test Adapter, copied fallback, direct Implement path, or direct\nCode Review path in production.\n\n## Fingerprint and resume\n\nBefore starting work, retain SHA-256 source-DAG and execution fingerprints.\nCanonicalize object keys before hashing so offline replay is deterministic. The\nsource fingerprint covers the published identity, ticket state, direct\ndependency edges, and collision metadata. The execution fingerprint covers\nimmutable bases, repository and tracker boundaries, resolved canonical\ndependencies, and executor configuration inputs. Retain direct pointers to the\ncurrent inputs, the current digest, and, for resume, the retained input snapshot\nand digest so offline replay can recompute both sides of the decision.\n\nStart fresh when no retained state was supplied. Resume only when retained\nevidence is complete and both retained fingerprints match the current inputs.\nReject stale, partial, corrupt, or mismatched evidence before starting a ticket,\nand retain the mismatch and required recovery.\n\nFor a compatible resume:\n\n- skip only a ticket whose retained result reference resolves to a complete\n  authoritative reviewed-ticket result bound to that exact ticket; when the\n  canonical Take Ticket result lacks ticket identity, require a Dispatch\n  Work-owned binding that retains the ticket-specific invocation, completion,\n  and canonical result reference;\n- restart incomplete lifecycle work unless a retained retry point and owned\n  worktree explicitly support continuation;\n- preserve failed, retryable, and human-decision states; and\n- recalculate the current frontier from verified retained transitions.\n\nAn interrupted `active` state is partial work, not completion. Never infer a\ncompleted phase from a commit, Review brief, or implementation handoff.\n\n## Select executor capacity\n\nResolve the first valid positive executor limit in this order:\n\n1. repository configuration;\n2. project configuration;\n3. user configuration;\n4. bundled default.\n\nRetain every consulted source and value, plus the selected source. Executor\ncapacity is owned by Dispatch Work. It does not change planning semantics,\nticket eligibility, dependency edges, or the published DAG.\n\n## Establish dispatch state\n\nRetain the source DAG identity, explicit authorization source, and initial\nstate of every ticket and direct dependency, including dependency edges\nalready satisfied before this run. A ticket is:\n\n- `blocked` while any direct dependency remains open;\n- `eligible` when it is open, inactive, and every direct dependency is\n  satisfied;\n- `active` only after its Take Ticket lifecycle starts;\n- `completed` only after Take Ticket returns a complete authoritative\n  reviewed-ticket result;\n- `retryable` when retained evidence names a bounded automatic recovery;\n- `human-decision` when progress requires user-owned authority or a decision;\n  or\n- `failed` when its lifecycle terminates unsuccessfully.\n\nOrdinary success, an implementation handoff alone, a passing check, a commit,\nor a Review brief alone is not completion. Never bypass Implement, full Code\nReview, correction when required, or targeted re-review; those stages remain\nowned by Take Ticket.\n\nAn initially failed ticket retains its actionable recovery and ordering\nsequence. An initially completed dependency has every outgoing retained edge\nmarked pre-satisfied; no other edge may be pre-satisfied. In-run completions\nproduce exactly the outgoing open-to-satisfied transitions they authorize.\n\n## Schedule collisions\n\nKeep collision constraints separate from the source DAG. A collision delays a\nstart but never creates or satisfies a dependency edge. At each calculation:\n\n1. compute every DAG-eligible ticket without considering collisions or capacity;\n2. keep active tickets in their owned slots;\n3. select up to the remaining executor capacity, excluding only tickets that\n   conflict with an active or already selected ticket; and\n4. retain each deferred ticket, its exact conflicting tickets or capacity\n   reason, and the source collision record.\n\nCollision is pairwise unless the published metadata names a larger conflict\nset. A chain `A-B-C` does not imply an `A-C` collision. Unrelated eligible\ntickets still start together.\n\n## Own isolated worktrees\n\nBefore a ticket becomes active, allocate one isolated worktree at its immutable\nbase. Retain the ticket, owner, canonical path, base, creation result, and\nlifecycle state. Reject reused ownership, a dirty or mismatched base, and any\npath already owned by another ticket.\n\nGive Take Ticket only that worktree. A ticket cannot read or write another\nticket's worktree. Record a passing isolation check and its evidence before the\nlifecycle starts; creation and lifecycle start must have distinct ordered\nevents. On complete reviewed work, record cleanup and remove the worktree when\nrepository policy permits. On creation, lifecycle, or cleanup failure, retain\nthe worktree or failed allocation record plus diagnostic artifacts and the next\nrecovery action. Cleanup must preserve the evidence needed to explain partial\nwork.\n\n## Run the moving frontier\n\n1. Calculate the current DAG frontier from retained ticket and direct\n   dependency state.\n2. Apply executor capacity and collision constraints. Give the calculation a\n   retained identity with eligible, selected, deferred, and active tickets.\n3. Create and record one owned worktree for each selected ticket, then start one\n   canonical Take Ticket lifecycle in that worktree. Every start references\n   exactly that one prior calculation and selection.\n4. Observe each lifecycle independently. Process a completion as soon as it\n   arrives, without waiting for unrelated active tickets.\n5. Verify that the returned reviewed-ticket result is complete and\n   authoritative. Retain its implementation handoff and Review brief.\n6. Mark only that ticket complete, satisfy only dependency edges that consume\n   that ticket, and record the completion and dependency transitions.\n7. Recalculate the frontier immediately. Start every newly unblocked eligible\n   ticket without waiting for unrelated active tickets.\n8. Continue until every ticket reaches a terminal state or no ticket can\n   advance.\n\nDo not use frontier-wide joins, fixed waves, fixed batches, or completion\nbarriers. Concurrency is limited only by explicit invocation limits and\npublished collision or shared-state constraints. Such a constraint can delay a\nticket's start, but it does not turn the DAG into stages.\n\nWhen a lifecycle fails or returns an incomplete or non-authoritative result,\nclassify it as retryable, failed, or human-decision from retained evidence. Do\nnot satisfy its outgoing dependencies. Continue independent work when its\nworktree, collision set, and remaining graph make that safe. Retain the first\nrecovery or human decision when no ticket can advance.\n\n## Gate PR maintenance\n\nDispatch authorization does not authorize PR mutation. When a ticket needs PR\nmaintenance, require a separate explicit authorization whose scope and source\ncover the requested actions.\n\nWithout that authorization, record the needed action and return it with zero\nattempted PR mutations. With authorization, invoke external `autopilot` only\nfor an exact authorized repository\u002Faction\u002Ftarget tuple; independently\nauthorized values do not combine into additional tuples. Retain each attempt\nand completion with that tuple, outcome, and evidence reference. A missing or\nfailed prerequisite leaves the ticket retryable or human-decision; it never\ngrants mutation authority. Tests observe this branch only through bounded test\nAdapters and sandboxed fixtures.\n\n## Synthesize completed frontiers\n\nSynthesis is aggregate-only. Bind each synthesis to one unique frontier\ncalculation. Consume exactly the completed subset of that calculation's\nselected tickets after their retained completion events, even when another\nselected member is retryable, failed, or awaiting a human decision. Use only\nthose completed tickets' compact implementation handoffs and Review briefs.\nRetain the synthesis sequence after those events.\nDetect concerns that emerge only across those inputs. Each concern retains its\nidentity, cited implementation handoffs and Review briefs, status, and one\ndisposition. Preserve unresolved concerns across later frontier calculations.\nEvery cross-ticket concern cites retained synthesis evidence associated with at\nleast two distinct ticket identities. A later synthesis may cite its own inputs\nand earlier ordered synthesis inputs, but never unsynthesized or future\nevidence. Each implementation handoff and Review brief reference has exactly\none ticket owner; reject aliased references before using them to establish\ncross-ticket evidence.\nRecommend one or more of:\n\n- acceptance;\n- fixes;\n- a ticket split; or\n- a human decision.\n\nFrontier synthesis does not repeat per-ticket Code Review, alter a reviewed\nfinding, or invent missing ticket authority. It may complete after later work\nhas already started; synthesis never becomes a barrier to a newly runnable\nticket unless its output identifies an explicit human decision.\n\nUse canonical Take It Offline only when a context boundary requires a compact\ncontinuation of current dispatch state. The continuation references retained\ndispatch artifacts and does not replace them.\n\n## Retain an inspectable dispatch artifact\n\nRetain enough structured state for deterministic inspection and offline replay:\n\n- source DAG identity and published-ready state;\n- fresh or resume decision, fingerprint inputs and digests, compatibility\n  checks, skipped work, and rejected evidence;\n- explicit authorization and its source;\n- executor candidates, precedence, selected capacity, and source;\n- collision records and every eligible, selected, deferred, and active ticket;\n- worktree ownership, base, path, creation, lifecycle, cleanup, and diagnostic\n  state;\n- every ticket lifecycle state, its selecting frontier calculation, and its\n  canonical Take Ticket invocation;\n- PR maintenance authorization, needed actions, and attempted and completed\n  mutations;\n- completion events and complete authoritative reviewed-ticket identities;\n- dependency transitions tied to the completion that authorized each one;\n- synthesis inputs, including implementation handoffs and Review briefs;\n- aggregate concern evidence, dispositions, unresolved systematic concerns,\n  and acceptance, fix, split, or human-decision recommendations;\n- initial and pre-satisfied ticket and edge state; and\n- final open, active, completed, retryable, human-decision, blocked, and failed\n  ticket state plus the first recovery action when dispatch is incomplete.\n\nKeep event ordering explicit. Preserve artifact references rather than copying\ntheir full contents. Do not include credentials, secrets, unrelated sensitive\ndata, or unbounded model transcripts.\n\n## Boundaries\n\nDispatch Work owns frontier calculation, Take Ticket invocation, event-driven\nadvancement, executor selection, collision scheduling, worktree lifecycle, the\nPR-maintenance authorization gate, aggregate synthesis, and retained dispatch\nstate. It does not own:\n\n- plan creation, planning semantics, or DAG publication;\n- per-ticket implementation, Code Review, correction, or re-review;\n- issue dependency, assignment, or closure changes;\n- branch, pull-request, CI, merge, or release topology outside an explicitly\n  authorized maintenance action;\n- migration or persistence decisions; or\n- a new shared Interface.\n\nDeterministic evaluation Adapters run only through the canonical test Adapter\nand test execution boundaries. They return normalized artifact references,\nobserved successful Skill loads, and observed tool and attempted-mutation\nevidence. Every selected ticket has exactly one fixture-local Take Ticket\ninvocation\u002Fcompletion artifact proving ticket identity and the complete\nimplementation, full-review, required correction, and targeted re-review\nphases with their ranges and artifacts. Owner-local grading executes the\ndeclared artifact checks against those bodies and observations; matching\nresponse prose is not evidence. These fixtures do not define a shared Take\nTicket schema or a production fallback.\n\nStop for a shared-interface, security-sensitive, migration, persistence,\nrelease, or cross-ticket ownership decision. Do not start an unrelated ticket\nor mutate tracker or PR topology as a side effect of dispatch.\n\n## Completion\n\nClaim a completed dispatch only when every published ticket has a complete\nauthoritative reviewed-ticket result, every in-run direct dependency transition\nis backed by such a completion, all completed frontiers have compact synthesis,\nand the retained artifact exposes the final dispatch state. A partial replay is\nstill valid when it faithfully retains pre-satisfied edges and completed, open,\nretryable, human-decision, blocked, or failed ticket states. Its final status\nmust match those categories, and its first recovery action must be the earliest\nretained actionable recovery by sequence. Return that state without claiming\ndispatch completion.\n","# Dispatch Work\n\nRun one authorized published ticket DAG through concurrent Take Ticket\nlifecycles. Compute and advance the DAG frontier whenever an authoritative\nticket completion arrives; never impose a fixed stage barrier.\n\n## Required authority and inputs\n\nRequire all of:\n\n- explicit dispatch authorization whose source can be retained;\n- one published ready DAG with a stable source identity, tickets, and direct\n  dependency edges plus any collision metadata;\n- repository and tracker boundaries for each ticket; and\n- canonical `take-ticket` and `take-it-offline` dependencies.\n\nA plan, ready-plan artifact, issue list, or publication request does not grant\ndispatch authority. If authorization is absent or ambiguous, stop before any\nticket lifecycle starts. If the DAG is unpublished, not ready, internally\ninconsistent, cyclic, or lacks a stable identity, stop before execution.\n\nLoad `take-ticket` and `take-it-offline` by their exact canonical Skill names\nbefore dispatch. If either is absent or unavailable, stop before ticket work\nwith the applicable exact message:\n\n- `Missing internal dependency \"take-ticket\"`\n- `Missing internal dependency \"take-it-offline\"`\n\nNever select a test Adapter, copied fallback, direct Implement path, or direct\nCode Review path in production.\n\n## Fingerprint and resume\n\nBefore starting work, retain SHA-256 source-DAG and execution fingerprints.\nCanonicalize object keys before hashing so offline replay is deterministic. The\nsource fingerprint covers the published identity, ticket state, direct\ndependency edges, and collision metadata. The execution fingerprint covers\nimmutable bases, repository and tracker boundaries, resolved canonical\ndependencies, and executor configuration inputs. Retain direct pointers to the\ncurrent inputs, the current digest, and, for resume, the retained input snapshot\nand digest so offline replay can recompute both sides of the decision.\n\nStart fresh when no retained state was supplied. Resume only when retained\nevidence is complete and both retained fingerprints match the current inputs.\nReject stale, partial, corrupt, or mismatched evidence before starting a ticket,\nand retain the mismatch and required recovery.\n\nFor a compatible resume:\n\n- skip only a ticket whose retained result reference resolves to a complete\n  authoritative reviewed-ticket result bound to that exact ticket; when the\n  canonical Take Ticket result lacks ticket identity, require a Dispatch\n  Work-owned binding that retains the ticket-specific invocation, completion,\n  and canonical result reference;\n- restart incomplete lifecycle work unless a retained retry point and owned\n  worktree explicitly support continuation;\n- preserve failed, retryable, and human-decision states; and\n- recalculate the current frontier from verified retained transitions.\n\nAn interrupted `active` state is partial work, not completion. Never infer a\ncompleted phase from a commit, Review brief, or implementation handoff.\n\n## Select executor capacity\n\nResolve the first valid positive executor limit in this order:\n\n1. repository configuration;\n2. project configuration;\n3. user configuration;\n4. bundled default.\n\nRetain every consulted source and value, plus the selected source. Executor\ncapacity is owned by Dispatch Work. It does not change planning semantics,\nticket eligibility, dependency edges, or the published DAG.\n\n## Establish dispatch state\n\nRetain the source DAG identity, explicit authorization source, and initial\nstate of every ticket and direct dependency, including dependency edges\nalready satisfied before this run. A ticket is:\n\n- `blocked` while any direct dependency remains open;\n- `eligible` when it is open, inactive, and every direct dependency is\n  satisfied;\n- `active` only after its Take Ticket lifecycle starts;\n- `completed` only after Take Ticket returns a complete authoritative\n  reviewed-ticket result;\n- `retryable` when retained evidence names a bounded automatic recovery;\n- `human-decision` when progress requires user-owned authority or a decision;\n  or\n- `failed` when its lifecycle terminates unsuccessfully.\n\nOrdinary success, an implementation handoff alone, a passing check, a commit,\nor a Review brief alone is not completion. Never bypass Implement, full Code\nReview, correction when required, or targeted re-review; those stages remain\nowned by Take Ticket.\n\nAn initially failed ticket retains its actionable recovery and ordering\nsequence. An initially completed dependency has every outgoing retained edge\nmarked pre-satisfied; no other edge may be pre-satisfied. In-run completions\nproduce exactly the outgoing open-to-satisfied transitions they authorize.\n\n## Schedule collisions\n\nKeep collision constraints separate from the source DAG. A collision delays a\nstart but never creates or satisfies a dependency edge. At each calculation:\n\n1. compute every DAG-eligible ticket without considering collisions or capacity;\n2. keep active tickets in their owned slots;\n3. select up to the remaining executor capacity, excluding only tickets that\n   conflict with an active or already selected ticket; and\n4. retain each deferred ticket, its exact conflicting tickets or capacity\n   reason, and the source collision record.\n\nCollision is pairwise unless the published metadata names a larger conflict\nset. A chain `A-B-C` does not imply an `A-C` collision. Unrelated eligible\ntickets still start together.\n\n## Own isolated worktrees\n\nBefore a ticket becomes active, allocate one isolated worktree at its immutable\nbase. Retain the ticket, owner, canonical path, base, creation result, and\nlifecycle state. Reject reused ownership, a dirty or mismatched base, and any\npath already owned by another ticket.\n\nGive Take Ticket only that worktree. A ticket cannot read or write another\nticket's worktree. Record a passing isolation check and its evidence before the\nlifecycle starts; creation and lifecycle start must have distinct ordered\nevents. On complete reviewed work, record cleanup and remove the worktree when\nrepository policy permits. On creation, lifecycle, or cleanup failure, retain\nthe worktree or failed allocation record plus diagnostic artifacts and the next\nrecovery action. Cleanup must preserve the evidence needed to explain partial\nwork.\n\n## Run the moving frontier\n\n1. Calculate the current DAG frontier from retained ticket and direct\n   dependency state.\n2. Apply executor capacity and collision constraints. Give the calculation a\n   retained identity with eligible, selected, deferred, and active tickets.\n3. Create and record one owned worktree for each selected ticket, then start one\n   canonical Take Ticket lifecycle in that worktree. Every start references\n   exactly that one prior calculation and selection.\n4. Observe each lifecycle independently. Process a completion as soon as it\n   arrives, without waiting for unrelated active tickets.\n5. Verify that the returned reviewed-ticket result is complete and\n   authoritative. Retain its implementation handoff and Review brief.\n6. Mark only that ticket complete, satisfy only dependency edges that consume\n   that ticket, and record the completion and dependency transitions.\n7. Recalculate the frontier immediately. Start every newly unblocked eligible\n   ticket without waiting for unrelated active tickets.\n8. Continue until every ticket reaches a terminal state or no ticket can\n   advance.\n\nDo not use frontier-wide joins, fixed waves, fixed batches, or completion\nbarriers. Concurrency is limited only by explicit invocation limits and\npublished collision or shared-state constraints. Such a constraint can delay a\nticket's start, but it does not turn the DAG into stages.\n\nWhen a lifecycle fails or returns an incomplete or non-authoritative result,\nclassify it as retryable, failed, or human-decision from retained evidence. Do\nnot satisfy its outgoing dependencies. Continue independent work when its\nworktree, collision set, and remaining graph make that safe. Retain the first\nrecovery or human decision when no ticket can advance.\n\n## Gate PR maintenance\n\nDispatch authorization does not authorize PR mutation. When a ticket needs PR\nmaintenance, require a separate explicit authorization whose scope and source\ncover the requested actions.\n\nWithout that authorization, record the needed action and return it with zero\nattempted PR mutations. With authorization, invoke external `autopilot` only\nfor an exact authorized repository\u002Faction\u002Ftarget tuple; independently\nauthorized values do not combine into additional tuples. Retain each attempt\nand completion with that tuple, outcome, and evidence reference. A missing or\nfailed prerequisite leaves the ticket retryable or human-decision; it never\ngrants mutation authority. Tests observe this branch only through bounded test\nAdapters and sandboxed fixtures.\n\n## Synthesize completed frontiers\n\nSynthesis is aggregate-only. Bind each synthesis to one unique frontier\ncalculation. Consume exactly the completed subset of that calculation's\nselected tickets after their retained completion events, even when another\nselected member is retryable, failed, or awaiting a human decision. Use only\nthose completed tickets' compact implementation handoffs and Review briefs.\nRetain the synthesis sequence after those events.\nDetect concerns that emerge only across those inputs. Each concern retains its\nidentity, cited implementation handoffs and Review briefs, status, and one\ndisposition. Preserve unresolved concerns across later frontier calculations.\nEvery cross-ticket concern cites retained synthesis evidence associated with at\nleast two distinct ticket identities. A later synthesis may cite its own inputs\nand earlier ordered synthesis inputs, but never unsynthesized or future\nevidence. Each implementation handoff and Review brief reference has exactly\none ticket owner; reject aliased references before using them to establish\ncross-ticket evidence.\nRecommend one or more of:\n\n- acceptance;\n- fixes;\n- a ticket split; or\n- a human decision.\n\nFrontier synthesis does not repeat per-ticket Code Review, alter a reviewed\nfinding, or invent missing ticket authority. It may complete after later work\nhas already started; synthesis never becomes a barrier to a newly runnable\nticket unless its output identifies an explicit human decision.\n\nUse canonical Take It Offline only when a context boundary requires a compact\ncontinuation of current dispatch state. The continuation references retained\ndispatch artifacts and does not replace them.\n\n## Retain an inspectable dispatch artifact\n\nRetain enough structured state for deterministic inspection and offline replay:\n\n- source DAG identity and published-ready state;\n- fresh or resume decision, fingerprint inputs and digests, compatibility\n  checks, skipped work, and rejected evidence;\n- explicit authorization and its source;\n- executor candidates, precedence, selected capacity, and source;\n- collision records and every eligible, selected, deferred, and active ticket;\n- worktree ownership, base, path, creation, lifecycle, cleanup, and diagnostic\n  state;\n- every ticket lifecycle state, its selecting frontier calculation, and its\n  canonical Take Ticket invocation;\n- PR maintenance authorization, needed actions, and attempted and completed\n  mutations;\n- completion events and complete authoritative reviewed-ticket identities;\n- dependency transitions tied to the completion that authorized each one;\n- synthesis inputs, including implementation handoffs and Review briefs;\n- aggregate concern evidence, dispositions, unresolved systematic concerns,\n  and acceptance, fix, split, or human-decision recommendations;\n- initial and pre-satisfied ticket and edge state; and\n- final open, active, completed, retryable, human-decision, blocked, and failed\n  ticket state plus the first recovery action when dispatch is incomplete.\n\nKeep event ordering explicit. Preserve artifact references rather than copying\ntheir full contents. Do not include credentials, secrets, unrelated sensitive\ndata, or unbounded model transcripts.\n\n## Boundaries\n\nDispatch Work owns frontier calculation, Take Ticket invocation, event-driven\nadvancement, executor selection, collision scheduling, worktree lifecycle, the\nPR-maintenance authorization gate, aggregate synthesis, and retained dispatch\nstate. It does not own:\n\n- plan creation, planning semantics, or DAG publication;\n- per-ticket implementation, Code Review, correction, or re-review;\n- issue dependency, assignment, or closure changes;\n- branch, pull-request, CI, merge, or release topology outside an explicitly\n  authorized maintenance action;\n- migration or persistence decisions; or\n- a new shared Interface.\n\nDeterministic evaluation Adapters run only through the canonical test Adapter\nand test execution boundaries. They return normalized artifact references,\nobserved successful Skill loads, and observed tool and attempted-mutation\nevidence. Every selected ticket has exactly one fixture-local Take Ticket\ninvocation\u002Fcompletion artifact proving ticket identity and the complete\nimplementation, full-review, required correction, and targeted re-review\nphases with their ranges and artifacts. Owner-local grading executes the\ndeclared artifact checks against those bodies and observations; matching\nresponse prose is not evidence. These fixtures do not define a shared Take\nTicket schema or a production fallback.\n\nStop for a shared-interface, security-sensitive, migration, persistence,\nrelease, or cross-ticket ownership decision. Do not start an unrelated ticket\nor mutate tracker or PR topology as a side effect of dispatch.\n\n## Completion\n\nClaim a completed dispatch only when every published ticket has a complete\nauthoritative reviewed-ticket result, every in-run direct dependency transition\nis backed by such a completion, all completed frontiers have compact synthesis,\nand the retained artifact exposes the final dispatch state. A partial replay is\nstill valid when it faithfully retains pre-satisfied edges and completed, open,\nretryable, human-decision, blocked, or failed ticket states. Its final status\nmust match those categories, and its first recovery action must be the earliest\nretained actionable recovery by sequence. Return that state without claiming\ndispatch completion.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","00b68ded1da612384ffdf1f27cf8228b9c2d4428","skills\u002Fdispatch-work","https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills","https:\u002F\u002Fgithub.com\u002FjhonDoe15","2026-10-16 01:12:43",{"source":8,"skillName":5,"commands":31,"prompt":41,"zipAvailable":23},[32,35,38],{"tool":33,"command":34},"npx","npx skills add jhonDoe15\u002Fskills --skill dispatch-work",{"tool":36,"command":37},"bunx","bunx skills add jhonDoe15\u002Fskills --skill dispatch-work",{"tool":39,"command":40},"pnpm","pnpm dlx skills add jhonDoe15\u002Fskills --skill dispatch-work","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdispatch-work\u002FSKILL.md",[43,49,53,59,63,67,71],{"path":44,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":47,"sourceHtmlUrl":48},"evals\u002Fcomponent-take-it-offline.json","REFERENCE","参考文档",2383,"https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdispatch-work\u002Fevals\u002Fcomponent-take-it-offline.json",{"path":50,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":51,"sourceHtmlUrl":52},"evals\u002Fcomponent-take-ticket.json",2496,"https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdispatch-work\u002Fevals\u002Fcomponent-take-ticket.json",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"evals\u002Fgrader.js","SCRIPT","脚本",66734,"https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdispatch-work\u002Fevals\u002Fgrader.js",{"path":60,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":61,"sourceHtmlUrl":62},"evals\u002Foutcome.json",5331,"https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdispatch-work\u002Fevals\u002Foutcome.json",{"path":64,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":65,"sourceHtmlUrl":66},"evals\u002Fpackage-closure.json",944,"https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdispatch-work\u002Fevals\u002Fpackage-closure.json",{"path":68,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":69,"sourceHtmlUrl":70},"evals\u002Frole.json",4619,"https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdispatch-work\u002Fevals\u002Frole.json",{"path":72,"resourceType":45,"resourceTypeDesc":46,"sizeBytes":73,"sourceHtmlUrl":74},"evals\u002Ftrigger.json",2271,"https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdispatch-work\u002Fevals\u002Ftrigger.json",[76,83,90,97,104,111],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":18},"01M7A4R91YWB9YCB90RYMEKP5Y","writing-foundation","Shared writing behavior consumed by to-humans and agent-writing; not a user-facing outcome.","https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fwriting-foundation\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":18},"01M7A4R5WK4J9HGENYK6JZN124","to-humans","Audience outcome for ordinary replies, progress updates, and requested prose whose primary reader is a person. Select it independently for human-facing expression, including alongside one substantive Primary outcome. Excludes agent-facing artifacts, fresh-context handoffs, Agent Skill packages, and non-prose work products.","https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fto-humans\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":18},"01M7A4R3DVDG3FN21JN4VAXXRF","ticket-scope","Private per-candidate scope judgment consumed by Slice Plan and PR Carver; not a user-facing planning outcome.","https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fticket-scope\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M7A4QZNMGMB448HXQQ052EYH","take-ticket","Use when a settled ticket must reach a reviewed-ticket result. Used directly or by Dispatch Work. Excludes implementation-only work, review-only work, ticket topology, publication, release, and multi-ticket dispatch.","https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftake-ticket\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":18},"01M7A4QX88C6QAFMWT7VWTYJXS","take-it-offline","Use when carrying current work into a fresh agent context through a continuation handoff. Excludes human summaries, archival specifications, general agent-facing artifacts, and Agent Skill authoring.","https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftake-it-offline\u002FSKILL.md",[],[],{"skillNo":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":18},"01M7A4QVFT7BVQW0KA651KK6BF","slice-plan","Private set-level decomposition consumed by Carve; not a user-facing planning outcome.","https:\u002F\u002Fgithub.com\u002FjhonDoe15\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fslice-plan\u002FSKILL.md",[],[]]