Playbook · prompt pattern
Stop pasting into ChatGPT blindly — use this prompt pattern
Raw notes into a chat window rarely give you something you can ship. A four-line frame — Role, Goal, Constraints, Output format — turns the same messy standup into a usable draft. Works in ChatGPT, Claude, and Gemini. Same pattern, any model.
The paste-and-hope problem
If you dump raw notes into a chat and hope, you’re leaving half the answer on the table.
Most people treat the model like a search box: paste the mess, hit send, skim whatever comes back. The reply is often polite fluff — a “general summary,” inventing structure you didn’t ask for, or inventing deadlines you never mentioned.
That isn’t a model failure. It’s a briefing failure. The model doesn’t know whether you want a weekly update, a checklist for owners, a rewrite for executives, or a brainstorm. Without constraints and a format, it guesses — and guessing produces text that looks finished but isn’t usable.
This playbook is the long-form companion to our short demo: same messy standup notes, framed once, so you get something you can actually hand off.
The 4-line frame
Four lines above your notes. That’s the whole pattern.
Who the model is
Give it a job title for this turn — “concise ops writing assistant,” “skeptical editor,” “meeting scrubber.” Role steers tone and what it prioritizes.
What you need done
One sentence on the outcome: turn notes into a weekly update draft, extract open questions, rewrite for a client email. Goal beats “help with this.”
Limits, tone, what to skip
Max length, no invented deadlines, neutral tone, skip unclear items. Constraints are where quality lives — they stop the model from filling gaps with fiction.
Shape of the answer
Markdown checklist, table, bullets with owners as [TBD], three paragraphs max. Format makes the reply paste-ready instead of “essay-shaped.”
ChatGPT is just the demo surface. The same four lines work in Claude and Gemini. Change the product; keep the briefing.
Copy-paste example
Generic standup notes only — no real names, emails, or company secrets. Paste the frame, then the notes, then send.
Messy notes (input)
standup notes — draft - follow up on the launch checklist - need tighter bullets for the weekly update - someone asked about the timeline?? unclear - also the FAQ page is messy
4-line prompt frame (paste above the notes)
Role: You are a concise ops writing assistant. Goal: Turn these standup notes into a usable weekly update draft. Constraints: Max 5 bullets. No invented deadlines. Neutral tone. Skip anything unclear. Output format: Markdown checklist with owners left as [TBD]. standup notes — draft - follow up on the launch checklist - need tighter bullets for the weekly update - someone asked about the timeline?? unclear - also the FAQ page is messy
Expect a short checklist: launch follow-up, weekly bullets, FAQ tidy-up — unclear timeline items omitted or flagged, owners as [TBD], no fake dates. That is “usable,” not “impressive.”
Before / after — what to expect
Qualitative only. No fake metrics, scores, or “X% better” claims.
Raw paste
- Vague “here’s a general summary…” opening
- Invented structure or deadlines you never said
- Essay-length fluff you have to rewrite
- Unclear items quietly “resolved” by the model
Framed paste
- Short checklist matching your format line
- Gaps left as [TBD] or skipped on purpose
- Tone and length match constraints
- Something you can paste into a doc and edit
You’re not buying magic. You’re buying a briefing habit: same notes, clearer job for the model, less cleanup for you.
One rule
Memorize this; the rest is optional polish.
When it fails
The frame is not a substitute for judgment. Watch for these.
- Vague goal. “Make this better” still leaves the model guessing. Name the artifact (weekly update, FAQ rewrite, open-question list).
- Constraints that fight each other. “Max 3 bullets” plus “cover every detail” forces compromise. Pick one priority.
- No human check on facts. The frame reduces invention; it doesn’t verify sources. Don’t publish claims you didn’t open yourself.
- Wrong job for chat. Recurring templates inside a workspace may belong in Notion (or similar) — use chat for blank-page thinking and one-off framing.
- Pasting secrets. Never drop real emails, API keys, or private customer data into a public model. Use generic stand-ins like the demo notes above.
Soft next steps
No payment. No checkout. Just the list and the channel when you want more.
Want the full prompt kit?
Join the waitlist for the expanded kit and the next workflow (notes → framed prompt → draft). Soft CTA only.
Also: About · Disclosures · Home.