[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M727KMEG8EWR9P3VSGQ69D1W":3,"skill-same:01M727KMEG8EWR9P3VSGQ69D1W":77},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":38,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M727KMEG8EWR9P3VSGQ69D1W","iterate-retrospective",null,"Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of a sprint, project, or milestone to reflect and improve team practices. To bank individual learnings into organizational memory afterward, use iterate-lessons-log.","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\u002Fiterate-retrospective\u002FSKILL.md",[],[],"2026-11-10 18:39:20",false,"---\nname: iterate-retrospective\ndescription: Facilitates and documents a team retrospective capturing what went well, what to improve, and action items. Use at the end of a sprint, project, or milestone to reflect and improve team practices. To bank individual learnings into organizational memory afterward, use iterate-lessons-log.\nlicense: Apache-2.0\nmetadata:\n  phase: iterate\n  version: \"2.2.0\"\n  updated: 2026-06-10\n  category: reflection\n  frameworks: [triple-diamond, lean-startup, design-thinking]\n  author: product-on-purpose\n---\n\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Retrospective\n\nA retrospective is a structured reflection that helps teams learn from their experiences and continuously improve. By regularly examining what went well, what didn't, and what to change, teams build a culture of learning and adaptation. The value isn't just in the discussion.it's in the documented actions and follow-through.\n\n## When to Use\n\n- At the end of every sprint (for agile teams)\n- After completing a significant project or milestone\n- Following a major incident or outage\n- When team dynamics feel off and need addressing\n- At regular intervals (monthly, quarterly) even without specific triggers\n- When onboarding new team members to establish improvement culture\n\n## When NOT to Use\n\n- You want one durable learning banked for the organization -> use `iterate-lessons-log`; the retro is the ceremony, the log entry outlives it\n- You are scoring an OKR cycle at close -> use `measure-okr-grader`\n- The reflection must end in a pivot-or-persevere call -> use `iterate-pivot-decision`\n- You need a recap of a general (non-retro) meeting -> use `foundation-meeting-recap`\n\n## Instructions\n\nWhen asked to facilitate or document a retrospective, follow these steps:\n\n1. **Set the Context**\n   Define what period or project this retrospective covers, who attended, and any significant events that occurred. This frames the discussion and helps future readers understand the context.\n\n2. **Choose a Format**\n   Select a retrospective format that fits the team's needs. Common options include:\n   - **Start\u002FStop\u002FContinue:** Simple and direct\n   - **4Ls:** Liked, Learned, Lacked, Longed for\n   - **Mad\u002FSad\u002FGlad:** Emotion-focused\n   - **Sailboat:** Visual metaphor (wind=helps, anchor=holds back)\n\n3. **Gather Input**\n   Collect observations from all team members. Ensure everyone contributes.quiet voices often have important insights. Group similar items to identify themes.\n\n4. **Discuss and Prioritize**\n   Don't try to address everything. Focus the discussion on the most impactful items. Vote or discuss to identify the top 2-3 issues to address.\n\n5. **Define Action Items**\n   Convert insights into specific, assignable actions. Every action needs an owner and a due date. Avoid vague improvements like \"communicate better.\"\n\n6. **Review Previous Actions**\n   Check the status of action items from the last retrospective. Celebrate completions and discuss blockers for incomplete items. This builds accountability.\n\n7. **Document for Future Reference**\n   Capture the key points so they're available for future team members and for tracking patterns over time.\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:** the recent `artifacts[]` entries, so the retrospective can look at what the cycle actually produced instead of relying on recall.\n- **Writes:** the lessons 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\nA retrospective surfaces raw observations, patterns, and commitments at once. Record the durable half, the lessons, under a single tag; a downstream reader needs to know how firmly to weight the entry, and a mixed tag tells it nothing.\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete retrospective fills every template section: Overview; Previous Retrospective Review; What Went Well; What to Improve; Discussion Notes; Action Items; Parking Lot; Metrics and Trends; Facilitator Notes; and Next Retrospective.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] All attendees had opportunity to contribute\n- [ ] Both positives and improvements are captured\n- [ ] Action items have owners and due dates\n- [ ] Previous retrospective actions are reviewed\n- [ ] A reader who missed the retro can tell what was decided and who owns each action from this document alone\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed example.\n","\u003C!-- PM-Skills | https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills | Apache 2.0 -->\n# Retrospective\n\nA retrospective is a structured reflection that helps teams learn from their experiences and continuously improve. By regularly examining what went well, what didn't, and what to change, teams build a culture of learning and adaptation. The value isn't just in the discussion.it's in the documented actions and follow-through.\n\n## When to Use\n\n- At the end of every sprint (for agile teams)\n- After completing a significant project or milestone\n- Following a major incident or outage\n- When team dynamics feel off and need addressing\n- At regular intervals (monthly, quarterly) even without specific triggers\n- When onboarding new team members to establish improvement culture\n\n## When NOT to Use\n\n- You want one durable learning banked for the organization -> use `iterate-lessons-log`; the retro is the ceremony, the log entry outlives it\n- You are scoring an OKR cycle at close -> use `measure-okr-grader`\n- The reflection must end in a pivot-or-persevere call -> use `iterate-pivot-decision`\n- You need a recap of a general (non-retro) meeting -> use `foundation-meeting-recap`\n\n## Instructions\n\nWhen asked to facilitate or document a retrospective, follow these steps:\n\n1. **Set the Context**\n   Define what period or project this retrospective covers, who attended, and any significant events that occurred. This frames the discussion and helps future readers understand the context.\n\n2. **Choose a Format**\n   Select a retrospective format that fits the team's needs. Common options include:\n   - **Start\u002FStop\u002FContinue:** Simple and direct\n   - **4Ls:** Liked, Learned, Lacked, Longed for\n   - **Mad\u002FSad\u002FGlad:** Emotion-focused\n   - **Sailboat:** Visual metaphor (wind=helps, anchor=holds back)\n\n3. **Gather Input**\n   Collect observations from all team members. Ensure everyone contributes.quiet voices often have important insights. Group similar items to identify themes.\n\n4. **Discuss and Prioritize**\n   Don't try to address everything. Focus the discussion on the most impactful items. Vote or discuss to identify the top 2-3 issues to address.\n\n5. **Define Action Items**\n   Convert insights into specific, assignable actions. Every action needs an owner and a due date. Avoid vague improvements like \"communicate better.\"\n\n6. **Review Previous Actions**\n   Check the status of action items from the last retrospective. Celebrate completions and discuss blockers for incomplete items. This builds accountability.\n\n7. **Document for Future Reference**\n   Capture the key points so they're available for future team members and for tracking patterns over time.\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:** the recent `artifacts[]` entries, so the retrospective can look at what the cycle actually produced instead of relying on recall.\n- **Writes:** the lessons 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\nA retrospective surfaces raw observations, patterns, and commitments at once. Record the durable half, the lessons, under a single tag; a downstream reader needs to know how firmly to weight the entry, and a mixed tag tells it nothing.\n## Output Format\n\nUse the template in `references\u002FTEMPLATE.md` to structure the output. A complete retrospective fills every template section: Overview; Previous Retrospective Review; What Went Well; What to Improve; Discussion Notes; Action Items; Parking Lot; Metrics and Trends; Facilitator Notes; and Next Retrospective.\n\n## Quality Checklist\n\nBefore finalizing, verify:\n\n- [ ] All attendees had opportunity to contribute\n- [ ] Both positives and improvements are captured\n- [ ] Action items have owners and due dates\n- [ ] Previous retrospective actions are reviewed\n- [ ] A reader who missed the retro can tell what was decided and who owns each action from this document alone\n\n## Examples\n\nSee `references\u002FEXAMPLE.md` for a completed example.\n",{"name":5,"license":15,"metadata":24,"description":7},{"phase":25,"author":9,"updated":26,"version":27,"category":28,"frameworks":29},"iterate",1781049600000,"2.2.0","reflection",[30,31,32],"triple-diamond","lean-startup","design-thinking","main","9b920db418c5bf641edea9afb4915a286e1d42ea","skills\u002Fiterate-retrospective",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":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add product-on-purpose\u002Fpm-skills --skill iterate-retrospective",{"tool":47,"command":48},"bunx","bunx skills add product-on-purpose\u002Fpm-skills --skill iterate-retrospective",{"tool":50,"command":51},"pnpm","pnpm dlx skills add product-on-purpose\u002Fpm-skills --skill iterate-retrospective","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fiterate-retrospective\u002FSKILL.md",true,[55,61,65,69,73],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"evals\u002Foutput-scenarios\u002Fsprint-42.md","REFERENCE","参考文档",2091,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fiterate-retrospective\u002Fevals\u002Foutput-scenarios\u002Fsprint-42.md",{"path":62,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":63,"sourceHtmlUrl":64},"evals\u002Ftrigger-fixtures.json",4370,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fiterate-retrospective\u002Fevals\u002Ftrigger-fixtures.json",{"path":66,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":67,"sourceHtmlUrl":68},"HISTORY.md",1734,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fiterate-retrospective\u002FHISTORY.md",{"path":70,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002FEXAMPLE.md",8428,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fiterate-retrospective\u002Freferences\u002FEXAMPLE.md",{"path":74,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002FTEMPLATE.md",3754,"https:\u002F\u002Fgithub.com\u002Fproduct-on-purpose\u002Fpm-skills\u002Fblob\u002Fmain\u002Fskills\u002Fiterate-retrospective\u002Freferences\u002FTEMPLATE.md",[78,85,92,99,106,113],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"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":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"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",[],[]]