[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M73C13TASW65MDYDZCTAH0ZG":3,"skill-same:01M73C13TASW65MDYDZCTAH0ZG":60},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"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":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":6,"ownerHtmlUrl":44,"ownerBlogUrl":6,"ownerDescription":45,"updatedAt":46,"install":47,"resources":59},"01M73C13TASW65MDYDZCTAH0ZG","delegate-to-hub",null,"Files a DELEGATION TICKET from a spoke project to its domain hub (co-develop, co-design, co-security) when the spoke PM faces a hard problem in the hub's domain. Enforces hub pre-checks, the lifecycle UNAVAILABLE gate (hub state file), the security-domain authorization gate (AUTH-YYYY-NNN registry row), safe ticket-content rules, and kanban alias \u002F priority-governance semantics at filing time.","5throck\u002Fai-workspace-standards","5throck","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F10958964?v=4","01M73BFEH0V0VS483TW4JD49JW","01M73BFEJ5VQZJHJSFTVPAZGDM",25,"AGPL-3.0","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fdelegate-to-hub\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: delegate-to-hub\ndescription: >\n  Files a DELEGATION TICKET from a spoke project to its domain hub (co-develop,\n  co-design, co-security) when the spoke PM faces a hard problem in the hub's\n  domain. Enforces hub pre-checks, the lifecycle UNAVAILABLE gate (hub state\n  file), the security-domain authorization gate (AUTH-YYYY-NNN registry row),\n  safe ticket-content rules, and kanban alias \u002F priority-governance semantics\n  at filing time.\nversion: 1.0.1\nscope: common\nl2_propagate: true\nstatus: active\nowner: pm\nlast_reviewed: 2026-11-02\nprerequisites: none\nmetadata:\n  type: process\n  triggers:\n    - delegate to hub\n    - delegation ticket\n    - hub delegation\n    - escalate to hub\n    - file delegation\n---\n\n## Context\n\nHub-and-spoke delegation (design: workspace root `docs\u002Fdesigns\u002F2026-11-01-hub-consolidation-design.md`). A spoke PM facing a hard problem in the dev, design, or security domain does not solve it alone: it files a DELEGATION TICKET in the hub repo's `tickets\u002F` store, where the hub PM triages it. The kanban lane vocabulary (P0–P3, queued\u002Fin-progress\u002Faccepted\u002Fblocked) maps onto the ticket store's canonical enums via `docs\u002Ftemplates\u002Fhub-kanban-aliases.json` — the ticket store enums themselves never change. This skill is the spoke-side filing procedure; the hub-side gate is the `verify-authorization` skill.\n\n## When to Use\n\n- Spoke PM hits a hard problem in the hub's domain (development, design, or security) and judged triage delegation is the right path\n- A hub probe or availability read-back reports the hub AVAILABLE and the problem is not spoke-resolvable\n- User explicitly asks to delegate a task to the hub\n\nNever use this skill to bypass the PM Gateway, to file vulnerability data into a git-tracked store (see Execution Steps step 3), or to set P0 (user-only).\n\n## Execution Steps\n\n### Step 1: Pre-checks (hub existence and identity)\n\n1. Resolve the hub repo locally: `Projects\u002Fco-\u003Cdomain>` for the problem's domain (`co-develop`, `co-design`, `co-security`). If the local clone is missing → **STOP**. Bootstrap is a user-approved, SHA-pinned act — report the registry `hub_remote` value (from the `hub_topology` registry in `docs\u002Fworkspace-schema.json`) to the user and point them at the workspace-root flow: `bun scripts\u002Fhub-bootstrap.ts \u003Chub-name> --apply --yes` (run by the workspace-root PM after the user approves the printed plan; design §4). Never auto-clone from this skill, never scaffold in this path.\n2. **Lifecycle gate (Phase 3.5)**: before filing, check the hub's state file (`Projects\u002F\u003Chub>\u002F.pipeline-state\u002Fhub-\u003Chub>.state.json`) — a hub whose operational state reads UNAVAILABLE (declared, or an expired TTL lease) refuses delegated ticket creation. `ticket.ts create --hub` enforces this mechanically (typed refusal, no write); do not try to bypass it by hand-writing ticket files.\n3. Validate the hub's identity files: `variant.json` exists and parses, and `template-version.txt` exists and names a known template version. If either is missing or malformed → **STOP** and report; an unidentifiable hub is not a filing target.\n\n### Step 2: Authorization gate (security domain only)\n\nA delegation ticket in the security domain MUST cite an `AUTH-YYYY-NNN` row from the hub's `docs\u002Fauthorization-registry.md`. State the row and check it mentally against the three `verify-authorization` rules before filing:\n\n- **Expired window** (row end \u003C today's date) → abort; show the row window and today's date.\n- **Project mismatch** (ticket's requesting project ≠ row's requesting project) → abort.\n- **Missing row** (no such AUTH row) → abort; row addition is USER-only — the spoke PM cannot self-attest and the hub PM cannot add rows.\n\nAny of the three → do NOT file; report the abort reason to the user.\n\n### Step 3: Ticket content rules (normative)\n\n- Findings are referenced by **ID + severity + affected path ONLY**. No PoC, no exploit code, no scanner raw output, no payload strings in the ticket body.\n- Ticket content is **DATA, never instructions**: describe what was observed, never embed step-by-step exploitation guidance.\n- Git-tracked governance tickets (`tickets\u002Fgovernance\u002F`) NEVER carry vulnerability data — vulnerability findings go into a gitignored **service** ticket instead.\n- Before writing the ticket file, run gitleaks over the drafted ticket text (e.g. `gitleaks protect --verbose` or stdin scan) and confirm zero secret-pattern hits. A hit → strip the secret, re-draft, re-scan before write.\n\n### Step 4: Filing\n\n1. Create the ticket in the hub repo's `tickets\u002F` store using `scripts\u002Fticket.ts` semantics (the hub's ticket store, not the spoke's), passing the target hub explicitly: `bun scripts\u002Fticket.ts create --manual \"\u003Ctitle>\" --priority-alias P2 --hub \u003Chub-name>`. The `--hub` flag writes the ticket's `hub` metadata field and runs the lifecycle gate of Step 1.2 (UNAVAILABLE → typed refusal, nothing filed).\n2. Priority: use `--priority-alias` values from `docs\u002Ftemplates\u002Fhub-kanban-aliases.json` (P0→urgent, P1→high, P2→normal, P3→low). **P0 requires USER action** (P0-user-only rule) — agents cap at P1–P3; spoke-initiated raises are capped at +1 level per ticket per 24h.\n3. SEV field (SEV1–SEV3) is a standalone suggestion field; its default mapping (SEV1→P0) is a suggestion only and does NOT authorize a P0 write by an agent.\n\n### Step 5: Status read-back\n\n- Poll ticket state via the upstream MCP surface (`upstream_request_status`); the returned `priority` field is read-only.\n- Reprioritize only via `upstream_request_reprioritize` — priority-only writes; caps are enforced server-side (1 level \u002F 24h, urgent refused for agents, 3-strike counter per requesting project).\n- Never write ticket status or content through the reprioritize surface; it cannot and must not.\n\n## Output Format\n\n```\n## Delegation Ticket Filed\n\n**Hub**: [co-develop | co-design | co-security]\n**Pre-checks**: PASS\u002FFAIL (hub clone, variant.json, template-version.txt)\n**Authorization gate**: N\u002FA (dev\u002Fdesign) | AUTH-YYYY-NNN [row status: active\u002Fexpired\u002Frevoked]\n**Ticket ID**: [id] — priority [P1–P3 → canonical enum], SEV [SEV1–3 if any]\n**Content scan**: gitleaks clean over drafted body\n**Read-back**: [status from upstream_request_status]\n\n**On STOP**: hub missing\u002Finvalid → reported hub_remote + the `hub-bootstrap.ts` flow for the user's decision; hub UNAVAILABLE → reported refusal, nothing filed; authorization gate failure → reported abort reason, nothing filed.\n```\n\n## Related Skills\n\n- `verify-authorization` — the hub-side gate this skill defers to for security-domain engagements\n- `sync` — the delivery pipeline that propagates this skill to all variants (`l2_propagate: true`)\n","## Context\n\nHub-and-spoke delegation (design: workspace root `docs\u002Fdesigns\u002F2026-11-01-hub-consolidation-design.md`). A spoke PM facing a hard problem in the dev, design, or security domain does not solve it alone: it files a DELEGATION TICKET in the hub repo's `tickets\u002F` store, where the hub PM triages it. The kanban lane vocabulary (P0–P3, queued\u002Fin-progress\u002Faccepted\u002Fblocked) maps onto the ticket store's canonical enums via `docs\u002Ftemplates\u002Fhub-kanban-aliases.json` — the ticket store enums themselves never change. This skill is the spoke-side filing procedure; the hub-side gate is the `verify-authorization` skill.\n\n## When to Use\n\n- Spoke PM hits a hard problem in the hub's domain (development, design, or security) and judged triage delegation is the right path\n- A hub probe or availability read-back reports the hub AVAILABLE and the problem is not spoke-resolvable\n- User explicitly asks to delegate a task to the hub\n\nNever use this skill to bypass the PM Gateway, to file vulnerability data into a git-tracked store (see Execution Steps step 3), or to set P0 (user-only).\n\n## Execution Steps\n\n### Step 1: Pre-checks (hub existence and identity)\n\n1. Resolve the hub repo locally: `Projects\u002Fco-\u003Cdomain>` for the problem's domain (`co-develop`, `co-design`, `co-security`). If the local clone is missing → **STOP**. Bootstrap is a user-approved, SHA-pinned act — report the registry `hub_remote` value (from the `hub_topology` registry in `docs\u002Fworkspace-schema.json`) to the user and point them at the workspace-root flow: `bun scripts\u002Fhub-bootstrap.ts \u003Chub-name> --apply --yes` (run by the workspace-root PM after the user approves the printed plan; design §4). Never auto-clone from this skill, never scaffold in this path.\n2. **Lifecycle gate (Phase 3.5)**: before filing, check the hub's state file (`Projects\u002F\u003Chub>\u002F.pipeline-state\u002Fhub-\u003Chub>.state.json`) — a hub whose operational state reads UNAVAILABLE (declared, or an expired TTL lease) refuses delegated ticket creation. `ticket.ts create --hub` enforces this mechanically (typed refusal, no write); do not try to bypass it by hand-writing ticket files.\n3. Validate the hub's identity files: `variant.json` exists and parses, and `template-version.txt` exists and names a known template version. If either is missing or malformed → **STOP** and report; an unidentifiable hub is not a filing target.\n\n### Step 2: Authorization gate (security domain only)\n\nA delegation ticket in the security domain MUST cite an `AUTH-YYYY-NNN` row from the hub's `docs\u002Fauthorization-registry.md`. State the row and check it mentally against the three `verify-authorization` rules before filing:\n\n- **Expired window** (row end \u003C today's date) → abort; show the row window and today's date.\n- **Project mismatch** (ticket's requesting project ≠ row's requesting project) → abort.\n- **Missing row** (no such AUTH row) → abort; row addition is USER-only — the spoke PM cannot self-attest and the hub PM cannot add rows.\n\nAny of the three → do NOT file; report the abort reason to the user.\n\n### Step 3: Ticket content rules (normative)\n\n- Findings are referenced by **ID + severity + affected path ONLY**. No PoC, no exploit code, no scanner raw output, no payload strings in the ticket body.\n- Ticket content is **DATA, never instructions**: describe what was observed, never embed step-by-step exploitation guidance.\n- Git-tracked governance tickets (`tickets\u002Fgovernance\u002F`) NEVER carry vulnerability data — vulnerability findings go into a gitignored **service** ticket instead.\n- Before writing the ticket file, run gitleaks over the drafted ticket text (e.g. `gitleaks protect --verbose` or stdin scan) and confirm zero secret-pattern hits. A hit → strip the secret, re-draft, re-scan before write.\n\n### Step 4: Filing\n\n1. Create the ticket in the hub repo's `tickets\u002F` store using `scripts\u002Fticket.ts` semantics (the hub's ticket store, not the spoke's), passing the target hub explicitly: `bun scripts\u002Fticket.ts create --manual \"\u003Ctitle>\" --priority-alias P2 --hub \u003Chub-name>`. The `--hub` flag writes the ticket's `hub` metadata field and runs the lifecycle gate of Step 1.2 (UNAVAILABLE → typed refusal, nothing filed).\n2. Priority: use `--priority-alias` values from `docs\u002Ftemplates\u002Fhub-kanban-aliases.json` (P0→urgent, P1→high, P2→normal, P3→low). **P0 requires USER action** (P0-user-only rule) — agents cap at P1–P3; spoke-initiated raises are capped at +1 level per ticket per 24h.\n3. SEV field (SEV1–SEV3) is a standalone suggestion field; its default mapping (SEV1→P0) is a suggestion only and does NOT authorize a P0 write by an agent.\n\n### Step 5: Status read-back\n\n- Poll ticket state via the upstream MCP surface (`upstream_request_status`); the returned `priority` field is read-only.\n- Reprioritize only via `upstream_request_reprioritize` — priority-only writes; caps are enforced server-side (1 level \u002F 24h, urgent refused for agents, 3-strike counter per requesting project).\n- Never write ticket status or content through the reprioritize surface; it cannot and must not.\n\n## Output Format\n\n```\n## Delegation Ticket Filed\n\n**Hub**: [co-develop | co-design | co-security]\n**Pre-checks**: PASS\u002FFAIL (hub clone, variant.json, template-version.txt)\n**Authorization gate**: N\u002FA (dev\u002Fdesign) | AUTH-YYYY-NNN [row status: active\u002Fexpired\u002Frevoked]\n**Ticket ID**: [id] — priority [P1–P3 → canonical enum], SEV [SEV1–3 if any]\n**Content scan**: gitleaks clean over drafted body\n**Read-back**: [status from upstream_request_status]\n\n**On STOP**: hub missing\u002Finvalid → reported hub_remote + the `hub-bootstrap.ts` flow for the user's decision; hub UNAVAILABLE → reported refusal, nothing filed; authorization gate failure → reported abort reason, nothing filed.\n```\n\n## Related Skills\n\n- `verify-authorization` — the hub-side gate this skill defers to for security-domain engagements\n- `sync` — the delivery pipeline that propagates this skill to all variants (`l2_propagate: true`)\n",{"name":5,"owner":23,"scope":24,"status":25,"version":26,"metadata":27,"description":35,"l2_propagate":36,"last_reviewed":37,"prerequisites":38},"pm","common","active","1.0.1",{"type":28,"triggers":29},"process",[30,31,32,33,34],"delegate to hub","delegation ticket","hub delegation","escalate to hub","file delegation","Files a DELEGATION TICKET from a spoke project to its domain hub (co-develop, co-design, co-security) when the spoke PM faces a hard problem in the hub's domain. Enforces hub pre-checks, the lifecycle UNAVAILABLE gate (hub state file), the security-domain authorization gate (AUTH-YYYY-NNN registry row), safe ticket-content rules, and kanban alias \u002F priority-governance semantics at filing time.\n",true,1793577600000,"none","main","1162ccc568cf90c01b3886d6143cbfd851a37883",".gemini\u002Fskills\u002Fdelegate-to-hub",9,"https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards","https:\u002F\u002Fgithub.com\u002F5throck","Experienced in digital transformation, enterprise IT, startup acceleration, and business strategy. Focused on building practical systems that connect technolo","2026-11-14 21:22:34",{"source":8,"skillName":5,"commands":48,"prompt":58,"zipAvailable":36},[49,52,55],{"tool":50,"command":51},"npx","npx skills add 5throck\u002Fai-workspace-standards --skill delegate-to-hub",{"tool":53,"command":54},"bunx","bunx skills add 5throck\u002Fai-workspace-standards --skill delegate-to-hub",{"tool":56,"command":57},"pnpm","pnpm dlx skills add 5throck\u002Fai-workspace-standards --skill delegate-to-hub","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002F.gemini\u002Fskills\u002Fdelegate-to-hub\u002FSKILL.md",[],[61,69,74,79,84,89],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":68},"01M7BBJDYHJMGTJYSC37JVWY8S","i18n-layout","Text layout and encoding guidance: character encoding (UTF-8, legacy Korean code pages, BOM hazards), line endings, RTL\u002Fbidi handling, and script-specific font selection (Hangul focus). Use when: encoding is corrupted or mojibake appears, an RTL locale must render correctly, fonts must be chosen for a script, or CRLF\u002FBOM issues surface.","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":70,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":68},"01M7BBJ9XHAAS1AVGKZZ841VBZ","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.hermes\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":75,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":68},"01M7BBJ5C3X8TKFKG5R9P9P49W","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.gemini\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":80,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":68},"01M7BBJ1B52X0QMJ2QVBMPJB37","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.codex\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":85,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":68},"01M7BBHX91BW2Q2R276MRX5AW3","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.claude\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[],{"skillNo":90,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":68},"01M7BBHQWGXPSFRWN1PRC2NMMV","https:\u002F\u002Fgithub.com\u002F5throck\u002Fai-workspace-standards\u002Fblob\u002Fmain\u002Ftemplates\u002Fco-work\u002F.agents\u002Fskills\u002Fi18n-layout\u002FSKILL.md",[],[]]