[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71ES9PYMGT8F7CJ0GRX1FB3":3,"skill-same:01M71ES9PYMGT8F7CJ0GRX1FB3":59},{"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":32,"linkOnly":33,"markdownContent":34,"markdownBody":35,"frontMatter":36,"refName":37,"commitSha":38,"skillDirectory":39,"forksCount":40,"repositoryHtmlUrl":41,"repositoryHomepageUrl":42,"ownerHtmlUrl":43,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":44,"install":45,"resources":58},"01M71ES9PYMGT8F7CJ0GRX1FB3","pmo-delivery",null,"Use for delivery planning, handoff, task source of truth, engineering sequencing, and semantic handoff review.","witchwasin\u002FAxiom-PMO","witchwasin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F212774037?v=4","01M71ERPAKYZ7GWV9FV63G8Y9P","Witchwasin K.","01M71ERPB9RWQHQAQ2GQ2EEH7Q",3,"MIT","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Fskills\u002Fpmo-delivery\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31],"delivery","pmo","pmo delivery","review","handoff","planning","engineering","use","task","semantic","sequencing","for","source","2026-11-10 10:12:30",false,"---\nname: pmo-delivery\ndescription: Use for delivery planning, handoff, task source of truth, engineering sequencing, and semantic handoff review.\n---\n\n# pmo-delivery\n\n## Purpose\nTranslate approved scope\u002Fdesign into executable work items and handoff notes, and review whether the resulting contract is actually sufficient for a developer to start, integrate, and demonstrate.\n\n## Trigger\nUse when creating or reviewing `DELIVERY.md`, sequencing work, assigning owners, checking task-source consistency, or preparing\u002Freviewing a handoff.\n\n## Intents\n\n| Intent | Use when | Read set |\n|---|---|---|\n| `delivery_planning` (default) | Creating or changing work items | `PROJECT.md`, `DELIVERY.md`, design context |\n| `handoff_review` | Preparing for, or checking, the Handoff gate | see below |\n\n## Required Inputs\n`PROJECT.md`, task source of truth, relevant design context, and the context\u002Fartifact contract in `pmo-config\u002Fcontext-map.json` and `pmo-config\u002Fartifact-policy.json`.\n\nFor `handoff_review`, additionally: `HANDOFF.md`, `DESIGN\u002FBUILD-SPEC.md`, `RAID-log.md` and `decision-log.md` if present, and `pmo-config\u002Fhandoff-policy.json`. When `DESIGN\u002FVISUAL-DIRECTION.md`, `DESIGN\u002FDESIGN-SYSTEM.md`, and `DESIGN\u002FDESIGN-SYSTEM.html` all exist, also read `DESIGN\u002FVISUAL-REVIEW.json` and the declared capture paths. Read only these. Do not read release artifacts, and do not read `source\u002F**` beyond the rows already cited in `PROJECT.md` unless a specific finding requires it.\n\n## Allowed Context\nUse the context router handoff set. Do not read release artifacts unless the user asks for release readiness.\n\n## Mode Behavior\nUse `pmo-config\u002Fpolicy.json` for mode, status, review-stage, task-source, strict-trigger, and sentinel values. Use `pmo-config\u002Fartifact-policy.json` to decide whether `DELIVERY.md` is required, conditional, or replaceable by GitHub Issues for the active mode and gate. Use `pmo-config\u002Fhandoff-policy.json` for handoff artifacts, review lenses, blocking points, and owner policy.\n\n## Execution Steps - delivery_planning\n\n1. Confirm task source of truth: file or GitHub.\n2. Create work items with mode, strict trigger, requirement ref, design ref, status, review stage, evidence, and labels.\n3. Check enum values against runtime policy.\n4. Flag missing blockers or client decisions.\n5. Route implementation deviations through `CHANGE-REQUESTS.json`; do not silently edit the execution contract or acceptance criteria to absorb them.\n\n## Execution Steps - handoff_review\n\nThe deterministic validator proves the contract is **complete**. It cannot prove it is **sensible**. This review is the part that reads for sense, and its output is structured so the validator can then check that the reading happened, covered everything, and is still current.\n\n1. Run the gate first: `node cli\u002Faxiom.mjs validate --project \u003Cproject> --mode \u003Cmode> --gate Handoff`. Do not re-report anything it already caught. Structural gaps are its job; this review starts where it stops.\n2. Read the artifacts listed above. Read them together, not one at a time — most real findings are contradictions *between* documents, each of which is defensible alone.\n3. Walk **every** lens in `pmo-config\u002Fhandoff-policy.json` `semantic_review.lenses`. Record each one in the output even when it found nothing; a lens with no entry is an unfinished review, and `HANDOFF-010` will say so.\n4. Record findings in `HANDOFF-REVIEW.json` (see `templates\u002FHANDOFF-REVIEW.json`).\n5. Record **both** freshness digests. The `handoffDigest` tool (`src\u002Ftools\u002Fdigest-tools.ts`) prints them:\n   - `source_snapshot.digest` — the material the requirements came from\n   - `review_inputs.digest` — the governed artifacts you actually read\n\n   A review that records only the first keeps reporting as current after\n   someone rewrites the build sequence or waives a build-spec section.\n6. If the visual-artifact triple exists, treat Visual Proof as separate conditional candidate evidence: confirm the manifest has two committed captures, an input digest, complete rubric, named human reviewer, and direction decision references. Do not judge aesthetics yourself, replace the human declaration, or describe this check as a new approval.\n7. Re-run the gate, then `node cli\u002Faxiom.mjs handoff` for stage verdicts.\n8. When the Claude Design provider track is active, merge only current accepted output into the Final Handoff — the output set whose digest `DESIGN\u002FCLAUDE-DESIGN\u002FREVIEW.json` records. Unaccepted or stale output is not handoff content (`DPROV-005`\u002F`DPROV-006`).\n\n### The twelve lenses\n\n| Lens | The question it asks |\n|---|---|\n| `value_and_scope_slice` | Does the slice deliver the value the target milestone has to show? |\n| `capability_lifecycle` | Is each capability complete across its lifecycle, or only the happy path? A count that can go down but never up cannot be demonstrated twice. |\n| `data_cardinality_and_units` | Do entities, cardinality, quantities, and units support the declared use cases? A \"stock\" entity with no quantity and no unit is a name, not a model. |\n| `state_transitions_and_rollback` | Does every state machine declare guards, terminal states, and how a transition is reversed? |\n| `concurrency_and_idempotency` | Two users at once, a retried request, two callers allocating an id. Is any of that specified? |\n| `dependencies_and_build_order` | Can the declared sequence actually be executed in that order? Work-item numbering is not build order. |\n| `ownership_and_capacity` | Does every stream have a named owner, an integrator, and stated capacity that fits the horizon? |\n| `acceptance_seed_reachability` | Can each acceptance case be reached from the declared seed data? |\n| `automated_manual_test_split` | Is each case classified, and does the classification have a runner or a person behind it? |\n| `privacy_and_data_classification` | Do declared data elements, free text, files, and metadata have classification decisions? Does a privacy commitment in one document contradict a feature in another? |\n| `environment_and_device_constraints` | Does the serving model satisfy the declared device and runtime capabilities? |\n| `demo_startup_reset_and_recovery` | Is there a declared startup, reset, degraded, and recovery path? |\n\n### Rules for findings\n\n- **Every finding cites evidence.** `evidence_refs` names the artifact rows the finding is derived from. A finding with no evidence is an opinion.\n- **Every finding has a suggestion and an owner.** Naming a problem without naming the next action or who takes it is not a review outcome.\n- **Never invent a requirement.** If a capability looks incomplete relative to what the source already asked for, that is a *completeness* finding against the existing requirement — not new scope. If it is genuinely new scope, it is an open question for a human, not a finding.\n- **Separate blocking points.** `before_build` is a different claim from `before_demo`. Getting this wrong is the most damaging thing this review can do: mislabelling a demo blocker as a build blocker stalls a team that could be working, and the reverse produces a demo-day surprise.\n- **Do not restate deterministic findings.** If `HANDOFF-004` already caught the inverted sequence, do not raise it again here.\n- **Do not echo source content.** Findings are read in CI logs and dashboards. Cite the location; do not paste the row.\n\n### What an AI reviewer may and may not close\n\nMay close a finding (`status: resolved`) when the artifacts now show it was fixed, and cite the change as evidence. Every non-`open` status needs a `decision_ref` that resolves.\n\nThese limits are **enforced by `HANDOFF-010`**, not merely requested here. An AI-authored review that sets `accepted_risk`, or that closes a privacy finding, fails the gate. A closure under a human-only lens additionally has to cite a `DEC-###` that exists in `decision-log.md` with a named decider.\n\n**May not close**, regardless of how obvious the answer looks — these need a named human and a decision record:\n\n- anything under `privacy_and_data_classification` or `environment_and_device_constraints` (configured in `semantic_review.human_only_close_lenses`)\n- anything requiring a business, legal, security, commercial, or budget decision\n- anything that would change scope, a deadline, or an accepted risk\n\nSet `status: open` and name the human in `owner`.\n\n## Output Contract\n\nFor `delivery_planning`: work-item changes, dependency notes, owner gaps, and validation result.\n\nFor `handoff_review`: a `HANDOFF-REVIEW.json` conforming to `templates\u002FHANDOFF-REVIEW.json`, plus a short summary naming what blocks build, what blocks demo, and what needs a human decision. When Visual Proof applies, also identify missing or stale `VISUAL-REVIEW.json` evidence without making an aesthetic verdict.\n\n## Approval Rules\n\nMode escalation and high-risk work require human confirmation before delivery starts.\n\n**A handoff review is not an approval.** `HANDOFF-REVIEW.json` is candidate evidence produced by a reviewer. It never substitutes for the `Design Ready` approval row in `PROJECT.md`, and the Handoff gate introduces no new approval of its own — it reuses the one that already exists. An AI must never move an approval from pending to approved, and must never present a readiness score as a decision. See `docs\u002Fconcepts\u002Fhuman-authority.md`.\n\n## Validation Command\n\n```bash\nnode cli\u002Faxiom.mjs validate --project \u003Cproject> --mode \u003Cmode> --gate Scope\nnode cli\u002Faxiom.mjs validate --project \u003Cproject> --mode \u003Cmode> --gate Handoff\nnode cli\u002Faxiom.mjs handoff --project \u003Cproject> --mode \u003Cmode>\n```\n\n## Prohibited Actions\n\nDo not create hidden task systems, duplicate source of truth, hardcode mode\u002Fgate matrices, or add features outside scope. Do not hardcode review lenses, blocking points, or owner tokens — they come from `pmo-config\u002Fhandoff-policy.json`. Do not record a review whose digests you did not recompute — both of them, after every other artifact is final.\n\n## Completion Criteria\n\nEvery work item references an existing requirement\u002Fbusiness rule and has valid mode, status, and review stage.\n\nFor `handoff_review`: every lens is recorded, every finding has evidence, a suggestion, an owner, and a blocking point, the digest is current, and every finding that needs a human decision is still `open` with that human named. If the visual-artifact triple exists, conditional Visual Proof evidence must also be present and current, while `Design Ready` remains human-owned.\n\nVisual Proof has no `.agents\u002Fskills` mirror. Follow the active `.claude\u002Fskills\u002F` workflow and use\nthe generated `skills\u002F` package only through its repository build command.\n","# pmo-delivery\n\n## Purpose\nTranslate approved scope\u002Fdesign into executable work items and handoff notes, and review whether the resulting contract is actually sufficient for a developer to start, integrate, and demonstrate.\n\n## Trigger\nUse when creating or reviewing `DELIVERY.md`, sequencing work, assigning owners, checking task-source consistency, or preparing\u002Freviewing a handoff.\n\n## Intents\n\n| Intent | Use when | Read set |\n|---|---|---|\n| `delivery_planning` (default) | Creating or changing work items | `PROJECT.md`, `DELIVERY.md`, design context |\n| `handoff_review` | Preparing for, or checking, the Handoff gate | see below |\n\n## Required Inputs\n`PROJECT.md`, task source of truth, relevant design context, and the context\u002Fartifact contract in `pmo-config\u002Fcontext-map.json` and `pmo-config\u002Fartifact-policy.json`.\n\nFor `handoff_review`, additionally: `HANDOFF.md`, `DESIGN\u002FBUILD-SPEC.md`, `RAID-log.md` and `decision-log.md` if present, and `pmo-config\u002Fhandoff-policy.json`. When `DESIGN\u002FVISUAL-DIRECTION.md`, `DESIGN\u002FDESIGN-SYSTEM.md`, and `DESIGN\u002FDESIGN-SYSTEM.html` all exist, also read `DESIGN\u002FVISUAL-REVIEW.json` and the declared capture paths. Read only these. Do not read release artifacts, and do not read `source\u002F**` beyond the rows already cited in `PROJECT.md` unless a specific finding requires it.\n\n## Allowed Context\nUse the context router handoff set. Do not read release artifacts unless the user asks for release readiness.\n\n## Mode Behavior\nUse `pmo-config\u002Fpolicy.json` for mode, status, review-stage, task-source, strict-trigger, and sentinel values. Use `pmo-config\u002Fartifact-policy.json` to decide whether `DELIVERY.md` is required, conditional, or replaceable by GitHub Issues for the active mode and gate. Use `pmo-config\u002Fhandoff-policy.json` for handoff artifacts, review lenses, blocking points, and owner policy.\n\n## Execution Steps - delivery_planning\n\n1. Confirm task source of truth: file or GitHub.\n2. Create work items with mode, strict trigger, requirement ref, design ref, status, review stage, evidence, and labels.\n3. Check enum values against runtime policy.\n4. Flag missing blockers or client decisions.\n5. Route implementation deviations through `CHANGE-REQUESTS.json`; do not silently edit the execution contract or acceptance criteria to absorb them.\n\n## Execution Steps - handoff_review\n\nThe deterministic validator proves the contract is **complete**. It cannot prove it is **sensible**. This review is the part that reads for sense, and its output is structured so the validator can then check that the reading happened, covered everything, and is still current.\n\n1. Run the gate first: `node cli\u002Faxiom.mjs validate --project \u003Cproject> --mode \u003Cmode> --gate Handoff`. Do not re-report anything it already caught. Structural gaps are its job; this review starts where it stops.\n2. Read the artifacts listed above. Read them together, not one at a time — most real findings are contradictions *between* documents, each of which is defensible alone.\n3. Walk **every** lens in `pmo-config\u002Fhandoff-policy.json` `semantic_review.lenses`. Record each one in the output even when it found nothing; a lens with no entry is an unfinished review, and `HANDOFF-010` will say so.\n4. Record findings in `HANDOFF-REVIEW.json` (see `templates\u002FHANDOFF-REVIEW.json`).\n5. Record **both** freshness digests. The `handoffDigest` tool (`src\u002Ftools\u002Fdigest-tools.ts`) prints them:\n   - `source_snapshot.digest` — the material the requirements came from\n   - `review_inputs.digest` — the governed artifacts you actually read\n\n   A review that records only the first keeps reporting as current after\n   someone rewrites the build sequence or waives a build-spec section.\n6. If the visual-artifact triple exists, treat Visual Proof as separate conditional candidate evidence: confirm the manifest has two committed captures, an input digest, complete rubric, named human reviewer, and direction decision references. Do not judge aesthetics yourself, replace the human declaration, or describe this check as a new approval.\n7. Re-run the gate, then `node cli\u002Faxiom.mjs handoff` for stage verdicts.\n8. When the Claude Design provider track is active, merge only current accepted output into the Final Handoff — the output set whose digest `DESIGN\u002FCLAUDE-DESIGN\u002FREVIEW.json` records. Unaccepted or stale output is not handoff content (`DPROV-005`\u002F`DPROV-006`).\n\n### The twelve lenses\n\n| Lens | The question it asks |\n|---|---|\n| `value_and_scope_slice` | Does the slice deliver the value the target milestone has to show? |\n| `capability_lifecycle` | Is each capability complete across its lifecycle, or only the happy path? A count that can go down but never up cannot be demonstrated twice. |\n| `data_cardinality_and_units` | Do entities, cardinality, quantities, and units support the declared use cases? A \"stock\" entity with no quantity and no unit is a name, not a model. |\n| `state_transitions_and_rollback` | Does every state machine declare guards, terminal states, and how a transition is reversed? |\n| `concurrency_and_idempotency` | Two users at once, a retried request, two callers allocating an id. Is any of that specified? |\n| `dependencies_and_build_order` | Can the declared sequence actually be executed in that order? Work-item numbering is not build order. |\n| `ownership_and_capacity` | Does every stream have a named owner, an integrator, and stated capacity that fits the horizon? |\n| `acceptance_seed_reachability` | Can each acceptance case be reached from the declared seed data? |\n| `automated_manual_test_split` | Is each case classified, and does the classification have a runner or a person behind it? |\n| `privacy_and_data_classification` | Do declared data elements, free text, files, and metadata have classification decisions? Does a privacy commitment in one document contradict a feature in another? |\n| `environment_and_device_constraints` | Does the serving model satisfy the declared device and runtime capabilities? |\n| `demo_startup_reset_and_recovery` | Is there a declared startup, reset, degraded, and recovery path? |\n\n### Rules for findings\n\n- **Every finding cites evidence.** `evidence_refs` names the artifact rows the finding is derived from. A finding with no evidence is an opinion.\n- **Every finding has a suggestion and an owner.** Naming a problem without naming the next action or who takes it is not a review outcome.\n- **Never invent a requirement.** If a capability looks incomplete relative to what the source already asked for, that is a *completeness* finding against the existing requirement — not new scope. If it is genuinely new scope, it is an open question for a human, not a finding.\n- **Separate blocking points.** `before_build` is a different claim from `before_demo`. Getting this wrong is the most damaging thing this review can do: mislabelling a demo blocker as a build blocker stalls a team that could be working, and the reverse produces a demo-day surprise.\n- **Do not restate deterministic findings.** If `HANDOFF-004` already caught the inverted sequence, do not raise it again here.\n- **Do not echo source content.** Findings are read in CI logs and dashboards. Cite the location; do not paste the row.\n\n### What an AI reviewer may and may not close\n\nMay close a finding (`status: resolved`) when the artifacts now show it was fixed, and cite the change as evidence. Every non-`open` status needs a `decision_ref` that resolves.\n\nThese limits are **enforced by `HANDOFF-010`**, not merely requested here. An AI-authored review that sets `accepted_risk`, or that closes a privacy finding, fails the gate. A closure under a human-only lens additionally has to cite a `DEC-###` that exists in `decision-log.md` with a named decider.\n\n**May not close**, regardless of how obvious the answer looks — these need a named human and a decision record:\n\n- anything under `privacy_and_data_classification` or `environment_and_device_constraints` (configured in `semantic_review.human_only_close_lenses`)\n- anything requiring a business, legal, security, commercial, or budget decision\n- anything that would change scope, a deadline, or an accepted risk\n\nSet `status: open` and name the human in `owner`.\n\n## Output Contract\n\nFor `delivery_planning`: work-item changes, dependency notes, owner gaps, and validation result.\n\nFor `handoff_review`: a `HANDOFF-REVIEW.json` conforming to `templates\u002FHANDOFF-REVIEW.json`, plus a short summary naming what blocks build, what blocks demo, and what needs a human decision. When Visual Proof applies, also identify missing or stale `VISUAL-REVIEW.json` evidence without making an aesthetic verdict.\n\n## Approval Rules\n\nMode escalation and high-risk work require human confirmation before delivery starts.\n\n**A handoff review is not an approval.** `HANDOFF-REVIEW.json` is candidate evidence produced by a reviewer. It never substitutes for the `Design Ready` approval row in `PROJECT.md`, and the Handoff gate introduces no new approval of its own — it reuses the one that already exists. An AI must never move an approval from pending to approved, and must never present a readiness score as a decision. See `docs\u002Fconcepts\u002Fhuman-authority.md`.\n\n## Validation Command\n\n```bash\nnode cli\u002Faxiom.mjs validate --project \u003Cproject> --mode \u003Cmode> --gate Scope\nnode cli\u002Faxiom.mjs validate --project \u003Cproject> --mode \u003Cmode> --gate Handoff\nnode cli\u002Faxiom.mjs handoff --project \u003Cproject> --mode \u003Cmode>\n```\n\n## Prohibited Actions\n\nDo not create hidden task systems, duplicate source of truth, hardcode mode\u002Fgate matrices, or add features outside scope. Do not hardcode review lenses, blocking points, or owner tokens — they come from `pmo-config\u002Fhandoff-policy.json`. Do not record a review whose digests you did not recompute — both of them, after every other artifact is final.\n\n## Completion Criteria\n\nEvery work item references an existing requirement\u002Fbusiness rule and has valid mode, status, and review stage.\n\nFor `handoff_review`: every lens is recorded, every finding has evidence, a suggestion, an owner, and a blocking point, the digest is current, and every finding that needs a human decision is still `open` with that human named. If the visual-artifact triple exists, conditional Visual Proof evidence must also be present and current, while `Design Ready` remains human-owned.\n\nVisual Proof has no `.agents\u002Fskills` mirror. Follow the active `.claude\u002Fskills\u002F` workflow and use\nthe generated `skills\u002F` package only through its repository build command.\n",{"name":5,"description":7},"main","9a62fb94c5b3066a2810d0e6685c533a4e2df145","skills\u002Fpmo-delivery",1,"https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Freleases","https:\u002F\u002Fgithub.com\u002Fwitchwasin","2026-10-14 19:35:57",{"source":8,"skillName":5,"commands":46,"prompt":56,"zipAvailable":57},[47,50,53],{"tool":48,"command":49},"npx","npx skills add witchwasin\u002FAxiom-PMO --skill pmo-delivery",{"tool":51,"command":52},"bunx","bunx skills add witchwasin\u002FAxiom-PMO --skill pmo-delivery",{"tool":54,"command":55},"pnpm","pnpm dlx skills add witchwasin\u002FAxiom-PMO --skill pmo-delivery","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Fskills\u002Fpmo-delivery\u002FSKILL.md",true,[],[60,73,81,89,98,116],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":32},"01M71ET8C9TYQMP9F4TQT31E1Q","pmo-quality-release","Valid fixture skill description.","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-quality-release\u002FSKILL.md",[],[67,20,68,69,70,71,72],"pmo quality release","quality","release","fixture","fixture skill","valid",{"skillNo":74,"name":75,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":32},"01M71ET6XRZVVAKSP58XX54G3W","pmo-intake","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-intake\u002FSKILL.md",[],[79,20,80],"pmo intake","intake",{"skillNo":82,"name":83,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":32},"01M71ET5CECTETCAE5FNRV0FRE","pmo-governance","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-governance\u002FSKILL.md",[],[87,20,88,70,71,72],"pmo governance","governance",{"skillNo":90,"name":91,"nameZh":6,"description":63,"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":32},"01M71ET3YQASNPFSFPJVG3V660","pmo-git-safety","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-git-safety\u002FSKILL.md",[],[20,95,96,97,70,71,72],"pmo git safety","Safety","git",{"skillNo":99,"name":100,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":113,"publishedAt":32},"01M71ET2DA7SMTNRW95K3QAF5J","pmo-design","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-design\u002FSKILL.md",[103,108],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":109,"categoryName":110,"taxonomyType":111,"taxonomyTypeDesc":112},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[114,20,115,71,72,70],"pmo design","design",{"skillNo":117,"name":5,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":32},"01M71ET0VGV1DVPNXEQWX4P27V","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-delivery\u002FSKILL.md",[],[19,20,21,71,70,72]]