PMO Skills

Nine skills covering a project from intake through cadence for new-gen PMOs using Notion and Slack. Name and description are pulled straight from each skill file — the source link goes to the real thing.

Skill	Description	Impact	Source
`pmo-project-overview`	Turn notes from the initial one-on-one between a PM and the project sponsor/requestor into a structured project overview and team roster, then create it as a child subpage under the project's Notion node — following the HostPapa PMO project-initiation methodology. Use whenever the user has notes, a transcript, or a recap from that initial "what is this project" meeting and wants a project overview, summary, or Notion "entry point" page from it — e.g. "turn these notes into a project overview," "summarize this intake call for the project page," "draft the overview for the WordPress migration project." Asks for the project node URL and publishes as a subpage there. This overview is shared at the later team kickoff call (see `pmo-kickoff-scheduler`) — this skill is the sponsor meeting that precedes it, not the kickoff. First skill in the pmo- family; other pmo-* skills cover later stages (team intake, scheduling, meeting recaps, Slack/Notion sync, project registry).	High time savings	View the skills file
`pmo-project-registry`	Locate and validate a project's four Notion/Slack data repositories — the project node page, steps database, project workbook database, and Slack channel — then record them in a "Data Repositories" section on the project node page, following the HostPapa PMO methodology. Use whenever the user wants to register, record, or confirm where a project's data lives, or asks where a specific repository is for a project — e.g. "set up the project registry for the WordPress migration," "register the data repositories for this project," "confirm the steps database and Slack channel are set up right for X," "where does this project's workbook live." Runs real validation checks (naming patterns, database vs. page, expected views, public vs. private channel) rather than trusting a URL at face value. Part of the pmo- family; `pmo-project-overview`, `pmo-team-member-intake`, `pmo-step-schedule`, and `pmo-slack-notion-sync` all check this registry's "Data Repositories" section before falling back to asking the PM directly.	Low time savings	View the skills file

Skill	Description	Impact	Source
`pmo-team-member-intake`	Turn notes or a transcript from a PM's one-on-one with a contributing team member (or several members of the same team), held after the initial project-sponsor meeting, into a structured capture of what that person confirmed, contributed, and needs — then create it as a new page in Notion and flag any genuine conflicts or unresolved questions directly on the Project Overview, following the HostPapa PMO's team-onboarding process. Use whenever the user has notes from a one-on-one with someone who will actually do the work on a project (as opposed to the sponsor/requestor) and wants it turned into a project record — e.g. "here's my call with the engineering lead, capture this," "turn these notes from my one-on-one with Design into the intake," "I met with two people from Data, write up what we got." Asks for the destination Notion URL and creates the page there rather than just returning text. Part of the pmo- family alongside pmo-project-overview.	Medium time savings	View the skills file

Skill	Description	Impact	Source
`pmo-step-schedule`	Preps a project's Notion Steps database ahead of the team-intake 1:1s by carrying forward applicable steps and learnings from similar past projects (found via the Project Manager property), plus a specific previous plan or steps database if the PM has one — then keeps the schedule current from weekly sync notes posted in the project's Slack channel. Follows the HostPapa PMO's steps-not-tasks methodology — steps are deliverables, not task chains. Use when a PM wants to prep for team 1:1s by reusing what applies from past projects, or wants statuses refreshed from this week's Slack sync. Triggers include "find past projects like this and carry forward what applies," "prep the steps database before I meet the teams," "update the schedule from this week's sync." Doesn't write team-confirmed deliverables or propose milestones — pmo-planning-synthesis owns that once deliverables are confirmed. Asks for the destination Notion URL. Part of the pmo- family with pmo-project-overview and pmo-planning-synthesis.	High time savings	View the skills file

Skill	Description	Impact	Source
`pmo-kickoff-scheduler`	Given a confirmed project team roster, propose and send calendar invites for two distinct scheduling moments in a project's life — the kickoff call with the sponsor and full team (run once team feedback from pmo-team-member-intake is resolved), and the bundled block of planning sessions plus the recurring weekly sync (run once the kickoff call has happened). Never sends a single invite without showing the complete proposed batch first and getting explicit approval. Use whenever the user wants meetings scheduled to move a project forward — e.g. "schedule the kickoff call for this project," "set up the planning sessions and weekly sync now that kickoff happened," "get invites out for the WordPress migration team." This is the automation the PMO methodology was actively prototyping, not an established process — it stays conservative on purpose. Part of the pmo- family, downstream of pmo-project-overview and pmo-team-member-intake.	Low time savings	View the skills file

Skill	Description	Impact	Source
`pmo-planning-synthesis`	Turn planning-session meeting transcripts into a documented strategy and plan (WBS), attached under the Steps database's seeded "Define a strategy"/"Create a plan" rows; write each team's confirmed deliverable as its own step row (using pmo-team-member-intake outputs, refined by planning); then propose milestones from the finished schedule and the Project Overview. Use once a project's planning sessions have happened and the PM wants the schedule finalized — e.g. "write up the strategy and plan from planning and finish the schedule," "turn the planning notes into our WBS and propose milestones." Asks the PM directly for the relevant Project Workbook entries rather than searching for them. Shows drafts and proposed steps/milestones for approval before writing. Part of the pmo- family, downstream of pmo-team-member-intake and pmo-kickoff-scheduler's Flow B, and of pmo-step-schedule's prep run.	High time savings	View the skills file

Skill	Description	Impact	Source
`pmo-meeting-recap`	Reconcile a PM's own light meeting notes against the Gemini/AI notes and transcript, write a strict-format recap (Conclusions, Decisions, Changes, Problems, Risks, Dependencies, Action items, Things to know), get the PM's approval, then post it as a threaded reply under that meeting's agenda message in the project's Slack channel — following the HostPapa PMO's meeting cadence. Use whenever the user has their own scratch notes from a meeting plus Gemini/Google Meet notes or a transcript and wants a reconciled recap written up and posted — e.g. "cross-check my notes against the Gemini notes and post the recap," "here's my scratch notes and the AI transcript, write up this meeting," "post the recap for today's sync." The point is catching what the PM missed while staying present in the meeting, not just summarizing a transcript. Never posts without explicit approval. Part of the pmo- family; the recap it posts is exactly what pmo-slack-notion-sync later mines for the workbook.	High time savings	View the skills file
`pmo-slack-notion-sync`	Pull decisions, changes, problems, risks, dependencies, action items, and learnings out of a Slack message or thread — typically a pmo-meeting-recap post — and add them as new rows in the project workbook database in Notion, tagged by category with a link back to the source message. Use whenever the user has a Slack message or thread and wants its contents synced into the workbook — e.g. "sync this recap into the workbook," "pull the decisions and action items from this thread into Notion," "add what's in this Slack message to the project workbook." Recognizes pmo-meeting-recap's fixed headings directly; falls back to best-effort categorization for plainer messages, flagging anything ambiguous instead of guessing. Checks for duplicates before adding and never modifies the workbook's schema. Part of the pmo- family, downstream of pmo-meeting-recap.	Medium time savings	View the skills file
`pmo-link-harvest`	Scan a Slack channel over a date range — reading every thread in full, not just parents — for links to real documents (Docs/Sheets, Notion pages, Jira tickets, sites) never logged in the project's Notion Project Workbook, then add each as a row: Recorded = message date, Name = the document's real title, Summary (≤40 words) naming who shared it with a link back to the source message, URL, Category (Jira for Atlassian links, Doc otherwise). Use when the workbook needs to catch up on links shared in a channel — e.g. "scan #proj-mwp-rebuild since Monday for links we haven't logged," "check the migration channel this week for docs people shared," "did anyone drop a link in the channel we missed." Skips links pointing only to other Slack messages — only genuine documents count. Always checks existing workbook URLs first. Part of the pmo- family with pmo-slack-notion-sync (which pulls decisions/risks/action items from one message — this sweeps a whole channel over time instead).	Medium time savings	View the skills file