1.3 Your first three tasks — Antigravity for PMs

Do these in order. They are deliberately small, and each one teaches one habit.

Task one — make it write in your voice

Take something you wrote and shipped. Put it in shipped/. Then:

Read @shipped/last-update.md. Describe the writing style in six bullet points: sentence length, how it opens, how it delivers bad news, what it never does. Do not praise it.

Read the six bullets. They will be about seventy per cent right, and the wrong thirty per cent is the interesting part — it is what your writing looks like from outside. Correct them and save the result as context/voice.md. You now have a file you can attach any time you want something to sound like you rather than like a press release.

The habit

Ask it to observe before you ask it to produce. An observation you can correct is worth more than a draft you have to rewrite.

Task two — make it stay inside the evidence

Put a real transcript, support export or survey dump in research/. Then:

Read @research/interviews-march.md. List every distinct complaint, with the exact quote it came from. If a theme appears once, say so. Do not group things that are not the same thing.

Then check three quotes against the file. Not one — three. The failure mode you are looking for is a quote that is almost in the transcript: paraphrased, tightened, attributed to the wrong person. It is the single most expensive failure in PM use of these tools, because a tightened quote is exactly what gets pasted into a deck.

The habit

Demand quotes, then spot-check them. Every time, for the first month.

Task three — make it disagree with you

Write two sentences of a position you hold about your product. Then:

Here is my position: [paste]. Using only @context/company.md and @research/interviews-march.md, give me the strongest case against it. If the evidence does not support a case against it, say that instead of inventing one.

The second sentence is what makes this work. Without it you get manufactured disagreement, which is worse than agreement because it sounds like rigour.

The habit

Give it permission to find nothing. Models default to producing what you asked for, and an explicit escape hatch is the cheapest way to tell the difference between a real objection and a generated one.

If task two went badly

Invented quotes usually mean the file was too long for the context available, and the agent summarised rather than read. Split the file, or ask about one section at a time. It does not mean the tool is useless; it means you asked it to read more than it read.