What your five skills actually produce.

Every sample below was generated by running the real skill on one shared, fictional construction project — Northgate Retail Centre. Not mockups: genuine, downloadable outputs.

Core daily

DOCX

meeting-minutes

Say "write up the minutes"

Formatted Minutes of Meeting for Project Team Meeting PTM #13 — attendees, a previous-actions review that threads forward, numbered discussion items and a colour-coded actions summary.

• Every action has a named owner and a specific due date — no “the team”, no vague dates.
• Disputes recorded with both positions attributed by name (the $180k claim vs the ~$70k Apex disputes).
• Live Word dropdown controls in the remarks and priority columns; validated OOXML, 4 clean pages.

Download sample →

DOCX

executive-summary-report

Say "give me an ex summary"

A decision-ready executive summary for the client’s senior management at Month 9 — the 3-point progress slip, root causes, the variation dispute and the façade award, with numbered actions.

• Leads with the “so what”, then an amber risk callout and a “so what” line after every data table.
• Shows the commercial working (~$110k agreed / ~$70k disputed) rather than just quoting a total.
• 3 tight A4 pages with a clean sign-off block.

Download sample →

MD

mom-priority-distiller

Say "distil the MOM / what do I chase"

PTM #13 distilled into a prioritised action table, decisions log, risk flags, a watch-list and a pre-brief for the next meeting.

• Status logic worked against today’s date: critical items read OVERDUE, near-term items DUE THIS WEEK.
• Sorted overdue → critical → high, with carryover, cost-impact and owner flags applied.
• Doubles as a meeting pre-brief for PTM #14.

Download sample →

MD

document-review

Say "review this / anything off"

A sceptical review of the ~$180k basement-waterproofing variation — unbundles the claim into legitimate change vs re-measure vs padding, and arms you with sharp challenge questions.

• Exposes where the disputed ~$70k hides, tied to the real project facts.
• Ends with seven pointed questions to ask before approving anything.
• Flags the natural next steps (a formal letter, an exec summary, an email to the QS).

Download sample →

MD

email-drafter

Say "draft an email to…"

A firm-but-professional chase to the architect and structural lead — pressing for a transfer-slab recovery plan, coordinating the façade interface, and locking a call before the next PTM.

• Facts and the ask carry the pressure, not cold language; collaborative framing, no “you must”.
• Chase structure: what was expected/when → impact → what’s needed by when, with dated asks.
• No padding, no buzzwords — a searchable subject line and one live figure from the project.

Download the draft (Word) →