Create Meeting Minutes

Draft professional AEC meeting minutes from raw notes. Output is a Markdown document ready to email, paste into Word, or save as .md.

Input you need

Before drafting, gather:

• Project name — from $ARGUMENTS if provided, else ask.
• Meeting type — OAC, coordination, design review, kickoff, owner workshop, pre-bid, pre-construction, punch walk.
• Date in Month DD, YYYY format.
• Time + time zone (e.g., 9:00 AM ET).
• Location — address (in-person) or video-conference link.
• Attendees — name, firm, role.
• Raw notes — agenda items, discussion, decisions, action items.

If any of the above is missing or ambiguous, ask the user before drafting. Do not invent attendees, decisions, or action items.

Output structure

Produce a single Markdown document in this exact layout:

# Meeting Minutes — [Project Name]

**Meeting:** [type, e.g., OAC #4]
**Date:** [Month DD, YYYY]
**Time:** [HH:MM AM/PM zone]
**Location:** [address or video conference]
**Prepared by:** [name, firm]
**Distribution:** [comma-separated list]

---

## Attendees

| Name | Firm | Role |
|------|------|------|
| Sarah Chen | SOM | Architect of Record |
| ... | ... | ... |

## Discussion

### 1. [Topic]

[1–3 sentence summary of discussion.]

**Decisions:** [bullet list — or `None`]

### 2. [Topic]

...

---

## Action Items

| # | Item | Owner | Due | Status |
|---|------|-------|-----|--------|
| 1 | Confirm structural depth at grid B-3 | Sarah Chen, SOM | 2026-05-16 | Open |

---

## Open Issues

1. [Unresolved items carried forward to next meeting.]

---

## Next Meeting

**Date:** [TBD or specific]
**Agenda preview:**
- [Bullet]

NA AEC conventions (enforce)

• English only. No Hangul anywhere.
• Imperial-first units (ft, in, sf, °F); metric in parens only when useful.
• Dates use Month DD, YYYY (e.g., May 9, 2026). Time zones are explicit (ET / CT / MT / PT).
• Roles are project roles, not corporate titles: Architect of Record (AOR), Owner, Owner's Representative, Construction Manager (CM), MEP Engineer, Structural Engineer (SE), General Contractor (GC). Never use "Director" as a project role.
• Firms — full legal name on first reference, abbreviation thereafter.
• AHJs — name specifically: NYC DOB, FDNY, LADBS, DSA, CA HCAI, GSA, USACE, NYC SCA. Never "the city" or "the AHJ".
• Action item owners — Name, Firm (e.g., Sarah Chen, SOM). Firm alone is not enough.
• AIA contract references where relevant: AIA B101 §3.2.5.1 (design review), AIA A201 §3.2.2 (contractor review), etc.
• Floor labels — Level 3, L3, or 3rd floor. Never 3F.

Constraints

• Do not fabricate attendees, decisions, or action items that are not in the input.
• If raw notes are incomplete, surface gaps under Open Issues rather than guessing.
• Keep agenda-item summaries to 1–3 sentences. Minutes are a record, not a transcript.
• Action items must have an owner (named person + firm) and a due date. If the user did not record one, flag it explicitly: Owner: TBD — confirm at next meeting.
• Markdown only for v1. Word (.docx) and PDF output will be available once the aec-doc-gen companion skill is installed.

Workflow

1. Echo back what you parsed: meeting type, date, project, attendee count, agenda-item count. One line.
2. If any required input is missing, list the gap and stop.
3. Otherwise, produce the full Markdown document in one shot.
4. After the draft, list any items flagged for follow-up (TBD owners, missing dates, ambiguous decisions) so the user can resolve them before distributing.