End "which file is latest?" forever
Creates a consistent project folder template, enforces versioned file naming, and keeps a lightweight transmittal log so you can always prove what was issued, when, and to whom.
Create a skill called "Project File & Version Governor" for an architecture practice. At project kickoff (or when I ask), you should: 1. Generate a standard folder structure by phase and discipline: 00_Admin, 01_SD, 02_DD, 03_CD, 04_CA, Consultants, Issued 2. Create a file naming convention cheat sheet with examples using the pattern YYYYMMDD-Issue-Rev## (or a pattern I specify) 3. Set up a transmittal log template with fields: date, recipient, version, scope, and notes 4. At every issue event, prompt me to update the transmittal log and lock the version in the Issued folder 5. Send weekly reminders to log any issued files and flag versions that look out of date If I report a "which file is latest?" confusion, trace it back through the log and tell me the answer.
Architecture projects generate thousands of files across months or years. When
someone asks "which version did we issue?" or "is this the latest CD set?",
you need an answer in seconds, not a 20-minute folder archaeology session.
This recipe sets up a standard folder structure at project kickoff, enforces a
naming convention, and maintains a transmittal log that tracks every issue event.
Kill RFIs before they're born
Runs a repeatable coordination pass between drawings, schedules, and specifications before every issue set. Catches mismatched terminology, missing spec references, and known conflict patterns — so the contractor finds fewer reasons to write RFIs.
Handle account suspensions with a calm, evidence-based playbook
Account suspensions can be existential for businesses. This recipe creates an incident SOP: information capture, likely causes, remediation steps, communications, and an escalation path. It also generates a "postmortem" template to prevent repeats.
Emergency checklist for internet/platform failures
Traders frequently mention outages and connectivity failures as real risks, especially when trades lack hard stops. This recipe creates an "emergency runbook" and periodically tests readiness.
Verify brand offers before you click anything
Screens incoming partnership offers for phishing and scam patterns: suspicious domains, attachments, fake checks, requests to "connect your account," and vague contracts. Outputs a risk rating and safe verification steps.