dgusoff
- 9 skills
- 0 followers
- 1 hour ago last updated
- ▌ Cargo Arrival Schedule Analysis · dgusoff bundleAnalyzes the LA LNG ISBL Critical Cargo / Planning Schedule workbooks in the "Logistics Barge Schedule" Teams channel — arrivals by port (HOU, LCH), MOF barge arrivals, road and domestic barging, and vendor voyages — and builds the readable consolidated workbook from one. Use when the user asks to "analyze the barge schedule", "what's the latest cargo arrival schedule", "what changed between SF28 and SF29", "what arrives at the MOF next month", "which shipments are TBC or delayed", "build the consolidated view", or references an "SFxx Planning Schedule" file. Do NOT use for the line-item vendor equipment table (use vendor-equipment-consolidation), for unrelated spreadsheets (use the xlsx skill), for scheduling meetings, or for other Teams channels.
- ▌ Brief · dgusoff bundleUse when a manager or senior engineer wants to capture what they know so others can use it — "create a brief", "build a brief on", "capture what I know about", "brain dump", "let me dictate my thinking", "onboarding guide for my team", "document how we actually do this", "write up the tribal knowledge", "knowledge transfer for my project", "make a one-pager on this process" — or when someone asks a question against an existing brief ("what does the brief say about"), asks to update one, or submits a document to be checked against one. Do not use for meeting or transcript summaries (use meeting-intel), for status updates to stakeholders (use stakeholder-comms), for engineering review comment matrices or backchecks (use comment-disposition-build or comment-backcheck), or for formatting an existing document with no knowledge capture involved.
- ▌ Comment Backcheck · dgusoff bundleStep 2 of the engineering-document review comment-disposition cycle: verify that checker/reviewer comments were actually incorporated into the revised document before backcheck and approval. Compares the original comments, the revised document, and the Step 1 disposition matrix, then sets each comment to Incorporated (with evidence of where the change was made), Not Incorporated (with the originator's stated rationale), or Needs Clarification; drafts disposition language where appropriate; and flags comments with no traceable change. Use when the user asks to "backcheck the revised document", "did I address the checker's comments", "verify the markup was incorporated", "disposition these comments against the revised doc", "check the comments before approval", or "finish the disposition form". Do NOT use to build or extract the initial matrix from raw markup — use comment-disposition-build instead; and do NOT author, technically review, or approve/sign the deliverable.
- ▌ Followup Escalation Coordination · dgusoff bundleTracks pending actions, approvals, review requests, and open tasks across Teams chats, meetings, email, and Planner, then drafts reminders, escalation notices, and status roll-ups using age and priority rules. Use when user asks to "what am I waiting on", "who owes me a response", "chase my open approvals", "follow up on my pending items", "what's overdue", "escalate stalled items", or "send a status update on open actions". Also use when the user asks what they still owe or have not done across meetings, with no request to create tasks. Do NOT use for a general day overview (use daily-briefing), summarizing one meeting (use meeting-intel), or creating tasks from a single meeting recap (use meeting-action-items-to-planner).
- ▌
- ▌ Lessons Learned Drafting · dgusoff bundleTurns Natrium / NS&E project experience — meeting notes, emails, IDC or EPPR activity, issue resolutions, quality events, field observations — into a submission-ready Bechtel Lessons Learned package aligned to procedure 2QP-M01-00002 Rev. 002, screened for lesson quality, legal sensitivity, duplicate risk, institutionalization, and project impact. Use when the user asks to "draft a lesson learned", "turn these notes into a lessons learned submission", "review this draft lesson against the Bechtel procedure", "is this a valid lesson learned or just an action item", "rewrite this lesson to remove blame", or "suggest institutionalization and impact assessment follow-ups". Do NOT use to approve, reject, publish, archive, legally review, or submit a lesson — Ideagen and the SharePoint Lessons Learned Portal remain the system of record. Do NOT use to build a parallel lessons repository.
- ▌ Vendor Equipment Consolidation · dgusoff bundleBuilds the Consolidated Vendor Equipment table — one row per equipment Tag ID — from the weekly LA LNG ISBL planning schedule's vendor detail tabs, following Quiana Cipriani's documented consolidation process. Use when the user asks to "build the vendor equipment table", "rebuild Quiana's table", "run the consolidation prompt", "consol vendor equip table", "line-item equipment table", or wants tags with weights and ETAs listed individually. Do NOT use for shipment-level arrival analysis, MOF/port timelines, or "the consolidated view" (use cargo-arrival-schedule-analysis), nor for unrelated spreadsheets (use the xlsx skill).
- ▌ Comment Disposition Build · dgusoff bundleStep 1 of the engineering-document review comment-disposition cycle: turn a checker/reviewer marked-up PDF into a structured IDC comment disposition matrix the originator can work through. Handles both typed markup (Bluebeam/ Acrobat annotations) and handwritten ink on scanned check-prints, merging them into one register, and separates the originator's responses from the reviewer's comments so replies are never logged as new comments. Use when the user asks to "build the comment disposition form", "create the IDC disposition form", "extract comments from this markup PDF", "turn this markup into a disposition matrix", "log the checker's comments into a register", or "transcribe the handwritten review comments". Do NOT use to verify incorporation or backcheck a revised document — use comment-backcheck instead; and do NOT author, technically review, or approve the document.
- ▌ Bechtel Enterprise Word Doc · dgusoff bundleUse when a Bechtel user asks to "create a Bechtel Word document", "make this a Word doc", "use the Bechtel Word template", "build a Bechtel memo", "create a fact sheet", "write a long-form report", "apply BVI to this document", or "turn these files and images into a branded DOCX". Creates or restyles editable Word documents on the official Bechtel templates, applies Bechtel Visual Identity typography, palette, logo, and accessibility rules, places user-supplied images, charts, and tables intentionally, and validates the file before delivery. Do NOT use for PowerPoint, Excel, PDF-only delivery, non-Bechtel or client/JV branding, final technical or legal approval, or publishing to a system of record.