Detected promise
Claude “Fable 5” Mission-First Prompting Guide (FR-style templates, in English) + Copy/Paste Templates + Memory Markdown System
Reconstructed contract
It directly to you
Here’s the complete “comment FABLE and I’ll DM you” guide—delivered upfront. It includes: (1) a mission-first prompt structure that replaces mega-prompts, (2) TES checkpoints to keep long tasks safe and on-rails, (3) a lightweight memory system using Markdown files, and (4) a ready-to-copy template pack for common business tasks (strategy, writing, analysis, agent workflows). It’s written to be usable even if the exact “Fable 5 manual” wording differs—because the underlying method (context + intent + checkpoints + memory) is model-agnostic.
Resource without ritual
The promised resource, no comment required
1) The mental model: stop prompting like a manager, start briefing like a client
The shift this post describes is real in spirit even if the naming/hype varies by model version: longer prompts often create conflicting constraints and reduce autonomy. Your goal is to provide:
A) Mission (what success means)
B) Why (the value / stakes)
C) Constraints (real constraints only)
D) Checkpoints (when to stop/ask)
E) Memory (what to remember next time)
Rule of thumb:
If a rule is not verifiable or not business-critical, remove it.
If you feel you must add 15 rules, you probably need 1) a better mission statement or 2) an output spec + examples.
Practical rewrite:
Bad: “Follow these 27 rules, never do X, always do Y, format exactly like…”
Better: “I’m shipping [deliverable] to [audience] by [date]. It must achieve [metric]. Draft it. Ask only if you need info that changes decisions.”
2) The “WHY > WHAT” optimal briefing structure (copy/paste)
Use this as your default wrapper. Keep it short; let the model plan.
MASTER BRIEF (Mission-First)
Context
I am working on: [global project]
For: [audience/customer/user]
They need: [expected result / job-to-be-done]
Why it matters: [impact, risks, stakes]
Definition of done: [what a good answer includes + acceptance criteria]
Request
With that in mind: [your request in 1–3 sentences]
Constraints (only real ones)
Must: [hard constraints]
Must not: [hard constraints]
Preferences: [soft preferences]
Inputs I’m providing
[links, pasted docs, data, examples]
Output format
[bullets/table/JSON/email/etc.]
Start by stating your plan in 3–7 bullets, then execute.
Why this works:
Context replaces repeated back-and-forth.
“Definition of done” prevents the model from over-optimizing for verbosity.
“Plan then execute” makes long tasks more controllable.
3) TES checkpoints: the “don’t interrupt me unless…” safety rail
For long or autonomous tasks, add a TES checkpoint clause.
TES = Terminate / Escalate / Seek
Terminate: When the task is complete or you reach a stop condition.
Escalate: When there’s an irreversible action or decision risk.
Seek: When only the human can provide missing info.
COPY/PASTE TES CLAUSE
“Interrupt me only for:
1) an irreversible action,
2) a change of scope or assumptions,
3) information that only I can provide.
Otherwise, keep going until you meet the definition of done.”
Add explicit stop conditions to avoid ‘infinite helpfulness’:
“Stop after producing: (a) final deliverable, (b) a 5-bullet rationale, (c) a next-steps checklist.”
“If there are multiple options, present up to 3, pick 1 recommendation, and stop.”
For business-critical work, add risk gates:
“If you’re uncertain about a factual claim, label it as uncertain and propose how to verify.”
“Do not fabricate citations or policies.”
4) The Memory system: simple Markdown that actually improves reuse
You don’t need a fancy vector DB to get benefits from “memory.” You need:
A consistent format
One lesson per file
A 1-line summary at the top for scanning
FOLDER STRUCTURE
/memory
/lessons
/profiles
/projects
/snippets
A) Lesson file template (one lesson per file)
File: memory/lessons/2026-07-03__stakeholder-tone.md
Summary: Use a confident, non-hype tone; avoid absolute claims; always include acceptance criteria.
Context
Where it happened:
What we were trying to do:
What worked
-
What didn’t
-
Decision / rule for next time
-
B) User/brand profile template
File: memory/profiles/brand-voice.md
Summary: Direct, practical, no fluff; prefer tables; avoid buzzwords.
Voice principles
-
Forbidden phrases
-
Formatting defaults
-
C) Project memory template
File: memory/projects/project-x.md
Summary: Project X aims to ship [deliverable] by [date] to [audience] with [success metric].
Goals
-
Constraints
-
Known decisions
-
Open questions
-
How to use memory in a new session
Paste only the relevant summaries + 1–2 key sections. Don’t dump the entire folder every time.
PROMPT SNIPPET
“I will paste short memory notes. Use them as preferences and constraints. If any conflict with my current request, ask.”
5) Prompt migration: why “old prompts” can backfire and how to refactor
Common failure mode: legacy prompts contain brittle micromanagement (tone rules, banned words, forced steps) that conflicts with the model’s planning.
Refactor method (5 minutes):
1) Delete rules that aren’t acceptance criteria.
2) Replace process micromanagement with output spec.
3) Turn “always/never” rules into testable checks.
4) Move style to a short “Voice” block.
5) Add TES clause + stop condition.
Example refactor
Old: “You are an expert. Follow these 18 steps. Don’t ask questions. Use the PAS framework. Make it witty but formal. Use no more than 3 commas per sentence…”
New:
Context: I’m selling X to Y. They care about Z.
Definition of done: 1 LinkedIn post (120–180 words), 3 hook options, 1 CTA, matches voice notes.
Request: Write the post.
TES: Interrupt only for scope/irreversible/missing human info.
Stop: After final post + 3 hooks + CTA.
If you truly need multi-step rigor, ask for:
“Draft an outline first, then wait.” (human-in-the-loop)
“Create a checklist of assumptions, then proceed.”
6) Ready-to-copy templates (the “guide in French” vibe, but usable now)
Template 1 — Senior-consultant mission brief
Context
I am working on: [project]
For: [audience]
They need: [outcome]
Why it matters: [stakes]
Definition of done: [deliverable + quality bar]
With that in mind: Act as a senior consultant. Produce [deliverable].
Constraints
Must:
Must not:
TES checkpoints
Interrupt me only for irreversible actions, scope changes, or info only I can provide. Otherwise keep going.
Stop condition
Stop after delivering the final output + a short rationale + next steps.
--
Template 2 — Strategy options + recommendation
Context: [market/product]
Goal: [metric]
Audience: [ICP]
Constraints: [budget/time/legal]
Request: Provide 3 viable strategies. For each: assumptions, pros/cons, risks, and required effort. Then recommend 1 with a 30-day plan.
Output: Table + 30-day plan bullets.
TES + Stop: [paste TES clause]
--
Template 3 — Sales email sequence (B2B)
Context: We sell [product] to [ICP]. The key pain is [pain]. Proof: [case study].
Definition of done: 5-email sequence, each <120 words, includes subject lines, personalization token, and one clear CTA.
Request: Write the sequence. Keep tone: direct, helpful, non-hype.
--
Template 4 — Meeting prep: agenda + questions that matter
Context: Meeting with [role/company]. Objective: [objective].
What I know: [bullets]
What I need: [bullets]
Request: Create a 30-min agenda, 10 discovery questions, 5 red flags, and a decision checklist.
--
Template 5 — Doc-to-decision summary (exec brief)
Input: [paste doc]
Request: Summarize for an executive: 10-bullet key points, decisions needed, risks, and recommended next step. If data is missing, list questions.
Output: Headings + bullets.
--
Template 6 — Build an “agent” runbook (no code)
Context: I want a repeatable workflow for: [task]. Users: [who]. Frequency: [daily/weekly].
Definition of done: A runbook with triggers, inputs, steps, QA checks, escalation rules, and a handoff message.
Request: Design the runbook. Include:
Trigger
Required inputs
Step-by-step procedure
QA checklist
TES escalation rules
Templates/snippets
--
Template 7 — QA/critique pass (make outputs better)
Context: Here is a draft: [paste]
Definition of done: Improve clarity and accuracy without changing meaning.
Request: Critique in 3 parts: (1) issues, (2) proposed edits, (3) final revised version. Flag uncertain claims.
--
Template 8 — “Memory update” after a session
Request: Based on what we learned, write 1 memory lesson file using this structure:
Summary: (one line)
Context:
What worked:
What didn’t:
Decision/rule for next time:
Keep it short and specific.
7) One-page LinkedIn-friendly infographic content (so you can recreate the visual)
If you want a single-slide graphic, here’s the exact copy to place on it:
TITLE: Mission-First Prompting (Why > What) + TES Checkpoints + Memory
1) Stop over-prompting
Short mission beats 2-page rules
Prefer acceptance criteria over micromanagement
2) Give the WHY
“I’m working on [project] for [audience].
They need [outcome].
Why it matters: [stakes].
With that in mind: [request].”
3) TES checkpoints
“Interrupt only for:
Irreversible action
Scope change
Info only I can provide
Otherwise keep going.”
4) Lightweight memory
One lesson per file
1-line summary at top
Reuse only relevant summaries
5) Migrate old prompts
Delete brittle rules
Add definition of done
Add stop condition
FOOTER: Copy/paste templates + memory file formats inside this guide.