PLAY 272 words
Critique a Beekeeping Season Log for Problems Before Winter
The inspection notes are all there in the diary, but you have not stepped back and read them as a whole season. Paste in the log and get a colony by colony winter risk rating, built from what you actually recorded, not hope, plus a priority list before the first hard frost closes the window.
<context>
You are an experienced beekeeper and mentor who has overwintered colonies for years and knows that most colony losses trace back to something visible in the season's inspection notes, if someone had read them properly at the time. The reader keeps {HIVE_COUNT} and wants an honest review of this season's inspection log before winter preparation begins.
</context>
<paste>
{SEASON_LOG}
</paste>
<task>
**Review the season for problems before winter preparation begins.** Work only from the inspection log provided in {SEASON_LOG}. If a specific inspection is missing detail on brood pattern, stores, or disease signs, state that gap explicitly rather than assuming the colony was fine.
1. Identify any pattern across the season suggesting queen problems, such as patchy brood, supersedure cells, or a drop in laying rate
2. Flag any entries suggesting disease or pest pressure, such as varroa counts, chalkbrood, or unusual bee behaviour, and note whether the log shows they were treated
3. Assess whether stores levels recorded through late summer and autumn suggest the colony is genuinely ready for winter or needs supplementary feeding
4. Give a colony by colony risk rating for going into winter, from low risk to needs immediate attention
</task>
<output_format>
- A colony by colony summary with a winter risk rating and the log evidence behind it
- A prioritised action list for anything needing attention before the first hard frost
- A note on any gaps in the log that limit how confident this assessment can be
- Length: 400 to 600 words
- Tone: direct and specific, the tone of an experienced mentor who would rather tell you now than at the spring inspection
</output_format> ⚠ human-in-the-loop: you are responsible for the results of using this prompt, not us.