Reproduce the bug in the linked issue. Follow the reported steps, then try likely variations. If you reproduce it, write a minimal failing test and stop. If you cannot, list what you tried and the information to ask the reporter for.
Outcome: A failing test or a precise follow-up question for the reporter.
Create a sample in <language> that shows how to <task> with our SDK. Keep it under 60 lines, add comments only where the API is surprising, run it against the test environment and add a README with setup steps.
Outcome: A runnable, tested sample with setup instructions.
Write a developer blog post about <topic> for <audience>. Build the sample first in a samples/<slug> folder and run it. Pull every code snippet in the post from that sample, so nothing is untested. Include prerequisites, the steps, the expected output and a "what to try next" section. Keep it under 1,200 words.
Outcome: A draft post and a runnable sample that back each other up.
Read the release notes for <version>. Create three child sessions that run at the same time. (1) Build and run a sample in samples/<slug> that shows the headline feature. (2) Draft a blog post that pulls every snippet from that sample once it passes. (3) Write a five-post social thread with alt text for any images. Open one pull request for the sample and the post, and put the thread in a Markdown file for me to review.
Outcome: A tested sample, a post and a social thread for one release, ready for review together.
Plan a 90-second video that shows <feature>. First write the script with timings and a shot-by-shot storyboard, and wait for my approval. Then build it as a Remotion project in videos/<slug>: title card, screen captures I provide in assets/, captions from the script and an end card. Render it to MP4 and use ffmpeg to make a 30-second cut for social.
Outcome: An approved script, a storyboard and rendered MP4 files you can regenerate when the product changes.
Turn a week of posts and replies into themes, sentiment and follow-ups.
ChatsOffice canvases: Availability variesMy work
Office canvases: The Word, Excel and PowerPoint canvases may not be on for your account yet. If they are not in the Canvas view in Customize, ask the agent to write the .docx, .xlsx or .pptx file with a script and open it in Office.
Open the attached export of social posts that mention <product> from the last 7 days. Remove usernames. Group posts into themes with a count, overall sentiment and two representative quotes each. Flag bug reports and link any that match an existing issue. Draft a reply for the three posts that most need one, for me to review and post myself.
Outcome: A weekly social digest, matched issues and draft replies that a person posts.
Compare the docs page <path> with the current implementation. List every place where the docs are wrong, missing or out of date. Then update the page, and preview it if the docs site has a dev server.
Outcome: A docs fix grounded in the code, with a preview.
A scheduled automation reads a chat channel and error data, then files deduplicated issues.
AutomationsConnectors: Availability varies
Connectors: Connectors may not be on for your account yet. If they are not in the Customize view, add the service as an MCP server where your admin allows it, or attach an export.
Read the last 24 hours of <Slack or Teams channel> and recent errors from <error tracker>. Group reports that describe the same problem, link each group to an existing issue or open a new one with steps and quotes, and post a short summary of what you filed.
Outcome: A clean issue backlog that reflects what users report.
Summarize the support and discussion threads from the last 7 days. List the top five questions by volume with links, the docs or product change that would remove each one, and any quotes worth sharing with customer details removed.
Outcome: A weekly digest the product team can act on.
