{"id":40998,"plugin_id":"plugin_asdk_app_6a53f7d79b5c81919a02e9814eb9f070","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T12:56:56.327Z","digest":"518b5f4359d5c68cfa80881ee8a0f6e47e02625fc0beeeed4960dc9a6a9e9c61","against":null,"payload":{"description":"Cross-references a changelog or upcoming release against the Supademo library and flags every demo a product change will touch — before it ships. Use in release planning so demo updates land with the launch, not weeks after.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":217}],"name":"product-change-mapper","skill_md_contents":"---\nname: product-change-mapper\ndescription: Cross-references a changelog or upcoming release against the Supademo library and flags every demo a product change will touch — before it ships. Use in release planning so demo updates land with the launch, not weeks after.\n---\n\n# Product Change Mapper\n\nThe release notes say \"redesigned settings page.\" This skill answers the question nobody asked in the launch meeting: which 9 demos show the old settings page?\n\n## Prerequisites\n\n- Supademo MCP connected\n- The change list: changelog, release notes, or a launch plan (works for shipped *and* upcoming changes)\n\n## Workflow\n\n1. **Decompose the changes.** For each item, note the affected surface (screen/flow), the change type (rename, redesign, move, remove, add), and whether it's shipped or upcoming.\n2. **Sweep the library.** `list_demos` with `list_folders`/`list_tags` to narrow by product area, then `get_demo` on candidates. Match on step copy mentioning the feature, chapter titles, and captures of the affected screens.\n3. **Build the impact matrix:**\n   | Change | Demo | Steps affected | Severity | When |\n   Severity: **breaking** (demo now shows wrong/missing UI), **cosmetic** (looks dated, still accurate), **copy-only** (terminology drift).\n4. **Sequence the work.** Breaking changes on high-traffic demos first (cross-reference `get_demo_analytics`). For upcoming changes, note the ship date so recaptures are scheduled for launch day, not discovered after.\n5. **Mark and hand off.** For authorized tagging, resolve or create the `impacted-{release}` tag ID using `list_tags`/`create_tags`, then apply `add_demo_tags` and pass the queue to `feature-launch-demo-updater` for execution.\n\n## Guardrails\n\n- For a mapping-only request, return the report without changing content; apply tracking tags only when requested. Keeping mapping separate from fixing means the impact report can go in the launch plan as-is.\n- For upcoming changes, never edit demos early — the live demo must match the live product until ship day. Suggest `duplicate_demo` to prep the updated version in parallel, swapping at launch.\n\n## Supademo tool conventions\n\nRead [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}