Verified against ChatGPT · 2026-08-13
Write an occasion poem in a specific form without it reading like a greeting-card template
Produces a poem for a real occasion in a chosen fixed form, using one concrete, specific memory as its anchor image so the form's constraints sharpen the meaning instead of forcing generic sentiment into the meter.
The prompt
Ready to copy — highlighted parts are example details you can swap.
Write a poem for a specific occasion, in the form specified below. The biggest risk with occasion poems is that the form's constraints push the language toward generic sentiment — I want the opposite: one real, specific detail doing all the emotional work, with the form sharpening it rather than diluting it. OCCASION A father's retirement after 34 years as a high school shop teacher. FORM Shakespearean sonnet (14 lines, ABAB CDCD EFEF GG, iambic pentameter). THE ONE CONCRETE MEMORY OR DETAIL TO ANCHOR ON He kept a coffee can full of mismatched screws on his workbench and could find the right one by feel in under ten seconds, without looking. WHO IT'S FOR Written by his daughter, to be read aloud at his retirement dinner. RULES Build the entire poem around He kept a coffee can full of mismatched screws on his workbench and could find the right one by feel in under ten seconds, without looking. — do not introduce a second, unrelated memory or image partway through just to fill out the form's length requirement; if the form needs more material, find it by looking closer at the one detail already given (its texture, what led up to it, what it implies) rather than importing something new. Follow the technical requirements of Shakespearean sonnet (14 lines, ABAB CDCD EFEF GG, iambic pentameter). precisely (meter, rhyme scheme, line count, or repetition pattern, whichever applies) — state the scheme you're using at the top of your output before the poem itself, so any deviation is visible rather than silently smoothed over. Avoid the stock vocabulary of occasion poetry (words like "cherish," "treasure," "forever," "journey" used abstractly) unless one of those words is doing specific, load-bearing work tied to the anchor detail rather than functioning as filler sentiment. Let the final line or stanza turn — reveal something about the anchor detail or the relationship that wasn't obvious from the opening, rather than simply restating affection more emphatically. WHAT NOT TO DO Do not write generic praise that could apply to any Written by his daughter, to be read aloud at his retirement dinner. in this same occasion category — every line should only make sense for this specific person and this specific memory, such that swapping in a different name or occasion would break the poem. Do not sacrifice the anchor detail's specificity to make a rhyme or meter work; if a technical requirement of the form is fighting the concrete detail, flag the tension and pick the version that keeps the detail intact. OUTPUT FORMAT 1. The form and scheme stated plainly (e.g., "Petrarchan sonnet, ABBAABBA CDECDE"). 2. The poem. 3. One line noting any place you had to make a trade-off between the form's technical requirement and the anchor detail's specificity, and which way you resolved it.
Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Occasion poems default toward generic sentiment because a fixed form imposes real constraints (meter, rhyme, line count) that are easiest to satisfy with abstract, high-frequency emotional vocabulary — words like "cherish" and "forever" are metrically flexible and rhyme easily, which is exactly why they show up so often in weak occasion verse, and it's the same reason a model under a strict form constraint will reach for them unless explicitly redirected. Anchoring the entire poem on one supplied concrete detail and explicitly forbidding the introduction of a second, unrelated image forces GPT-5.1 to generate the form's required additional material by examining the given detail more closely rather than padding with new, generic content — which is the difference between a poem that could only be about this specific person and one that's a template with a name dropped in. Requiring the form's scheme to be stated explicitly before the poem itself creates a checkable commitment: a model asked simply to "write a sonnet" will sometimes produce fourteen lines with an inconsistent or drifting rhyme scheme because nothing forces it to track the pattern it's supposed to be holding, and stating the scheme up front makes any drift visible to both the model and the reader rather than silently smoothed over in generation. The instruction to flag trade-offs between the form's technical demands and the anchor detail's specificity matters because those two goals do genuinely conflict sometimes — a perfect rhyme sometimes only exists in more generic language — and surfacing the trade-off rather than silently resolving it toward the easier, blander option keeps the writer in control of which one wins.
What you get back
Not treasure, no — a coffee can of screws, / mismatched, unsorted, thirty years deep-worn; / his hand knew which to choose before he'd choose, / found by feel alone, past needing to be shown.
Verified against
ChatGPT GPT-5.1 · 2026-08-13
Changelog
- 2026-08-13 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.
EXPLORE WHAT SCULT BUILDS
