Record and generate professional meeting minutes for OAC meetings, progress meetings, safety meetings, and pre-installation conferences. Tracks action items across meetings with automatic carry-forward. Generates .docx minutes documents with status indicators. Integrates with morning brief (overdue action items), weekly report (meeting summary), and daily report (action item references). Surfaces critical action items in handoff reports. Triggers: "meeting notes", "meeting minutes", "OAC meeting", "OAC notes", "progress meeting", "safety meeting", "toolbox talk", "pre-install meeting", "pre-installation conference", "action items", "carry forward", "action item status".
From foremanos-planningnpx claudepluginhub mgoodman60/foreman-os-plugin --plugin foremanos-planningThis skill uses the workspace's default tool permissions.
references/action-item-tracking.mdreferences/docx-styling.mdreferences/meeting-template.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Provides structured meeting recording, action item tracking, and professional .docx generation for construction project meetings. Supports multiple meeting types with specialized content for pre-installation conferences. Automatically carries forward open action items between meetings and surfaces critical items in daily operations.
{
id: "MTG-001", # Auto-assigned, sequential, never reset
type: "OAC" | "progress" | "safety" | "pre-install" | "coordination",
date: "2025-02-17", # ISO 8601 format
time: "09:00 AM", # 12-hour format with AM/PM
location: "Project Trailer" | "Site Office",
attendees: [
{
name: "John Smith",
company: "ABC Construction",
role: "Project Manager",
phone: "555-0101",
email: "john@abcconstruction.com"
},
...
],
discussion_items: [
{
topic: "Schedule Updates",
discussion_summary: "Team reviewed current critical path...",
decisions_made: ["Adjust concrete pour by 3 days", "Expedite rebar delivery"],
linked_action_items: ["AI-0001", "AI-0002"]
},
...
],
action_items: ["AI-0001", "AI-0002", ...], # References to action item IDs
carry_forward_items: ["AI-0045", "AI-0046", ...], # From previous meetings
previous_meeting_id: "MTG-015" | null,
prepared_by: "Jane Doe",
prepared_date: "2025-02-17",
general_notes: "Weather delay expected next week"
}
{
id: "AI-0001", # Auto-assigned, sequential, never reset
description: "Review final mechanical submittal and approve",
assignee: "Tom Jones",
assignee_company: "XYZ MEP",
due_date: "2025-02-24",
status: "open" | "in_progress" | "closed" | "deferred",
linked_rfi: "RFI-018" | null,
linked_co: "CO-005" | null,
linked_submittal: "SUB-M-042" | null,
created_meeting: "MTG-001",
closed_meeting: null,
notes: "Client awaiting architect review",
created_date: "2025-02-17"
}
{
project_id: "PRJ-2024-001",
meetings: [
{ Meeting Object },
{ Meeting Object },
...
],
last_meeting_date: "2025-02-17"
}
{
project_id: "PRJ-2024-001",
items: [
{ Action Item Object },
{ Action Item Object },
...
],
open_count: 23,
overdue_count: 3,
closed_count: 145
}
When creating a new meeting:
If meeting type == "pre-install":
/morning-brief surfaces:
- Overdue action items (due_date < today AND status in [open, in_progress])
- High-priority open items from most recent OAC meeting
- Any deferred items with new due dates
- Display format: "2 overdue action items require status update"
/weekly-report includes:
- Count of meetings held that week
- Summary of meeting types
- New action items created
- Action items closed
- Overdue count at week end
- Critical decisions made (from OAC meetings)
- Format: Executive summary section, detailed table
/daily-report can reference:
- Due today action items
- Upcoming critical milestones
- Links to related meeting minutes
- Format: "Action items due today" section
Transition reports include:
- All open action items (sorted by due date)
- Deferred items with rationale
- Critical carry-forward items for next phase
- Meeting schedule cadence established
folder_mapping.oac_reports / "meeting_minutes" / "meeting_minutes_MTG-001_2025-02-17_OAC.docx"
meeting-log.json → meetings[] → All meetings, indexed by meeting_id
meeting-log.json → action_items[] → All action items, indexed by action_id
meeting-log.json → last_meeting_date → Date of most recent meeting
When project intelligence is loaded, auto-populate meeting agenda sections with current project data to save time and ensure accuracy.
Before or during progress/OAC meetings:
schedule.json → current_phase, percent_complete, milestones[]schedule.json → critical_path[] → list critical path activities and their statusFor OAC and progress meetings:
rfi-log.json → count RFIs by status (open, overdue >14 days, resolved this week)submittal-log.json → count submittals by status (pending review, overdue >10 days, approved this week)For OAC meetings:
change-order-log.json → group COs by status (draft, submitted, under_review, approved)For all meeting types:
meeting-log.json → pull all action items where status != "closed" from previous meetingsFor progress meetings:
daily-report-data.json → pull weather data from all reports in the meeting periodFor all meeting types (safety moment section):
safety-log.json → pull incident count, near-miss count for the periodosha_300_log if availablesafety-log.json → toolbox_talks[] → count talks held this periodThe skill activates on phrases like: