Draft launch content, changelogs and demos grounded in what shipped.
Start from what merged, so messaging matches the product.
Read the pull requests merged since <date or tag> that touch <area>. Write a launch brief with the audience, the problem, three messaging pillars with proof points linked to the PRs, and anything that is not ready to talk about yet.
Outcome: A brief where every claim links to the change that backs it.
Moves:Time to first draft
Write with the agent reading the code instead of guessing at it.
Draft an 800-word blog post announcing <feature> for <audience>. Base every technical statement on the code and docs in this repository. Include a short getting-started snippet that you have run. Outline first and wait for my approval.
Outcome: An outline you approve, then a draft with a tested code sample.
Moves:Time to first draft
Create a PowerPoint deck in a canvas from the approved brief.
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.
Create a PowerPoint deck from the launch brief above: title slide, problem, three pillar slides with proof points, a demo slide and a call to action. Keep text to three bullets per slide and add speaker notes.
Outcome: A first-draft deck you refine slide by slide.
Moves:Time to first draft
Edit marketing pages on a branch and review the rendered result.
Update the copy on <page> to match this message: <message>. Keep the existing layout and components. Start the dev server and open the page so I can review the change before you commit.
Outcome: A previewed copy change on its own branch, ready for review.
Moves:PR cycle time
Get a small, reliable sample app for a video or live demo.
Cloud sandbox: Cloud sandboxes are in public preview, and an admin may need to enable them for your organization or enterprise.
Create a minimal demo app in a new folder that shows <feature> in under two minutes of screen time. Seed realistic sample data, make the happy path work end to end, and write a numbered demo script in DEMO.md.
Outcome: A runnable demo and a script to record from.
Moves:Time to prototype
An automation drafts customer-facing changelog entries every week.
Draft changelog entries for pull requests merged in the last 7 days that change user-facing behavior. Write one or two sentences each in plain language and link the PR. Skip internal and test-only changes.
Outcome: A changelog draft waiting for you each Monday.
Moves:Toil hours