Turn a meeting transcript into a properly formatted .docx

When to use

Writing up minutes eats an hour after every meeting, and the format drifts each time. What matters is the decisions and the action items.

Preparation

Host version

0.1.2-alpha.5

Model

To fill

Mode / permissions

--profile headless / workspace-write / python-docx / no Word / no LibreOffice

Plugins required

None (add name & version after testing if used)

Input materials

A 534-character synthetic meeting note with three decisions that name an owner and two items explicitly marked undecided

Full instruction

Turn this meeting transcript into formal minutes as a .docx.

The transcript came from speech recognition; expect typos and filler words. Requirements:
1. Fixed structure: meeting info (date, attendees, topics), decisions, action items, risks and open questions.
2. Action items in a table with four columns: item, owner, due, status. If an owner or due date was not stated, write 'not specified'. Never guess.
3. Decisions must reflect what was actually said; do not add judgments nobody voiced.
4. Remove filler and repetition without changing facts or numbers.
5. When generating the .docx: Heading 1/2 for structure, 12pt body, bordered tables, filename minutes-YYYYMMDD.docx.
6. Finish with a list of every edit you made: which sentences were merged and what you dropped as small talk.

Copy full instruction

Run log

What the run showed

• The clause about preserving undecided items held: the output contains the undecided marker 10 times and the 'not stated in source' marker 11 times. I verified by reading the file back with python-docx, not by trusting its report.
• It did something extra and useful: a separate section for information the source lacks — meeting location, chair, note-taker, which three products, who delivers the design file. None of that was in the source, and inventing it would have been easier than leaving it blank.
• One thing to improve: reading styles with python-docx showed all 12 paragraphs are Normal, no Heading. Visual hierarchy was likely done by manual size and bold, which means Word's navigation pane and automatic table of contents see no structure. The recipe should require heading styles.
• It reported an OOXML child-element order check (zero violations, to avoid Word refusing the file). I cannot verify that independently — no Word on this machine.

Output

After a successful run, list files and screenshots here, and note whether originals changed.

Acceptance checklist

Tap to tick each item off as you verify.

• All four sections present, no invented chapters
• No fabricated owner or deadline; missing values say 'not specified'
• Every decision can be traced back to a line in the transcript
• The .docx opens cleanly with correct heading levels and table styling
• Edit list included and each change can be traced

Failures & boundaries

• Output quality is capped by transcription quality; jargon and crosstalk are the main error sources
• No audio upload here: transcribe first, then feed the text in
• Does not replace compliance requirements for minutes (for example cases that require the original recording)
• This is a recipe template; it has not been run end to end on this site yet

Claim this recipe Back to recipes