Translating product intent into written tickets is where detail gets lost. Engineers get ambiguity; you get "what did you mean by this?" in standup.
How it works
Record the walkthrough
Demonstrate the change or request and explain the why.
It becomes requirements
Read by a coding agent, each ask becomes a numbered requirement tied to the moment you said it.
Task lands with the team
A GitHub issue opens with the video linked, through the GitHub integration, your dispatcher or a coding agent.
- Hand off intent with the video, not just words
- Fewer "what did you mean by this?" questions
- Watch the work move stage by stage on Agent Workstreams
How screen recording for product managers works with a coding agent team
Record the walkthrough
Open the screen you want changed and talk through it as you would in a meeting: what is there now, what should change and why. With the Chrome extension you can circle a button, cross out a banner or write the new copy by hand. Each mark is saved with the sentence you were saying, so nobody has to guess which button you meant.
No extension? Press New Recording in Vidmatic and pick a screen or window. There is no pen in that mode, so say out loud which element you mean and pause on it.
Three ways it becomes an issue
With GitHub connected and Auto-create GitHub issue on, Vidmatic opens the issue in your default repository when you stop, with your default labels and assignees, a share link to the video and, if you chose it, the full transcription. No agent is involved.
If your asks span several repos, choose Add to Agent Workstreams instead. Your dispatcher files each request in the repo it belongs to and asks you only when it cannot tell.
If you or an engineer use Claude Code, Give to your agent copies one prompt. The agent files one issue with a row per ask: the time, the mark, your words and the files it found.
When a written ticket lost detail
If an issue already exists and links a recording, an engineer can run /mcp__vidmatic__issue_intel with the issue URL. Their agent reads the recording and posts every ask as a comment, so what the write-up dropped is back on the ticket.
Watch it ship
Agent Workstreams shows each issue as a card with a box per stage, such as plan, build, review and ship. When the issue ships, the card shows the pull request and the demo video, and the demo lands in the Inbox of the account that ran the agent. A card marked Stalled has had no report from the agent for an hour.
Questions
- Do I need to use Claude Code myself?
- No. The GitHub integration opens the issue when you stop recording, with no agent involved.
- Can engineers watch the recording from the issue?
- Yes. The issue links to the recording with a share link, so anyone who can read the issue can watch it.
- Can I write a request without recording?
- Yes. Choose New request at the top of Agent Workstreams, write what should change and choose Add to Agent Workstreams.
- Can the new user path be shown as a video?
- Yes. An engineer can run /mcp__vidmatic__demo_user_journey, which records a narrated demo of the shortest path a new user takes to a first win.
- Where do I see progress?
- On Agent Workstreams, in the app sidebar. Each issue is a card with a box per stage, and the record of each stage is what the agent reported.
Related use cases
- Create a Ticket From a Video
Create a ticket from a video. Record your screen, add it to Agent Workstreams, and your dispatcher files a GitHub issue in the right repo.
- Generate a Demo Video
Finish a feature in Claude Code and let it record, narrate and publish the demo. Vidmatic drives your running app, adds a voice-over and returns a share link.
- Screen Recording to GitHub Issue
Turn a screen recording into a GitHub issue your agent can build: numbered requirements tied to the moment you said them, grounded in your code.
Stop Writing Tasks Manually
Record once. Vidmatic handles the documentation.
Explore more Vidmatic use cases
Docs: Agent Workstreams