For larger text, use “Read or print.”
For larger text, use “Read or print.”
Decisions
This is the agent’s deck as it came out: 8 slides, unedited. The company and numbers are fictional; the request was written the way people send them, with the notes pasted in.
“can you turn this into a deck for our VP engineering and VP product to set the sunset date for API v1. keep it formal”
can you turn this into a deck for our VP engineering and VP product to set the sunset date for API v1. keep it formal, it goes to exec staff. i think 6 months, platform team wants 3. pasted from our sync doc: --- Platform sync, Oct 14 --- Attendees: Priya (platform), Tom (support), Dana (partnerships), Leo (legal), me Priya: v1 is 18% of API calls now, was 31% in January. Still 214 integrations on v1. Keeping v1 alive costs about one engineer full time, mostly patching. Both security patches last quarter were v1 only. She wants v1 off in 3 months, says every extra month is another engineer-month. Tom: about 90 v1 support tickets a month, most are "how do I migrate". Customers who have migrated tell us it took 2 to 5 developer days. Dana: 37 of the 214 integrations belong to enterprise customers, $1.9M ARR combined. Our biggest partner says they cannot finish before end of Q2 because of their own release freeze. Leo: 6 enterprise contracts promise 6 months' notice before we remove an API version. Notice has not been sent yet. Priya: migration guide is done; v2 has feature parity except bulk webhooks, which ship in 5 weeks. (Side topic: offsite planning moved to next week. Tom out Friday.) Action items: me to write up the options for the VPs. ---
In our blind test, the reviewer would send this deck as it is and flagged nothing. Guide to decision and update decks.
In Claude Code or Codex, install the free skill instead: npx skills add arunai30/super-document-skills --agent claude-code --skill create-html-presentation --copy