[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727JMG4VXMQTEWNEPMN3EPT":3,"skill-same:01M727JMG4VXMQTEWNEPMN3EPT":71},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":31,"commitSha":32,"skillDirectory":33,"forksCount":34,"repositoryHtmlUrl":35,"repositoryHomepageUrl":36,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M727JMG4VXMQTEWNEPMN3EPT","foundation-meeting-synthesize",null,"Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeline, themes with confidence markers, stakeholder position tracking, consolidated decision list, contradiction flags, open items, narrative summary, and prioritized follow-ups.","product-on-purpose\u002Fpm-skills","product-on-purpose","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F253892650?v=4","01M7230Q4442AHBADCVFJCS277","Product on Purpose","01M727ASMTF77MQ3AKT3GKRQWM",805,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-meeting-synthesize\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: foundation-meeting-synthesize\ndescription: Cross-meeting archaeology skill. Consumes multiple meeting recaps (or raw notes) over a period and surfaces patterns invisible in any single meeting. Shows how decisions evolved, who has been saying what, where threads are stalling, and where contradictions have emerged. Produces a plain-text timeline, themes with confidence markers, stakeholder position tracking, consolidated decision list, contradiction flags, open items, narrative summary, and prioritized follow-ups.\nlicense: Apache-2.0\nmetadata:\n  classification: foundation\n  version: \"1.2.0\"\n  updated: 2026-07-05\n  category: meeting\n  frameworks: [meeting-skills-family]\n  author: product-on-purpose\n---\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Meeting Synthesize\n\nMeeting synthesis is the archaeology skill for multi-meeting initiatives. It consumes a set of meeting recaps (and optionally raw notes) over a period, and surfaces patterns that no single meeting reveals: how decisions evolved, how stakeholder positions shifted, where threads are stalling, where contradictions have emerged.\n\nDistinct from `\u002Fdiscover-interview-synthesis`: that skill works on user-research conversations with research-specific frameworks (jobs-to-be-done, buying insights). This skill works on internal org meetings with org-specific patterns (stakeholder alignment, decision evolution, project history).\n\nThis skill belongs to the Meeting Skills Family. It conforms to the [Meeting Skills Family Contract](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fskill-families\u002Fmeeting-skills-contract.md).\n\n## When to Use\n\n- Board prep or exec-brief preparation across a meeting sequence\n- Onboarding a new team member into the history of an initiative\n- Project retrospective input (the story of how we got here)\n- Investigating why a multi-meeting initiative has stalled\n- Quarterly review of a topic that has crossed many meetings\n- Surfacing contradictions that no single-meeting reviewer caught\n\n## When NOT to Use\n\n- Single-meeting summary. Use `foundation-meeting-recap` instead.\n- Communicating outcomes outward. Use `foundation-stakeholder-update`.\n- User research conversation synthesis. Use `discover-interview-synthesis`.\n\n## Zero-friction execution\n\nPer the family contract, this skill never blocks on interrogation. Default flow:\n\n1. Load all provided source files (recaps preferred, raw notes accepted with lower input-quality flag)\n2. Apply any filters (time range, topic, stakeholder)\n3. Run inference on themes, stakeholder evolution, contradictions\n4. Present a brief inference summary (meeting count after filter, time range detected, per-source input quality, scope filter applied)\n5. Accept `go` or corrections\n6. Produce the synthesis\n\nIf invoked with `--go`, skip the inference summary. Format hints (`board-prep`, `onboarding`, `retro-input`, `exec-brief`) control output presentation without changing the underlying process.\n\n## Instructions\n\nWhen asked to create a meeting synthesis, follow these steps:\n\n1. **Load sources**\n   Read all provided recap filenames or note files. Parse frontmatter to extract meeting metadata. Note per-source input quality (recap frontmatter's `input_quality` if available; otherwise assess from content).\n\n   **Metadata source tracking** (v1.1.0): for each recap, also note the `meeting_type_source` field (`explicit | inferred | null`). When synthesizing across mixed sources, the synthesis must document the mix explicitly in the Scope section: \"meeting_type values: N explicit, M inferred, K null.\" This prevents non-reproducible results when filtering by meeting_type across a mix of confidence levels. If filtering by `meeting_type`, state whether the filter includes inferred values and how null values are handled.\n\n2. **Apply filters**\n   If time range, topic, or stakeholder filter provided, narrow the source set before proceeding. Record the filter applied in frontmatter `scope_filter`.\n\n3. **Present go-mode inference summary**\n   Meeting count after filter, time range detected from source metadata, per-source input quality levels, scope filter description.\n\n4. **Build the plain-text timeline**\n   Chronological order by `meeting_date`. Each entry shows date, meeting name, key decision or shift, and confidence or contradiction flag if applicable. Render as markdown (no binary images. must render everywhere).\n\n5. **Extract themes**\n   Cluster recurring topics across sources. For each theme, record description, sources where it appeared, and confidence marker tied to frequency (\"appears in 5\u002F5 meetings\" → high; \"appears in 2\u002F5 meetings\" → medium; \"mentioned in 1 meeting\" → low).\n\n6. **Track stakeholder positions**\n   For each named stakeholder across sources, record initial position → current position, alignment state (aligned \u002F divergent \u002F shifting), and key statements with dates. Flag confidence on each position based on whether it was direct-quoted or paraphrased.\n\n7. **Consolidate decisions**\n   Cross-meeting, sorted chronologically. Table format: Date | Decision | Context | Meeting | Confidence.\n\n8. **Separate decision evolution from unresolved contradictions** (v1.1.0)\n   Two distinct outputs, not one combined \"contradictions\" section:\n   - **Decision evolution** (resolved): earlier decision → later decision on the same topic, where the later one supersedes. This is historical context, not a red flag. No `⚠` emphasis.\n   - **Unresolved contradictions**: decisions or positions currently in conflict that need reconciliation. Use `⚠` visual emphasis. For each:\n     - Earlier reference (meeting + date + decision)\n     - Later reference (meeting + date + decision that conflicts)\n     - Status: unresolved \u002F needs reconciliation\n   \n   The distinction matters because v1.0.0 conflated them, creating false-positive \"contradictions\" in exec contexts where the \"contradiction\" was actually intentional scope evolution.\n\n9. **Identify open items and stalled threads**\n   Topics surfacing 2+ times without resolution. When they last appeared.\n\n10. **Draft narrative summary**\n    2-3 paragraphs: what happened, what changed, where we are, what is at stake. The \"story\" of the meeting set.\n\n11. **Prioritize follow-up suggestions**\n    - High: unblocking now; suggested owner or forum\n    - Medium: important but not blocking\n    - Low: monitor\n    Each with rationale.\n\n12. **Apply format hint** (if provided)\n    One process generates the full synthesis data. The hint controls section ordering and truncation for the specific use case:\n    - `board-prep`: lead with narrative + contradictions + prioritized follow-ups; shorter timeline\n    - `onboarding`: lead with narrative + stakeholder tracking; full timeline\n    - `retro-input`: lead with themes + stalled threads + meeting-quality aggregate\n    - `exec-brief`: TL;DR + top 3 items only\n\n13. **Render TEMPLATE.md and validate**\n    - `source_meetings` list is non-empty\n    - `time_range.start` ≤ `time_range.end`\n    - Every theme has a confidence marker\n    - Every contradiction has before\u002Fafter source citations\n    - At least 1 prioritized follow-up\n\n## Project Memory Contract\n\nActive only when `.claude\u002Fpm-skills.local.md` exists. With no file, ignore this section entirely\nand behave exactly as described above.\n\n- **Reads:** `active_initiative` and prior `interpretation` artifacts on the same topic, so the synthesis shows movement rather than restating what is already recorded.\n- **Writes:** the synthesis as an `interpretation` artifact.\n- **Posture:** propose the entry and wait for confirmation before writing, unless\n  `memory_auto_append: true` is set, in which case append and echo what was written.\n- **Write discipline:** re-read the file immediately before writing, never from the copy that\n  produced the proposal. If it changed in between, merge your entry into the current state and\n  re-propose rather than overwriting; add only your own entry and leave every other field and\n  section byte-identical. Nothing enforces this at runtime and the file is gitignored, so a\n  careless whole-file write loses another session's work with no way to recover it.\n\nThis complements the family's filename-based chaining rather than replacing it: filenames still locate the sibling artifacts of one meeting, while project memory carries the durable product context across meetings.\n## Quality Checklist\n\n- [ ] Source meetings listed with filename + date + per-source input quality\n- [ ] Time range populated and sensible\n- [ ] Scope filter described (or \"none applied\")\n- [ ] Timeline is plain-text markdown (no binary images)\n- [ ] Themes include confidence markers tied to frequency\n- [ ] Stakeholder position tracking shows evolution (initial → current), not just snapshot\n- [ ] Consolidated decision list is chronological with source citations\n- [ ] Contradictions are flagged in their own first-class section (not buried)\n- [ ] Narrative summary is 2-3 paragraphs, not bullets\n- [ ] Follow-ups are prioritized (High \u002F Medium \u002F Low) with rationale\n- [ ] Frontmatter omits single-meeting fields (meeting_title, meeting_date, etc.)\n- [ ] Sources and References weights input quality across sources\n\n## See also\n\n- [Meeting Skills Family Contract](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fskill-families\u002Fmeeting-skills-contract.md)\n- [`foundation-meeting-recap`](..\u002Ffoundation-meeting-recap\u002FSKILL.md). upstream: primary input source\n- [`\u002Fdiscover-interview-synthesis`](..\u002Fdiscover-interview-synthesis\u002FSKILL.md). sibling pattern for user-research conversations (different domain)\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Meeting Synthesize\n\nMeeting synthesis is the archaeology skill for multi-meeting initiatives. It consumes a set of meeting recaps (and optionally raw notes) over a period, and surfaces patterns that no single meeting reveals: how decisions evolved, how stakeholder positions shifted, where threads are stalling, where contradictions have emerged.\n\nDistinct from `\u002Fdiscover-interview-synthesis`: that skill works on user-research conversations with research-specific frameworks (jobs-to-be-done, buying insights). This skill works on internal org meetings with org-specific patterns (stakeholder alignment, decision evolution, project history).\n\nThis skill belongs to the Meeting Skills Family. It conforms to the [Meeting Skills Family Contract](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fskill-families\u002Fmeeting-skills-contract.md).\n\n## When to Use\n\n- Board prep or exec-brief preparation across a meeting sequence\n- Onboarding a new team member into the history of an initiative\n- Project retrospective input (the story of how we got here)\n- Investigating why a multi-meeting initiative has stalled\n- Quarterly review of a topic that has crossed many meetings\n- Surfacing contradictions that no single-meeting reviewer caught\n\n## When NOT to Use\n\n- Single-meeting summary. Use `foundation-meeting-recap` instead.\n- Communicating outcomes outward. Use `foundation-stakeholder-update`.\n- User research conversation synthesis. Use `discover-interview-synthesis`.\n\n## Zero-friction execution\n\nPer the family contract, this skill never blocks on interrogation. Default flow:\n\n1. Load all provided source files (recaps preferred, raw notes accepted with lower input-quality flag)\n2. Apply any filters (time range, topic, stakeholder)\n3. Run inference on themes, stakeholder evolution, contradictions\n4. Present a brief inference summary (meeting count after filter, time range detected, per-source input quality, scope filter applied)\n5. Accept `go` or corrections\n6. Produce the synthesis\n\nIf invoked with `--go`, skip the inference summary. Format hints (`board-prep`, `onboarding`, `retro-input`, `exec-brief`) control output presentation without changing the underlying process.\n\n## Instructions\n\nWhen asked to create a meeting synthesis, follow these steps:\n\n1. **Load sources**\n   Read all provided recap filenames or note files. Parse frontmatter to extract meeting metadata. Note per-source input quality (recap frontmatter's `input_quality` if available; otherwise assess from content).\n\n   **Metadata source tracking** (v1.1.0): for each recap, also note the `meeting_type_source` field (`explicit | inferred | null`). When synthesizing across mixed sources, the synthesis must document the mix explicitly in the Scope section: \"meeting_type values: N explicit, M inferred, K null.\" This prevents non-reproducible results when filtering by meeting_type across a mix of confidence levels. If filtering by `meeting_type`, state whether the filter includes inferred values and how null values are handled.\n\n2. **Apply filters**\n   If time range, topic, or stakeholder filter provided, narrow the source set before proceeding. Record the filter applied in frontmatter `scope_filter`.\n\n3. **Present go-mode inference summary**\n   Meeting count after filter, time range detected from source metadata, per-source input quality levels, scope filter description.\n\n4. **Build the plain-text timeline**\n   Chronological order by `meeting_date`. Each entry shows date, meeting name, key decision or shift, and confidence or contradiction flag if applicable. Render as markdown (no binary images. must render everywhere).\n\n5. **Extract themes**\n   Cluster recurring topics across sources. For each theme, record description, sources where it appeared, and confidence marker tied to frequency (\"appears in 5\u002F5 meetings\" → high; \"appears in 2\u002F5 meetings\" → medium; \"mentioned in 1 meeting\" → low).\n\n6. **Track stakeholder positions**\n   For each named stakeholder across sources, record initial position → current position, alignment state (aligned \u002F divergent \u002F shifting), and key statements with dates. Flag confidence on each position based on whether it was direct-quoted or paraphrased.\n\n7. **Consolidate decisions**\n   Cross-meeting, sorted chronologically. Table format: Date | Decision | Context | Meeting | Confidence.\n\n8. **Separate decision evolution from unresolved contradictions** (v1.1.0)\n   Two distinct outputs, not one combined \"contradictions\" section:\n   - **Decision evolution** (resolved): earlier decision → later decision on the same topic, where the later one supersedes. This is historical context, not a red flag. No `⚠` emphasis.\n   - **Unresolved contradictions**: decisions or positions currently in conflict that need reconciliation. Use `⚠` visual emphasis. For each:\n     - Earlier reference (meeting + date + decision)\n     - Later reference (meeting + date + decision that conflicts)\n     - Status: unresolved \u002F needs reconciliation\n   \n   The distinction matters because v1.0.0 conflated them, creating false-positive \"contradictions\" in exec contexts where the \"contradiction\" was actually intentional scope evolution.\n\n9. **Identify open items and stalled threads**\n   Topics surfacing 2+ times without resolution. When they last appeared.\n\n10. **Draft narrative summary**\n    2-3 paragraphs: what happened, what changed, where we are, what is at stake. The \"story\" of the meeting set.\n\n11. **Prioritize follow-up suggestions**\n    - High: unblocking now; suggested owner or forum\n    - Medium: important but not blocking\n    - Low: monitor\n    Each with rationale.\n\n12. **Apply format hint** (if provided)\n    One process generates the full synthesis data. The hint controls section ordering and truncation for the specific use case:\n    - `board-prep`: lead with narrative + contradictions + prioritized follow-ups; shorter timeline\n    - `onboarding`: lead with narrative + stakeholder tracking; full timeline\n    - `retro-input`: lead with themes + stalled threads + meeting-quality aggregate\n    - `exec-brief`: TL;DR + top 3 items only\n\n13. **Render TEMPLATE.md and validate**\n    - `source_meetings` list is non-empty\n    - `time_range.start` ≤ `time_range.end`\n    - Every theme has a confidence marker\n    - Every contradiction has before\u002Fafter source citations\n    - At least 1 prioritized follow-up\n\n## Project Memory Contract\n\nActive only when `.claude\u002Fpm-skills.local.md` exists. With no file, ignore this section entirely\nand behave exactly as described above.\n\n- **Reads:** `active_initiative` and prior `interpretation` artifacts on the same topic, so the synthesis shows movement rather than restating what is already recorded.\n- **Writes:** the synthesis as an `interpretation` artifact.\n- **Posture:** propose the entry and wait for confirmation before writing, unless\n  `memory_auto_append: true` is set, in which case append and echo what was written.\n- **Write discipline:** re-read the file immediately before writing, never from the copy that\n  produced the proposal. If it changed in between, merge your entry into the current state and\n  re-propose rather than overwriting; add only your own entry and leave every other field and\n  section byte-identical. Nothing enforces this at runtime and the file is gitignored, so a\n  careless whole-file write loses another session's work with no way to recover it.\n\nThis complements the family's filename-based chaining rather than replacing it: filenames still locate the sibling artifacts of one meeting, while project memory carries the durable product context across meetings.\n## Quality Checklist\n\n- [ ] Source meetings listed with filename + date + per-source input quality\n- [ ] Time range populated and sensible\n- [ ] Scope filter described (or \"none applied\")\n- [ ] Timeline is plain-text markdown (no binary images)\n- [ ] Themes include confidence markers tied to frequency\n- [ ] Stakeholder position tracking shows evolution (initial → current), not just snapshot\n- [ ] Consolidated decision list is chronological with source citations\n- [ ] Contradictions are flagged in their own first-class section (not buried)\n- [ ] Narrative summary is 2-3 paragraphs, not bullets\n- [ ] Follow-ups are prioritized (High \u002F Medium \u002F Low) with rationale\n- [ ] Frontmatter omits single-meeting fields (meeting_title, meeting_date, etc.)\n- [ ] Sources and References weights input quality across sources\n\n## See also\n\n- [Meeting Skills Family Contract](..\u002F..\u002Fsite\u002Fsrc\u002Fcontent\u002Fdocs\u002Freference\u002Fskill-families\u002Fmeeting-skills-contract.md)\n- [`foundation-meeting-recap`](..\u002Ffoundation-meeting-recap\u002FSKILL.md). upstream: primary input source\n- [`\u002Fdiscover-interview-synthesis`](..\u002Fdiscover-interview-synthesis\u002FSKILL.md). sibling pattern for user-research conversations (different domain)\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":9,"updated":25,"version":26,"category":27,"frameworks":28,"classification":30},1783209600000,"1.2.0","meeting",[29],"meeting-skills-family","foundation","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Ffoundation-meeting-synthesize",102,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills","https:\u002F\u002Fproduct-on-purpose.github.io\u002Fpm-skills\u002F","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose","2026-11-14 16:57:35",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add product-on-purpose\u002Fpm-skills --skill foundation-meeting-synthesize",{"tool":45,"command":46},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill foundation-meeting-synthesize",{"tool":48,"command":49},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill foundation-meeting-synthesize","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-meeting-synthesize\u002FSKILL.md",true,[53,59,63,67],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"evals\u002Ftrigger-fixtures.json","REFERENCE","参考文档",3763,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-meeting-synthesize\u002Fevals\u002Ftrigger-fixtures.json",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"HISTORY.md",3092,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-meeting-synthesize\u002FHISTORY.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002FEXAMPLE.md",12242,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-meeting-synthesize\u002Freferences\u002FEXAMPLE.md",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002FTEMPLATE.md",5821,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Ffoundation-meeting-synthesize\u002Freferences\u002FTEMPLATE.md",[72,79,86,93,100,107],{"skillNo":73,"name":74,"nameZh":6,"description":75,"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":19},"01M727QTD4J5TPP3EEYPXMGZE4","utility-update-pm-skills","Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-update-pm-skills\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M727QQSXYBZK7D29C80WMQ8M","utility-slideshow-creator","Generates professional presentations from a JSON deck specification using 18 slide types with dark\u002Flight variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-slideshow-creator\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M727QKYD45K0PCJ591046TK2","utility-pm-workflow-orchestrator","Run an ordered sequence of pm-skills against one input, pausing for go\u002Fno-go and stopping on a failed or empty step. Accepts a saved prioritized action plan (Mode A) or an ad-hoc named chain (Mode B; the chain command routes here). Explicit invocation only; run --dry-run first while the native path is EXPERIMENTAL. To author a durable workflow instead, use utility-pm-workflow-builder.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-orchestrator\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M727QFN6W9M8JGVXNQMT5642","utility-pm-workflow-builder","Guides a contributor from a workflow idea to a complete Workflow Implementation Packet (draft workflow file, draft workflow command, cross-cutting update checklist) in a staging area for review. Runs overlap analysis against the existing workflows with a Why Gate, then helps select and sequence skills with authored handoffs. Use when creating a new multi-skill workflow or promoting a repeated ad-hoc chain into a durable one. To build a single skill instead, use utility-pm-skill-builder; to run a sequence without authoring anything, use the chain command or utility-pm-workflow-orchestrator.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-workflow-builder\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M727QCDS2WFTJPHXASSE5W6X","utility-pm-skill-validate","Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass\u002Ffail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-skill-validate\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M727Q8GW1AZWPNWXYH7WHG9F","utility-pm-skill-iterate","Applies targeted improvements to an existing pm-skills skill based on feedback, validation reports, or convention changes. Reads current files, previews proposed changes, writes on confirmation, and suggests a version bump. Use when improving a skill after validation or feedback.","https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Futility-pm-skill-iterate\u002FSKILL.md",[],[]]