War Story Blog Post Builder

Build a war story blog post from the following experience: The incident/situation: {&{INCIDENT_DESCRIPTION}} Your role: {&{YOUR_ROLE}} What went wrong (specifics): {&{WHAT_WENT_WRONG}} Key turning point: {&{TURNING_POINT}} Outcome/aftermath: {&{OUTCOME}} The hard-won lesson: {&{LESSON}} Tone: {&{TONE}} (e.g., darkly funny, unflinchingly honest, quietly devastating) Target audience: {&{TARGET_AUDIENCE}} **Construct the post in this order:** 1. **Title Options (3 variants)**: - One that names the disaster directly - One that leads with the lesson - One that opens with an ironic moment 2. **Opening Scene** (100–130 words): Drop into the worst moment first. Present tense. Specific timestamp, specific place, specific sensation. Do not explain what happened — make the reader feel it. 3. **The Context** (150–200 words): Pull back. Explain what was supposed to happen. What was the plan, the expectation, the confidence level before things went sideways? 4. **The Unraveling** (300–400 words): Scene by scene, show how things deteriorated. Use real sequencing ("By 11:30pm...", "Two hours in..."). Include at least one human moment — a miscommunication, a wrong assumption, a moment of denial. 5. **The Pivot** (150–200 words): The moment the team/narrator stopped panicking and started solving. What actually worked? What was embarrassingly simple? 6. **The Aftermath** (150–200 words): What was the real cost? What changed? Be honest — don't manufacture a clean resolution. 7. **The Lesson** (100–150 words): One specific, transferable insight. Not "always have backups." Something more uncomfortable and more true. Frame it as a confession, not advice. 8. **Closing Line**: One sentence. Not a summary. Not a call to action. The kind of line that a reader copies into their notes. **Anti-patterns:** - Do NOT write the narrator as a hero - Do NOT end with "And that's why we now do X" unless the X is genuinely surprising - Do NOT sanitize the emotional reality of the incident