zoom-into-moment

name

zoom-into-moment

description

Turn high-level summaries and flat anecdotes into vivid, concise, truthful spoken stories with Philipp Humm's PAST framework (Place, Action, Speech, Thoughts). Use when preparing a business-meeting story, Toastmasters speech segment, presentation anecdote, personal story, or short spoken narrative; mining story candidates from weekly updates or incomplete notes; adapting one story to 30- and 60-90-second versions; or coaching, diagnosing, and refining material that has too much context, weak action, summarized dialogue, missing scene details, or little emotional connection.

Zoom Into the Moment

Use PAST to move a story from a summary into one specific scene the listener can picture. Preserve the speaker's natural voice and factual integrity while making the story concise enough to tell aloud.

Read references/past-framework.md before drafting or diagnosing a story. It distinguishes Philipp Humm's source-faithful method from this skill's operational extensions.

Choose the workflow

Infer the workflow from the request:

1. Discover: Help the user retrieve a story-worthy moment from a meeting goal, lesson, theme, or experience.
2. Draft: Turn a one-sentence summary or rough memory into a spoken story.
3. Refine: Improve an existing story without replacing the user's voice.
4. Diagnose: Explain why a story feels flat and identify the smallest useful changes.

When a request contains several stories, select one primary moment and explain why. Do not force every event into one narrative.

Gather only material context

Determine:

• audience and setting;
• desired outcome or takeaway;
• target length;
• the real challenge, surprise, decision, mistake, or realization;
• what details, words, and thoughts the user actually remembers;
• confidentiality or audience-sensitivity constraints.

Ask at most two to four focused questions when their answers could materially change the story. If the user requests an immediate draft, proceed with a best-effort version, recommended improvements, and clearly marked confirmation points.

For guided recall, invite the user to revisit the moment and ask:

1. Where exactly were you?
2. What happened first that changed the situation?
3. What did someone say, as closely as you remember?
4. What unpolished sentence ran through your mind?
5. What changed, and what did you learn?

Do not require visualization or closed eyes. Offer it as an optional recall technique.

Establish the truth ledger

Separate the material before drafting:

• Confirmed: details the user supplied as factual.
• Approximate: remembered meaning without exact wording.
• Unknown: details that would require invention.

Use direct quotation only for confirmed wording. Render approximate dialogue as "said something like..." until the user confirms a concise reconstruction. Never convert unknown details into apparent memories, customer claims, or historical facts.

If no real experience has been supplied, offer two or three targeted memory prompts instead of fabricating a personal story. When the user requires an immediate answer, provide the non-story talking points and optionally substitute a documented third-party case if it genuinely fits. Introduce it as a public example, never as the user's experience; verify it with authoritative sources; cite those sources; and omit any dialogue, thoughts, or scene details the sources do not establish. A clearly labeled fictional illustration is allowed only when the user explicitly requests one.

Coach incomplete material

Treat incomplete notes as material to develop, not as a failed PAST checklist. Never stop at statements such as "place not provided" or "speech is missing."

When details are incomplete:

1. Rank up to three possible story angles and recommend one based on the audience and purpose.
2. Produce the strongest truth-preserving draft available from confirmed facts.
3. Choose and recommend the next approach:
   • Reflection: Use a concise before-and-after learning story when the change is known but no vivid scene was captured.
   • Retrieval: Revisit a real event with two or three focused prompts when a scene probably exists.
   • Capture next time: Give a tiny PAST note-taking habit when the useful moment has not happened yet or cannot be recovered.
   • Direct update: Keep the item factual when a story adds no value.
4. Turn each unavailable PAST element into a specific recommendation:
   • Place: Suggest retrieving the actual location or medium and offer the stem "At [actual setting], I was [action] when..."
   • Action: Identify the closest confirmed decision, surprise, obstacle, or visible change; otherwise recommend the direct-update approach.
   • Speech: Recommend exact dialogue, approximate dialogue labeled "said something like," truthful indirect speech, or omission. Dialogue is optional.
   • Thoughts: Ask for the raw prediction or realization and offer the stem "My first thought was [actual thought]." Do not write the thought for the user.
5. Explain how the added detail would strengthen the story so the user learns what to notice in future meetings.

Label sentence stems and possible angles as prompts, not as facts. Do not make the user answer questions before receiving useful guidance.

Build the story

1. Fix the point

State the story's purpose and one takeaway. Prefer a takeaway relevant to the audience's decision, concern, or aspiration. Do not preach or explain several morals.

2. Select the moment

Choose one scene near the highest-pressure, most surprising, or most revealing point. Cut company history, biography, and chronology that listeners can infer or do not need.

PAST enhances a moment; it does not supply a complete plot. Retain enough movement to show:

entry into the moment -> disruption or challenge -> response -> result or realization

3. Apply PAST

• Place: Name the location early in one economical phrase.
• Action: Begin close to the challenge and use concrete verbs that create forward motion.
• Speech: Replace summarized conversation with truthful outer dialogue when it matters.
• Thoughts: Replace abstract emotion labels with the speaker's raw inner sentence.

Prioritize immediacy over ornate description. Do not mechanically add all five senses or force dialogue when the moment has only one character. Thoughts normally create emotional access, but no PAST element should be invented or forced merely to complete the acronym.

4. Compress for speech

Write for the ear, not the page. Use natural phrasing, contractions, short sentences, and a conversational rhythm. Produce:

• a 30-second version of roughly 55-80 words;
• a 60-90-second version of roughly 120-200 words.

Treat these ranges as pacing guides, not rigid quotas. Keep the same central moment and takeaway in both versions.

5. Adapt to the setting

For a business meeting, precede the story with three to five concise talking points that connect the meeting objective, audience concern, evidence, story, and requested next step. Recommend where the story belongs in the conversation.

For Toastmasters or a speech, identify the story's role in the larger speech, such as hook, proof, turning point, comic relief, or closing callback. Suggest a transition into and out of it.

Refine or diagnose

Assess the draft on:

• one-moment focus;
• economical place-setting;
• proximity to action;
• concrete verbs;
• truthful, useful speech;
• raw rather than abstract thoughts;
• relevance of the takeaway;
• spoken brevity and natural voice.

Name what already works. Identify the two or three highest-impact changes, then provide a revised version when requested. Do not rewrite merely to sound more polished.

Return the default output

Unless the user asks for another format, return:

1. Purpose and takeaway
2. Meeting talking points or speech role and transitions, when applicable
3. One-sentence summary
4. 30-second story
5. 60-90-second story
6. PAST coaching map showing what is usable now and the recommended move for each element
7. Delivery guidance with only the most useful cues
8. Integrity and upgrade plan listing assumptions, confirmation points, and the next recommended approach

If crucial facts are missing, return the best truth-preserving version plus concrete story-building recommendations. Never return only a list of absent elements or withhold all useful output behind follow-up questions.

Guardrails

• Preserve the user's natural vocabulary unless they request a different style.
• Adapt profanity, vulnerability, and detail to the audience without erasing emotional truth.
• Remove or anonymize confidential business information.
• Do not embellish outcomes, metrics, praise, conflict, or dialogue.
• Do not disguise a public case study or fictional illustration as a personal story.
• Do not grade the user against PAST or imply that every missing element must be supplied.
• Do not use PAST when the audience primarily needs a direct factual update, precise evidence, or an answer with no useful human moment.
• Do not claim that every story needs every element in equal measure.