Flink Project Story Post

---
name: flink-project-story-post
description: Writes a Project Story Post from one real moment in your client work, with the first line inside the moment, what you did in two lines and an ending that is a plain fact. Use for "run flink-project-story-post", "write a post about this project", "show the work we did for a client", "turn this engagement into a post", "nobody knows about this project", "a case post for LinkedIn", "post about a win without bragging", part of the Claude Playbook for Authentic LinkedIn Presence Pack by Polar Bear.
---

# Project Story Post

## When To Use
You did good work for a client and nobody outside the room knows. You want one post that shows how you work, without a press release voice and without saying anything the client has not agreed to.

## When Not To Use
If the interesting part is what went wrong and what you changed, run Lesson Learned Post instead. If you have no permission to describe the work at all, even anonymised, run Opinion Post on the idea behind it.

## Inputs
- Your notes or a call transcript on the project, the moment you remember most, and two of your own past posts or your Personal Voice Guide
- The Claim and Permission Check for this project, if you have one: which numbers you can defend, whether the client agreed to be named or quoted on LinkedIn
If you have none of this, I start from five minutes of you telling me the moment out loud and mark the output as a first draft.

## Approach
One moment, told with a compressed story spine (Kenn Adams, via NPR, 23 June 2026): every day, but one day, because of that, until finally, ever since then. A post that summarises the whole project reads like a report and gets skipped; a post that opens inside one Tuesday afternoon gets read. The spine is a check, not a voice: if every post you write runs on it, readers hear the formula, so the shape stays under your own sentences. Most of these posts die on the first line, "Proud to share", because the reader has seen it too often to read on.

## Workflow
1. I ask three questions: which one moment from the project (the sentence the client said, the screen everyone stared at, the week it nearly failed); has the client agreed to be named or quoted on LinkedIn, which is a different permission from a website; is there a number you can defend, with its source.
2. I lay the moment on the spine in your words: the normal (every day), what broke (one day), what you did in two lines (because of that), what changed (until finally), and the plain fact it left behind (ever since then). Anything you did not tell me stays empty.
3. I write the first line from inside the moment: a time, a place, a sentence someone said. No announcement, no "we partnered with".
4. The client's line goes in only if they said it and agreed to this channel; otherwise it becomes your paraphrase without quotation marks, or comes out. The number goes in exactly as your source has it, or not at all.
5. I end on a plain fact (what the client does now, what is still running), never a moral, a lesson list or "what do you think?".
6. I strip the tells: the negation frame, three-item lists for rhythm, inflated verbs, emojis as bullets. You cut or keep each one.
7. You edit it into your own words and post it from your own account. I never post.

## Output Format
```markdown
# Project Story Post
## Spine
| Beat | Your words | Source |
|---|---|---|
| Every day | [the normal before] | [your notes, date] |
| But one day | [what broke] | [source] |
| Because of that | [what you did, two lines] | [source] |
| Until finally | [what changed] | [source] |
| Ever since then | [plain-fact ending] | [source] |
## Draft
[First line inside the moment]
[Body in your sentences]
[Ending: a plain fact]
## Permission and numbers
| Item | Status | Agreed by, channel, date |
|---|---|---|
| Client named | [yes / anonymised] | [role, LinkedIn, date] |
| Client line | [quoted / paraphrased / removed] | [source] |
| Number | [kept exactly / removed] | [source] |
## Decision
[You decide whether to post this draft, edit it, or hold it until the client agrees, by [date]. You post it yourself.]
```

## Done When
- The post covers one moment, not the whole project.
- The first line is inside the moment and the last line is a plain fact.
- Every client line and number has a source and a recorded permission, or is gone.
- No moral, lesson list or call to comment remains.

## Quality Bar
- Two lines on what you did; the client, named by role unless agreed, and the change carry the rest.
- Numbers are kept exactly; no rounding up, no "about", no added comparison.
- Confidentiality or contract questions about describing the work: check with a qualified adviser.
- One real moment; client words and numbers only with source and agreement, and Claude never invents a story, client or number, or posts for you.

## Next
Run flink-lesson-learned-post (Lesson Learned Post) to share the mistake that taught you the most this quarter.

## About the makers

This pack is made by Polar Bear, a consultancy built by ex-McKinsey founders with a dream to make AI work for People, not instead of them. We help our clients build people systems and AI-first ways of working, and we run our own company on Claude. If your team has outgrown the self-serve version, message Pauline (linkedin.com/in/paulinebertry).