Captures post-release learnings and decides whether product assumptions need revision.
npx skills add https://github.com/rombel00/game-processes --skill retro-rombel00
Please help me install this Agent Skill. Skill: retro Source: https://github.com/rombel00/game-processes/tree/main/plugins/product-definition/skills/retro Command: npx skills add https://github.com/rombel00/game-processes --skill retro-rombel00
High-intent search queries and answers about installing and using this skill.
Gather the task_spec acceptance criteria and the test_report from live verification, then record what was promised versus what was observed. Separate facts from interpretations, audit each upstream document for changed assumptions, and append a dated entry to the learnings artifact.
A fact is a direct observation, such as "3 of 10 users did not pass onboarding step 2." An interpretation is a hypothesis like "the onboarding is too long." Record both separately so interpretations are treated as inputs for the next cycle, not settled conclusions.
Yes. When the work went straight from brief to code, use direct observation as the fact source: how the result felt in use, what surprised you, and whether it matches the brief. This is the cheapest and often most useful retro.
Add a line to the Open Questions section of status.md noting that brief was proposed for update and listing which downstream documents (story_map, open task_specs) have not been revised. The orchestrator does not detect staleness, so this manual flag is the only signal.
When any assumption audit answers yes: the problem or user turned out different, the riskiest lean canvas assumption failed, the competitive picture changed, the roadmap order no longer makes sense, or a playtest disproved a readiness criterion. One yes is a trigger, not a minor edit.
kwanpham2195Define observable acceptance criteria and success contracts for ambiguous feature requests.
GP-SoftwareDivisionCoordinates a 6-phase product discovery process from framing to validation.
krazyuniksManage software development epics through a defined pipeline with status checks and HTML reports.
tarunccetDefine precise metric specifications with formulas, SQL, and ownership.
