Step 1: A line the tracker can read
Priya runs Brightline Books' weekly meetings, and after each one somebody types the action items into
the tracker by hand. It takes twenty minutes and things get lost: an action with no owner, a "by
Friday" that nobody turned into a date. You will write the prompt that does it. There is no code:
you edit prompt.md.
guidelines.md is Priya's house style. notes.jsonl has 8 real-looking meetings, each with the
actions a careful person would list. The harness sends each meeting to a model with your prompt, reads
the lines back and prices every mistake in minutes of Priya's time. A missed action costs 3, an invented
one 2, a wrong owner 2 and a wrong date 1.
The tracker imports lines in one exact shape. Anything else it cannot read, and a line it cannot read counts as a mistake.
Do this:
- Replace the one-line prompt above
---NOTES---. Ask for exactly one line per action, in the form fromguidelines.md, and nothing else: no headings, no bullets, no explanation. - Click Run.
python3 run_tests.py 2shows the model's full reply for meeting 2.
The check needs at least 20 of the 26 actions found and no more than 2 unreadable lines.
prompt.md, the file you edit8 lines
<!-- prompt.md: your instructions go above ---NOTES---; the template for each meeting goes below it.
The template can use {notes}, {date}, {weekday} and {calendar} (the next 45 days, one per line).
Notes between these marks are removed before sending. -->
<!-- TODO (Step 1): ask for one line per action in the tracker's exact format (see guidelines.md),
and nothing else. -->
List the action items from these meeting notes.
---NOTES---
{notes}actions.pyguidelines.mdholdout.jsonlnotes.jsonlrun_tests.py