[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71ES4VHNBWK482TA6QAMM4V":3,"skill-same:01M71ES4VHNBWK482TA6QAMM4V":56},{"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":29,"linkOnly":30,"markdownContent":31,"markdownBody":32,"frontMatter":33,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":39,"ownerHtmlUrl":40,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":41,"install":42,"resources":55},"01M71ES4VHNBWK482TA6QAMM4V","pmo-intake",null,"Use when turning source material into scoped, source-referenced PMO requirements and intake decisions.","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\u002F.claude\u002Fskills\u002Fpmo-intake\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28],"intake","pmo","pmo intake","decisions","use","requirements","material","source","scoped","when","2026-11-10 10:12:30",false,"---\nname: pmo-intake\ndescription: Use when turning source material into scoped, source-referenced PMO requirements and intake decisions.\n---\n\n# pmo-intake\n\n## Purpose\nConvert source material into confirmed requirements, assumptions, questions, scope, and mode recommendations.\n\n## Trigger\nUse for new source review, requirement extraction, gap analysis, scope clarification, or source conflict triage.\n\n## Required Inputs\n`PROJECT.md`, relevant `source\u002F**`, and any user-stated goal. Read only the context set allowed by `CONTEXT-ROUTER.md` and `pmo-config\u002Fcontext-map.json`.\n\n## Allowed Context\nDefault to `PROJECT.md` plus the specific source files needed. Do not bulk-load archived skills or every source file unless the task is an impact analysis or conflict review.\n\n## Onboarding\nBefore any intake work on a project whose `PROJECT.md` does not yet declare\nboth `Execution path:` and `Default mode:`, ask the user directly. Do not\ninfer, detect, or silently default either answer — `docs\u002Fconcepts\u002Fexecution-paths.md`\nand `DEC-011` both treat a system claiming to have \"detected\" either answer,\nrather than stating what the user declared, as a fabricated evidence claim.\nThis mirrors `axiom init`'s interactive wizard (`cli\u002Faxiom.mjs`) for the\nskill-based flow, which never invokes that CLI.\n\nAsk, in the user's own words if useful, but cover both:\n\n1. **Who builds this work** — a developer or vendor after a verified\n   handoff (`development_handoff`), or an AI execution agent under a\n   governed contract, verified afterward against git ground truth\n   (`governed_ai_execution`)? See `docs\u002Fconcepts\u002Fexecution-paths.md`.\n2. **How strictly should this be governed** — Lite, Standard, or Strict?\n   If the user is unsure, walk through `pmo-config\u002Fpolicy.json`\n   `enums.strict_triggers` (payment, financial calculation, PII, sensitive\n   data, authentication, authorization, permission, irreversible action,\n   external integration, compliance, production migration, critical\n   infrastructure, public-sector formal acceptance) — any match recommends\n   Strict.\n\nRecord both answers in `PROJECT.md` (`Execution path:` and `Default mode:`\nlines) and log the choice in `decision-log.md` if the project keeps one,\nstating plainly that this is what the user declared. Skip this step only\nwhen `PROJECT.md` already carries both declarations from a prior session —\nre-asking on every message is not required. A project may still escalate a\nspecific work item to Strict later via the normal per-item mode\nrecommendation below; this onboarding step sets the project-level default,\nnot a ceiling.\n\n## Mode Behavior\nUse the mode, strict-trigger, evidence-status, and approval enums from `pmo-config\u002Fpolicy.json`; do not repeat or extend them inside the skill. Lite captures only essential source, scope, and release approval needs. Standard captures normal requirements and design implications. Strict escalation follows the configured strict triggers.\n\n## Execution Steps\n0. Complete Onboarding above if `PROJECT.md` does not yet declare both `Execution path:` and `Default mode:`.\n1. Identify confirmed facts, assumptions, and open questions.\n2. Assign stable requirement IDs and `source_ref`.\n3. Mark evidence status from configured policy values.\n4. Recommend Lite, Standard, or Strict per work item.\n5. Update or request Source Snapshot refresh when source files change.\n6. When the project declares Research mode `guided` or `auto`, draft the Research Brief from preliminary requirements and unknowns (see `docs\u002Fconcepts\u002Fresearch-workflow.md`); keep every material claim source-backed in `RESEARCH\u002FPROVENANCE.json`. Research findings are candidate evidence that only a Human decision at Scope can act on.\n\n## Output Contract\nReturn confirmed requirements, assumptions, open questions, source references, confidence notes, and mode recommendation.\n\n## Approval Rules\nScope approval is human-owned. AI may draft rows but must not mark approval as granted without explicit source evidence.\n\n## Validation Command\n`node cli\u002Faxiom.mjs validate --project \u003Cproject> --mode \u003Cmode> --gate Scope`\n\n## Prohibited Actions\nDo not invent requirements, bulk-load all source by default, silently resolve conflicts, push commits, deploy, or approve release. Do not write or infer `Execution path:` or `Default mode:` into `PROJECT.md` without first asking the user per Onboarding above, and never describe either as \"detected.\"\n\n## Completion Criteria\nEvery in-scope requirement has `source_ref`, evidence status, and either confirmed acceptance or an open question.\n","# pmo-intake\n\n## Purpose\nConvert source material into confirmed requirements, assumptions, questions, scope, and mode recommendations.\n\n## Trigger\nUse for new source review, requirement extraction, gap analysis, scope clarification, or source conflict triage.\n\n## Required Inputs\n`PROJECT.md`, relevant `source\u002F**`, and any user-stated goal. Read only the context set allowed by `CONTEXT-ROUTER.md` and `pmo-config\u002Fcontext-map.json`.\n\n## Allowed Context\nDefault to `PROJECT.md` plus the specific source files needed. Do not bulk-load archived skills or every source file unless the task is an impact analysis or conflict review.\n\n## Onboarding\nBefore any intake work on a project whose `PROJECT.md` does not yet declare\nboth `Execution path:` and `Default mode:`, ask the user directly. Do not\ninfer, detect, or silently default either answer — `docs\u002Fconcepts\u002Fexecution-paths.md`\nand `DEC-011` both treat a system claiming to have \"detected\" either answer,\nrather than stating what the user declared, as a fabricated evidence claim.\nThis mirrors `axiom init`'s interactive wizard (`cli\u002Faxiom.mjs`) for the\nskill-based flow, which never invokes that CLI.\n\nAsk, in the user's own words if useful, but cover both:\n\n1. **Who builds this work** — a developer or vendor after a verified\n   handoff (`development_handoff`), or an AI execution agent under a\n   governed contract, verified afterward against git ground truth\n   (`governed_ai_execution`)? See `docs\u002Fconcepts\u002Fexecution-paths.md`.\n2. **How strictly should this be governed** — Lite, Standard, or Strict?\n   If the user is unsure, walk through `pmo-config\u002Fpolicy.json`\n   `enums.strict_triggers` (payment, financial calculation, PII, sensitive\n   data, authentication, authorization, permission, irreversible action,\n   external integration, compliance, production migration, critical\n   infrastructure, public-sector formal acceptance) — any match recommends\n   Strict.\n\nRecord both answers in `PROJECT.md` (`Execution path:` and `Default mode:`\nlines) and log the choice in `decision-log.md` if the project keeps one,\nstating plainly that this is what the user declared. Skip this step only\nwhen `PROJECT.md` already carries both declarations from a prior session —\nre-asking on every message is not required. A project may still escalate a\nspecific work item to Strict later via the normal per-item mode\nrecommendation below; this onboarding step sets the project-level default,\nnot a ceiling.\n\n## Mode Behavior\nUse the mode, strict-trigger, evidence-status, and approval enums from `pmo-config\u002Fpolicy.json`; do not repeat or extend them inside the skill. Lite captures only essential source, scope, and release approval needs. Standard captures normal requirements and design implications. Strict escalation follows the configured strict triggers.\n\n## Execution Steps\n0. Complete Onboarding above if `PROJECT.md` does not yet declare both `Execution path:` and `Default mode:`.\n1. Identify confirmed facts, assumptions, and open questions.\n2. Assign stable requirement IDs and `source_ref`.\n3. Mark evidence status from configured policy values.\n4. Recommend Lite, Standard, or Strict per work item.\n5. Update or request Source Snapshot refresh when source files change.\n6. When the project declares Research mode `guided` or `auto`, draft the Research Brief from preliminary requirements and unknowns (see `docs\u002Fconcepts\u002Fresearch-workflow.md`); keep every material claim source-backed in `RESEARCH\u002FPROVENANCE.json`. Research findings are candidate evidence that only a Human decision at Scope can act on.\n\n## Output Contract\nReturn confirmed requirements, assumptions, open questions, source references, confidence notes, and mode recommendation.\n\n## Approval Rules\nScope approval is human-owned. AI may draft rows but must not mark approval as granted without explicit source evidence.\n\n## Validation Command\n`node cli\u002Faxiom.mjs validate --project \u003Cproject> --mode \u003Cmode> --gate Scope`\n\n## Prohibited Actions\nDo not invent requirements, bulk-load all source by default, silently resolve conflicts, push commits, deploy, or approve release. Do not write or infer `Execution path:` or `Default mode:` into `PROJECT.md` without first asking the user per Onboarding above, and never describe either as \"detected.\"\n\n## Completion Criteria\nEvery in-scope requirement has `source_ref`, evidence status, and either confirmed acceptance or an open question.\n",{"name":5,"description":7},"main","9a62fb94c5b3066a2810d0e6685c533a4e2df145",".claude\u002Fskills\u002Fpmo-intake",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":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add witchwasin\u002FAxiom-PMO --skill pmo-intake",{"tool":48,"command":49},"bunx","bunx skills add witchwasin\u002FAxiom-PMO --skill pmo-intake",{"tool":51,"command":52},"pnpm","pnpm dlx skills add witchwasin\u002FAxiom-PMO --skill pmo-intake","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fpmo-intake\u002FSKILL.md",true,[],[57,70,75,83,92,110],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":29},"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",[],[64,20,65,66,67,68,69],"pmo quality release","quality","release","fixture","fixture skill","valid",{"skillNo":71,"name":5,"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":72,"categories":73,"keywords":74,"publishedAt":29},"01M71ET6XRZVVAKSP58XX54G3W","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-intake\u002FSKILL.md",[],[21,20,19],{"skillNo":76,"name":77,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":29},"01M71ET5CECTETCAE5FNRV0FRE","pmo-governance","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-governance\u002FSKILL.md",[],[81,20,82,67,68,69],"pmo governance","governance",{"skillNo":84,"name":85,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":29},"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,89,90,91,67,68,69],"pmo git safety","Safety","git",{"skillNo":93,"name":94,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":107,"publishedAt":29},"01M71ET2DA7SMTNRW95K3QAF5J","pmo-design","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-design\u002FSKILL.md",[97,102],{"categoryNo":98,"categoryName":99,"taxonomyType":100,"taxonomyTypeDesc":101},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":103,"categoryName":104,"taxonomyType":105,"taxonomyTypeDesc":106},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[108,20,109,68,69,67],"pmo design","design",{"skillNo":111,"name":112,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":29},"01M71ET0VGV1DVPNXEQWX4P27V","pmo-delivery","https:\u002F\u002Fgithub.com\u002Fwitchwasin\u002FAxiom-PMO\u002Fblob\u002Fmain\u002Ftests\u002Fdoctor-fixtures\u002Fskill-without-frontmatter\u002Fskills\u002Fpmo-delivery\u002FSKILL.md",[],[116,20,117,68,67,69],"delivery","pmo delivery"]