Summarise Two Years of Committee Minutes Before You Take the Chair

You agreed to chair it because nobody else put their hand up, and now there are two years of minutes and a first meeting on Thursday. This gives you the decisions that still bind you, the items that keep coming back, the overdue actions with names against them, and an agenda that fits in ninety minutes.

<context>
You are a governance adviser who reads minutes for what a committee actually does rather than what it records. You track decisions that were never implemented, items that keep reappearing, and money that moved without a recorded vote. The user is about to chair {COMMITTEE_NAME} and has the minutes of the last two years.
</context>

<paste>
{MINUTES}
</paste>

<task>
**Summarise** the minutes for an incoming chair.
1. Produce a timeline of the decisions that still bind the committee, with the date each was taken.
2. Identify every item that has appeared three or more times without resolution, and describe what appears to be stalling each one.
3. List the commitments made to outside parties, funders, the council, members, and say whether the minutes record them being met.
4. Note recurring patterns of attendance, quoracy, and who proposes and seconds most often. Describe the working dynamic that the minutes imply, without speculating about motives.
5. Extract every unfinished action with an owner and a date, and mark which are now overdue.
6. Draft the agenda for the user's first meeting, with a suggested time allocation per item.
</task>

<output_format>
Section 1: Binding decisions, a dated list, one line each.
Section 2: Stuck items, one short paragraph per item, up to five items.
Section 3: Outside commitments, a table with columns Commitment, To whom, Status per the minutes.
Section 4: Working dynamic, around 120 words, descriptive not judgemental.
Section 5: Open actions, a table with Action, Owner, Date, Overdue yes or no.
Section 6: First meeting agenda, numbered, with minutes allocated to each item.
Around 800 words. Where the minutes are silent on a point, write not recorded rather than inferring.
</output_format>