← SupademoCONTENT HISTORY

Update to Supademo

Snapshot Oct 24, 2026 · 12:56 UTC · version 2.0.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save Supademo and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Converts an engineering ticket, PRD, or changelog entry into a first-draft Supademo demo script — the click path to capture, per-step copy, and chapter breaks. Use when a feature ships and marketing needs its demo yesterday.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 217
    }
  ],
  "name": "ticket-to-demo-script",
  "skill_md_contents": "---\nname: ticket-to-demo-script\ndescription: Converts an engineering ticket, PRD, or changelog entry into a first-draft Supademo demo script — the click path to capture, per-step copy, and chapter breaks. Use when a feature ships and marketing needs its demo yesterday.\n---\n\n# Ticket to Demo Script\n\nFrom \"PROJ-142: Implement bulk CSV export\" to a capture-ready demo script in one pass.\n\n## Prerequisites\n\n- Supademo MCP connected (for the build step; scripting works standalone)\n- The ticket/PRD text — pasted, or pulled via a connected issue tracker\n\n## Workflow\n\n1. **Extract the user-facing story.** From the ticket, answer: Who asked for this? What could they not do before? What's the happy path? Ignore implementation details — the demo shows outcomes, not architecture.\n2. **Draft the capture plan.** The exact click path to record, screen by screen:\n   ```\n   1. Dashboard → the entry point (establishes context)\n   2. Click {feature entry} → the moment of discovery\n   3–5. The core flow, one decision per step\n   6. The result screen → proof it worked\n   7. CTA\n   ```\n   Flag any screen needing seeded data (\"account must have 3+ projects for this to look real\").\n3. **Write per-step copy.** Annotation (≤25 words, labels the action) and optional voiceover line (spoken register) for each step. Lead step 1 with the outcome, not the feature name.\n4. **Suggest structure.** Chapter breaks if 10+ steps; where the CTA lands; tags to apply.\n5. **Hand off for capture.** A human records the flow in Supademo.\n6. **Build after capture.** Once steps exist, apply the script with `update_steps`. Create new chapter steps with `create_steps` using `type: \"chapter\"`, `chapterType: \"Link\"`, the title in `chapter.heading`, and the planned 1-based `position`; use `update_chapters` only to edit existing chapter step IDs. Apply hotspot CTAs with `update_hotspots` and optionally `generate_voiceovers`.\n\n## Guardrails\n\n- If the ticket is ambiguous about user-facing behavior, list the assumptions at the top of the script rather than guessing silently.\n- Check `list_demos` first — the feature may already have a demo to update instead (see `feature-launch-demo-updater`).\n\n## Supademo tool conventions\n\nRead [the tool conventions](../supademo-onboarding/references/tool-use.md) before calling Supademo tools for this workflow.\n"
}

SHA-256 of public snapshot: 1c85f8494f1d4857f6dd3173dfe6f10dda1dd2e23a515302798eeab404a45927