The only prompt pattern you need first: Goal · Format · Boundaries
Goal: Replace vague asks with a daily GFB trio until “say it clearly” becomes a reflex.
Best for: Anyone whose chats start with “help me with this” and then spiral.
GFB is the house pattern on iswarp. Goal says what done looks like. Format says the shape. Boundaries say what must never happen (and when to ask you). Everything else—roles, rubrics, negatives—hangs off this skeleton.
Why beginners skip this
Dropping only a goal with no format or boundaries lets the model freestyle into unusable output. Write the three-pack once.
Step 1 — The template
Copy the GFB blank card below and fill it with today’s messiest real ask.
Goal: [what “done” looks like in one sentence]
Format: [bullets / table / email / length]
Boundaries: [must include / must avoid / ask me if unsure]
Input: [paste or attach]
Say the words out loud once. If you cannot fill Goal, you are not ready to chat—you are still clarifying the task.
Step 2 — Weak vs strong
Example
Filled prompt
Weak: Help me with this email.
Strong:
Goal: Reply to a customer who waited 4 days; keep the relationship.
Format: 120–150 words, 3 short paragraphs.
Boundaries: No blame on the customer; offer one clear next step; do not invent compensation amounts; no “Absolutely!” opener.
Input: [their email + my note: I can offer a Tue 15:00 HKT call]
What good output looks like
- Tone stays calm without fake discounts
- One next step you can actually keep
- Length lands near the ask
- You could hand it to a teammate without rewriting the facts
Step 3 — Save and reuse
Pin the empty GFB block in notes, or paste it into Project instructions as “Replace vague asks with a three-part template you” Version it when you add a new permanent Boundary (see prompt templates you can version).
Restate my Goal, Format, and Boundaries in three lines before you answer. If anything conflicts, ask me—do not guess.
Example
Filled prompt
Apply GFB to these messy notes. No invented facts. Return: (1) a filled GFB block I can reuse (2) the draft artifact (3) three self-checks I should run before send.
Notes:
---
Need a Friday all-hands blurb about the search redesign. Ship is internal-only. Do not promise mobile yet. Keep under 90 words. Audience: whole company, not just eng.
---
What good output looks like
- GFB block filled from the notes (internal-only, no mobile promise)
- Draft ≤90 words, company-wide tone
- Self-checks include “did I invent a mobile date?”
Close the loop
Write one line: next time I run with format or boundaries missing, I refuse.
Example
Filled prompt
I keep getting vague replies to "fix my email."
Rewrite as GFB for this job: Goal=ask manager to move 1:1 from Thu to Fri 15:00 HKT; Format=6 lines max; Boundaries=no guilt language, no inventing her calendar.
Return the GFB prompt only.
What good output looks like
- Goal/Format/Boundaries all present for “Replace vague asks with a three-part template you ”
- One example beats stacked IMPORTANT words
- Version/date kept when template changes
- Pass/fail: zero clarifying turns on live task
Example
Filled prompt
Fuzzy ask: "help with the deck."
GFB: Goal=trim deck to 6 slides for eng review; Format=slide titles only; Boundaries=no new metrics.
Return GFB only.
What good output looks like
- One example beats stacked IMPORTANT words
- Version/date kept when template changes
- Pass/fail: zero clarifying turns on live task
- Goal/Format/Boundaries all present for “Replace vague asks with a three-part template you ”
Red flag
“Just handle it” with no three-line GFB; unknowns unmarked—rewrite before run.
Save this card
Card: If goal · format · boundaries will not fit three lines, you are not ready for “just handle it.”. Keep this beside the tool; read before you start.
Before you start
Keep the last failing output visible. You will repair the prompt for “Replace vague asks with a three-part template” against that failure—not a fresh toy ask. Guide: prompt-goal-format-boundaries. Keep the real job visible the whole time; a blank box means stop and fetch the artifact first.
How to use this week
This week for a real task write goal / format / boundaries in three lines; fill any missing line before run.
Close the week by quoting aloud the refuse line you actually used once. If you cannot, rerun Practice now and date the pass/fail (Asia/Shanghai).
Pitfalls
| Pitfall | Fix |
|---|---|
| Goal that is just “write better” | Name the reader + done state |
| Format missing length | Add word/section caps |
| Boundaries that are only vibes | Ban concrete phrases and inventions |
| Skipping Input | Paste the raw material |
Field note: if the ask will not fit three lines (goal · format · boundaries), you are not ready for “just handle it.” Save the working trio with today’s date.
Practice now
Echo request: ask model to restate G/F/B before answering (Asia/Shanghai).
Boundary pair: one allowed example + one refused example (Asia/Shanghai).
Boundary example: one allowed + one disallowed output sample (Asia/Shanghai).
GFB-live drill: Goal/Format/Boundaries as three labeled lines before body (Asia/Shanghai).
GFB drill: write Goal / Format / Boundaries as three labeled lines before the ask body (Asia/Shanghai).
Thin-spot drill: rewrite the Save card with real nouns from your work (repo, doc, inbox). Generic placeholders fail the drill.
Tonight for a real task write goal / format / boundaries in three lines; fill any missing line before run.
Reality check: after Practice now, write one sentence you will refuse next time—and keep it on the Save card dated Asia/Shanghai.
Today card (copy) — prompt-goal-format-boundaries: 1. Artifact I will produce: ___ 2. Pass/fail check: ___ 3. Refuse-line if tempted to skip verify/send: ___ (date: Asia/Shanghai) 4. One never-do from this guide: ___
Extra pass: do the card on a real file today—reading alone does not count.
One sentence takeaway
Goal / format / boundaries three lines once; fill any missing line.
Next
Few-shot · Negative constraints · Copy-paste packs · Beginner mistakes
你最先需要的提示词模式:目标 · 格式 · 边界
目标: 用每天都能复用的三件套,换掉含糊提问:直到「说清楚」变成反射。
适合: 聊天总以「帮我弄一下」开头,然后越聊越散的人。
GFB 是 iswarp 的家规写法。目标写清怎样才算做完;格式写清外形(篇幅、段落、表);边界写清绝不能发生什么,以及什么时候该来问你。角色、评分表、反向约束,都挂在这副骨架上。
为什么新手跳过
只丢目标不写格式与边界,模型会自由发挥到用不了。三件套一次写清。
步骤 1——模板
抄下面这张 GFB 空卡,用你今天最含糊的一次真实请求来填。
目标:[一句话说清「完成」长什么样]
格式:[要点 / 表格 / 邮件 / 长度]
边界:[必须包含 / 必须避免 / 不确定就问我]
输入:[粘贴或附件]
大声说一遍。如果你填不出目标,你还没准备好聊天:你还在澄清任务。
步骤 2——弱 vs 强
实例
填好的提示词
弱:「帮我弄这封邮件。」
强:
目标:回复已经等了 4 天的客户,并保住关系。
格式:120–150 词,三段短段落。
边界:不指责客户;给出一个明确下一步;不编造赔付金额;不要用 “Absolutely!” 开场。
输入:[客户来信 + 我的备注:可约周二 15:00 香港时间通话]
像样的输出大概长这样
- 语气冷静,没有假折扣或瞎编赔付
- 下一步是你真能兑现的(周二 15:00 香港时间通话)
- 长度落在 120–150 词,三段短段落
- 事实冻结后几乎不用再改就能交给同事
- 开场不像 Absolutely! 啦啦队
步骤 3——存起来复用
把空的 GFB 模板钉在笔记里,或贴进 Project 说明当「默认提问形状」。每加一条永久边界,就升一个版本。
先用三行复述我的目标、格式、边界,再回答。如果有冲突,问我:不要猜。
实例
填好的提示词
用 GFB 处理这些乱笔记。不编造事实。返回:(1) 我可复用的填好的 GFB 块 (2) 草稿成品 (3) 发送前我该做的三条自检。
笔记:
---
周五全员会要一段搜索改版说明。仅内部上线。先别承诺移动端。90 词以内。读者:全公司,不只是工程。
---
像样的输出大概长这样
- GFB 块从笔记填出:仅内部、不承诺移动端、≤90 词
- 草稿用全公司能懂的语气,不堆工程黑话
- 自检含「有没有编造移动端日期?」
- 产物分三块:(1) 可复用 GFB (2) 草稿 (3) 发送前自检
- 不把内部上线说成对外发布
闭环
写下一行:下次缺格式或边界就开跑,我拒绝。
红旗
只丢目标不写格式与边界,输出会自由发挥到用不了;三件套一次写清。
保存这张卡
记下:今天改管用的那条提示词(含边界)+ 版本或日期。
开始前
开聊前在三条便利贴上写目标、格式、边界。如果跳过边界,你是在碰运气,不是在提示。
本周怎么用
本周对一个真任务写目标/格式/边界三行,缺一行就补齐再跑。
常见坑
| 坑 | 改法 |
|---|---|
| 「帮我弄一下」开场 | 先填目标·格式·边界 |
| 边界写在最后才提 | 边界与目标同屏出现 |
| 格式只说「好看点」 | 写清篇幅、段落、列表或表格 |
现在就练一次
今晚就练:对一个真任务写目标/格式/边界三行,缺一行就补齐再跑。
一句话带走
目标/格式/边界三行一次写清;缺一行就补齐。
下一步
← Back to home · Learn · Tools · Compare · Start