pm-claude-skills 61.2.2 → 62.0.0

package/README.md

@@ -1,4 +1,4 @@
-# 🧠 PM Skills — 751 Professional Agent Skills for Claude, ChatGPT, Gemini, Cursor, Codex & Hermes
+# 🧠 PM Skills — 771 Professional Agent Skills for Claude, ChatGPT, Gemini, Cursor, Codex & Hermes
 
 [![In the official Anthropic plugin directory](https://img.shields.io/badge/Anthropic%20Plugin%20Directory-Published-D97757?logo=anthropic&logoColor=white)](#-quick-start)
 [![Stars](https://img.shields.io/github/stars/mohitagw15856/pm-claude-skills?style=social)](https://github.com/mohitagw15856/pm-claude-skills/stargazers)
@@ -12,7 +12,7 @@
 [![License](https://img.shields.io/badge/license-MIT-lightgrey)](LICENSE)
 [![Sponsor](https://img.shields.io/badge/sponsor-❤️-ff69b4)](https://github.com/sponsors/mohitagw15856)
 
-**A library of 751 skills — each one a plain `SKILL.md` file that teaches your AI assistant to do one professional task properly.** Decode a lease before you sign it. Write a PRD your team can execute. Simulate the promotion committee before the real one meets. Check the weather with zero API keys. Generic AI gives you filler; these give you the structure a senior professional actually uses.
+**A library of 771 skills — each one a plain `SKILL.md` file that teaches your AI assistant to do one professional task properly.** Decode a lease before you sign it. Write a PRD your team can execute. Simulate the promotion committee before the real one meets. Check the weather with zero API keys. Generic AI gives you filler; these give you the structure a senior professional actually uses.
 
 Works natively in **Claude Code** and **Hermes Agent**, with ready-to-paste exports for **ChatGPT, Gemini, Cursor, Codex** and 8 more tools. *(PM stands for Professional, not just Product Management.)*
 
@@ -30,7 +30,7 @@ No `npm install` needed — `npx pm-claude-skills …` always runs the latest. `
 
 ## 📚 The skills
 
-Every skill follows the same discipline: what it produces, the inputs it needs, a real framework (severity scales, decision rules — not vibes), a concrete output template, quality checks, and anti-patterns. All 751 pass the [SkillSpec](SKILLSPEC.md) L3 gate and a security audit in CI.
+Every skill follows the same discipline: what it produces, the inputs it needs, a real framework (severity scales, decision rules — not vibes), a concrete output template, quality checks, and anti-patterns. All 771 pass the [SkillSpec](SKILLSPEC.md) L3 gate and a security audit in CI.
 
 ### For everyone — life's paperwork and decisions
 
@@ -46,7 +46,7 @@ Every skill follows the same discipline: what it produces, the inputs it needs,
 | 🤝 **Cowork** (100) | The office knowledge work an AI coworker actually does — the *frameworks* — [the whole bundle](plugins/pm-cowork/) | [email triage](skills/email-triage-system/SKILL.md) · [spreadsheet audit](skills/spreadsheet-audit/SKILL.md) · [meeting cost meter](skills/meeting-cost-meter/SKILL.md) · [deck outline first](skills/deck-outline-first/SKILL.md) · [saying no kindly](skills/saying-no-kindly/SKILL.md) · [delegation brief](skills/delegation-brief/SKILL.md) |
 | ⚡ **Cowork · Live** (12) | The same jobs, *done* — Claude Cowork acts on your **real data** via connectors + sandbox and returns an artifact — [the whole bundle](plugins/pm-cowork-live/) | [inbox triage (live)](skills/inbox-triage-live/SKILL.md) · [meeting prep (live)](skills/meeting-prep-live/SKILL.md) · [spreadsheet audit (live)](skills/spreadsheet-audit-live/SKILL.md) · [deck from doc](skills/deck-from-doc/SKILL.md) · [thread → decision](skills/thread-to-decision-live/SKILL.md) · [PR description (live)](skills/pr-description-live/SKILL.md) |
 
-### For professionals — 31 fields
+### For professionals — 35 fields
 
 | | | |
 |---|---|---|
@@ -55,7 +55,7 @@ Every skill follows the same discipline: what it produces, the inputs it needs,
 | 🎨 [Design & UX](plugins/pm-design/) | ⚖️ [Legal](plugins/pm-legal/) | 💰 [Finance](plugins/pm-finance/) |
 | 🚀 [Founders](plugins/pm-founders/) | 🔐 [Security](plugins/pm-security/) | 🏛 [Government](plugins/pm-gov/) |
 
-…plus HR, sales, operations, research, healthcare, educators, writers, social media, and more — **[the full profession index](SKILLS.md)**, or by bundle in [`plugins/`](plugins/) (90 bundles). Install any bundle: `/plugin install pm-decoders@pm-skills`.
+…plus HR, sales, operations, research, healthcare, educators, writers, social media, and more — **[the full profession index](SKILLS.md)**, or by bundle in [`plugins/`](plugins/) (94 bundles). Install any bundle: `/plugin install pm-decoders@pm-skills`.
 
 ### Meta
 
@@ -155,7 +155,7 @@ The whole library on one poster — start path, standout features, and install o
 
 ## 🆕 Latest
 
-**v61.2.2 — long-form video:** **[youtube-script](skills/youtube-script/SKILL.md)** — a full YouTube script (explainer/tutorial/video essay) engineered for watch-time: title + thumbnail concepts, a timed cold open, retention beats with B-roll cues, and chapter timestamps. Sibling to [short-form-script](skills/short-form-script/SKILL.md); for other languages, [professional-translator](skills/professional-translator/SKILL.md). *Earlier — v61.2, the builder's toolkit:* prove quality against real references, red-team robustness, test skills before a PR, run them offline, and sign what they produce. *v61.1, the demand side:* **[find](https://mohitagw15856.github.io/pm-claude-skills/find.html)** (task→skill router) with an honest per-skill **measured / no-claim** badge, per-skill versioning, and **[SkillSpec as an adoptable standard](conformance/REGISTRY.md)** (earnable `--badge` + public registry). Full history: **[CHANGELOG](CHANGELOG.md)** · [releases](https://github.com/mohitagw15856/pm-claude-skills/releases)
+**v62.0.0 — adopt-a-profession:** four new verticals built from the open "adopt a profession" issues — **[pm-teaching](plugins/pm-teaching/)** (K-12: lesson plans, IEP goals, parent conferences, behavior plans), **[pm-hospitality](plugins/pm-hospitality/)** (menu costing, health-inspection prep, shift schedules, guest incidents), **[pm-journalism](plugins/pm-journalism/)** (story pitch, source interviews, fact-check pass, source protection), and **[pm-veterinary](plugins/pm-veterinary/)** (treatment estimates, the euthanasia conversation, discharge notes, wellness plans). *Earlier — v61.3, most-requested skills* (reference-check, deprecation-comms, moderation-policy); *v61.2.2, [youtube-script](skills/youtube-script/SKILL.md);* *v61.1, the demand side:* **[find](https://mohitagw15856.github.io/pm-claude-skills/find.html)** (task→skill router) with an honest **measured / no-claim** badge. Full history: **[CHANGELOG](CHANGELOG.md)** · [releases](https://github.com/mohitagw15856/pm-claude-skills/releases)
 
 ## 🤝 Contributing
 
@@ -171,4 +171,4 @@ MIT — use them, fork them, ship them at work. Skills are judgment, and judgmen
 
 ---
 
-*Built by [Mohit](https://github.com/mohitagw15856) with Claude. 751 skills · 90 bundles · 31 professions · every commit gated. The long version of this README — every feature, wave, and frontier bet — lives in the **[Showcase](docs/SHOWCASE.md)**.*
+*Built by [Mohit](https://github.com/mohitagw15856) with Claude. 771 skills · 94 bundles · 35 professions · every commit gated. The long version of this README — every feature, wave, and frontier bet — lives in the **[Showcase](docs/SHOWCASE.md)**.*

package/exports/README.md

@@ -8,7 +8,7 @@ by hand; edit the source skill and run:
 node scripts/build-exports.mjs
 ```
 
-Currently exporting **751 skills** to:
+Currently exporting **771 skills** to:
 
 - **ChatGPT — Custom GPT instructions** → `exports/chatgpt/`
 - **Google Gemini — Gem instructions** → `exports/gemini/`

package/exports/aider/README.md

@@ -3,7 +3,7 @@
 > Auto-generated from `skills/*/SKILL.md` by `scripts/build-exports.mjs`.
 > **Do not edit these files by hand** — edit the source skill and regenerate.
 
-751 skills exported. Copy a `.md rule` into the tool to use it.
+771 skills exported. Copy a `.md rule` into the tool to use it.
 
 | Skill | Bundle | Path |
 |---|---|---|
@@ -54,6 +54,7 @@
 | Async Update Format | `pm-cowork` | `pm-cowork/async-update-format/async-update-format.md` |
 | Auto Repair Estimate Decoder | `pm-decoders` | `pm-decoders/auto-repair-estimate-decoder/auto-repair-estimate-decoder.md` |
 | Autopilot Charter | `pm-autopilot` | `pm-autopilot/autopilot-charter/autopilot-charter.md` |
+| Behavior Intervention Plan | `pm-teaching` | `pm-teaching/behavior-intervention-plan/behavior-intervention-plan.md` |
 | Beneficiary Audit | `pm-estate` | `pm-estate/beneficiary-audit/beneficiary-audit.md` |
 | Benefits Decoder | `pm-decoders` | `pm-decoders/benefits-decoder/benefits-decoder.md` |
 | Bid / Tender Review | `pm-construction` | `pm-construction/bid-tender-review/bid-tender-review.md` |
@@ -108,6 +109,7 @@
 | Claims Triage | `pm-insurance` | `pm-insurance/claims-triage/claims-triage.md` |
 | Claude Superpowers | `pm-engineering` | `pm-engineering/claude-superpowers/claude-superpowers.md` |
 | Clause Explainer | `pm-legal` | `pm-legal/clause-explainer/clause-explainer.md` |
+| Client Discharge Notes | `pm-veterinary` | `pm-veterinary/client-discharge-notes/client-discharge-notes.md` |
 | Client Discovery | `pm-consulting` | `pm-consulting/client-discovery/client-discovery.md` |
 | Climate Risk Assessment | `pm-climate` | `pm-climate/climate-risk-assessment/climate-risk-assessment.md` |
 | Clinical Case Summary | `pm-research` | `pm-research/clinical-case-summary/clinical-case-summary.md` |
@@ -126,6 +128,7 @@
 | College App Parent Guide | `pm-parents` | `pm-parents/college-app-parent-guide/college-app-parent-guide.md` |
 | College Cost | `pm-calculators` | `pm-calculators/college-cost/college-cost.md` |
 | Community Management Playbook | `pm-social` | `pm-social/community-management-playbook/community-management-playbook.md` |
+| Community Moderation Policy | `pm-social` | `pm-social/community-moderation-policy/community-moderation-policy.md` |
 | Company Brief | `pm-jobsearch` | `pm-jobsearch/company-brief/company-brief.md` |
 | Company Event Ops | `pm-cowork` | `pm-cowork/company-event-ops/company-event-ops.md` |
 | Comparative Market Analysis | `pm-realestate` | `pm-realestate/comparative-market-analysis/comparative-market-analysis.md` |
@@ -203,6 +206,7 @@
 | Demo Script | `pm-cowork` | `pm-cowork/demo-script/demo-script.md` |
 | Dependency Audit | `pm-engineering` | `pm-engineering/dependency-audit/dependency-audit.md` |
 | Dependency Conflict Resolver | `pm-engineering` | `pm-engineering/dependency-conflict-resolver/dependency-conflict-resolver.md` |
+| Deprecation Comms Plan | `pm-devrel` | `pm-devrel/deprecation-comms-plan/deprecation-comms-plan.md` |
 | Design Critique | `pm-design` | `pm-design/design-critique/design-critique.md` |
 | Design Handoff Brief | `pm-advanced` | `pm-advanced/design-handoff-brief/design-handoff-brief.md` |
 | Design System Audit | `pm-design` | `pm-design/design-system-audit/design-system-audit.md` |
@@ -253,6 +257,7 @@
 | ESG Disclosure Draft | `pm-climate` | `pm-climate/esg-disclosure-draft/esg-disclosure-draft.md` |
 | Estate Settlement Organizer | `pm-estate` | `pm-estate/estate-settlement-organizer/estate-settlement-organizer.md` |
 | Eulogy Writer | `pm-lifeadmin` | `pm-lifeadmin/eulogy-writer/eulogy-writer.md` |
+| Euthanasia Conversation | `pm-veterinary` | `pm-veterinary/euthanasia-conversation/euthanasia-conversation.md` |
 | EV vs Gas | `pm-calculators` | `pm-calculators/ev-vs-gas/ev-vs-gas.md` |
 | Eval Rubric Designer | `pm-ai` | `pm-ai/eval-rubric-designer/eval-rubric-designer.md` |
 | Evidence Grading | `pm-cowork` | `pm-cowork/evidence-grading/evidence-grading.md` |
@@ -276,6 +281,7 @@
 | Experiment Readout | `pm-dataeng` | `pm-dataeng/experiment-readout/experiment-readout.md` |
 | Expert Interview Prep | `pm-cowork` | `pm-cowork/expert-interview-prep/expert-interview-prep.md` |
 | Exploratory Test Charter | `pm-qa` | `pm-qa/exploratory-test-charter/exploratory-test-charter.md` |
+| Fact-Check Pass | `pm-journalism` | `pm-journalism/fact-check-pass/fact-check-pass.md` |
 | Factory Acceptance Test | `pm-hardware` | `pm-hardware/factory-acceptance-test/factory-acceptance-test.md` |
 | FAQ Builder | `pm-cowork` | `pm-cowork/faq-builder/faq-builder.md` |
 | Feature Flag Guide | `pm-engineering` | `pm-engineering/feature-flag-guide/feature-flag-guide.md` |
@@ -324,9 +330,11 @@
 | Grant Proposal | `pm-cross` | `pm-cross/grant-proposal/grant-proposal.md` |
 | Greenwashing Self-Audit | `pm-climate` | `pm-climate/greenwashing-self-audit/greenwashing-self-audit.md` |
 | Growth Experiment Backlog | `pm-growth` | `pm-growth/growth-experiment-backlog/growth-experiment-backlog.md` |
+| Guest Incident Log | `pm-hospitality` | `pm-hospitality/guest-incident-log/guest-incident-log.md` |
 | Handbook Page | `pm-cowork` | `pm-cowork/handbook-page/handbook-page.md` |
 | Hardware PRD | `pm-hardware` | `pm-hardware/hardware-prd/hardware-prd.md` |
 | Headline Options | `pm-copy` | `pm-copy/headline-options/headline-options.md` |
+| Health Inspection Prep | `pm-hospitality` | `pm-hospitality/health-inspection-prep/health-inspection-prep.md` |
 | Help Center Article | `pm-support` | `pm-support/help-center-article/help-center-article.md` |
 | HIPAA Safeguards | `pm-compliance` | `pm-compliance/hipaa-safeguards/hipaa-safeguards.md` |
 | Hiring Rubric | `pm-people` | `pm-people/hiring-rubric/hiring-rubric.md` |
@@ -339,6 +347,7 @@
 | i18n Readiness Review | `pm-localization` | `pm-localization/i18n-readiness-review/i18n-readiness-review.md` |
 | IEP 504 Meeting Kit | `pm-parents` | `pm-parents/iep-504-meeting-kit/iep-504-meeting-kit.md` |
 | IEP Goal Support | `pm-education` | `pm-education/iep-goal-support/iep-goal-support.md` |
+| IEP Goal Writer | `pm-teaching` | `pm-teaching/iep-goal-writer/iep-goal-writer.md` |
 | Impact Report | `pm-nonprofit` | `pm-nonprofit/impact-report/impact-report.md` |
 | Inbox Triage (Live) | `pm-cowork-live` | `pm-cowork-live/inbox-triage-live/inbox-triage-live.md` |
 | Inbox Unsubscribe Purge | `pm-cowork` | `pm-cowork/inbox-unsubscribe-purge/inbox-unsubscribe-purge.md` |
@@ -389,6 +398,7 @@
 | Legal Brief | `pm-legal` | `pm-legal/legal-brief/legal-brief.md` |
 | Lending Risk Brief | `pm-banking` | `pm-banking/lending-risk-brief/lending-risk-brief.md` |
 | Lesson Plan | `pm-education` | `pm-education/lesson-plan/lesson-plan.md` |
+| Lesson Plan Builder | `pm-teaching` | `pm-teaching/lesson-plan-builder/lesson-plan-builder.md` |
 | Lifecycle / CRM Plan | `pm-growth` | `pm-growth/lifecycle-crm-plan/lifecycle-crm-plan.md` |
 | LinkedIn Profile | `pm-personal` | `pm-personal/linkedin-profile/linkedin-profile.md` |
 | Literature Review | `pm-research` | `pm-research/literature-review/literature-review.md` |
@@ -415,6 +425,7 @@
 | Meeting Prep (Live) | `pm-cowork-live` | `pm-cowork-live/meeting-prep-live/meeting-prep-live.md` |
 | Meeting Prep Pack | `pm-cowork` | `pm-cowork/meeting-prep-pack/meeting-prep-pack.md` |
 | Meeting Room Etiquette | `pm-cowork` | `pm-cowork/meeting-room-etiquette/meeting-room-etiquette.md` |
+| Menu Cost Engineer | `pm-hospitality` | `pm-hospitality/menu-cost-engineer/menu-cost-engineer.md` |
 | Messaging Framework | `pm-growth` | `pm-growth/messaging-framework/messaging-framework.md` |
 | Metric Gaslighting Detector | `pm-warroom` | `pm-warroom/metric-gaslighting-detector/metric-gaslighting-detector.md` |
 | Metric Semantic Layer | `pm-dataeng` | `pm-dataeng/metric-semantic-layer/metric-semantic-layer.md` |
@@ -462,6 +473,7 @@
 | Package Health | `pm-live` | `pm-live/package-health/package-health.md` |
 | Paid Acquisition Plan | `pm-growth` | `pm-growth/paid-acquisition-plan/paid-acquisition-plan.md` |
 | Parent Communication | `pm-education` | `pm-education/parent-communication/parent-communication.md` |
+| Parent Conference Prep | `pm-teaching` | `pm-teaching/parent-conference-prep/parent-conference-prep.md` |
 | Parent Teacher Conference Prep | `pm-parents` | `pm-parents/parent-teacher-conference-prep/parent-teacher-conference-prep.md` |
 | Partnership Proposal | `pm-sales` | `pm-sales/partnership-proposal/partnership-proposal.md` |
 | Patient Communication | `pm-research` | `pm-research/patient-communication/patient-communication.md` |
@@ -541,6 +553,7 @@
 | Red-Team Review | `pm-cross` | `pm-cross/red-team-review/red-team-review.md` |
 | Redundancy Consultation | `pm-hr` | `pm-hr/redundancy-consultation/redundancy-consultation.md` |
 | Refactoring Plan | `pm-craft` | `pm-craft/refactoring-plan/refactoring-plan.md` |
+| Reference Check Script | `pm-recruiting` | `pm-recruiting/reference-check-script/reference-check-script.md` |
 | Reference Letter | `pm-lifeadmin` | `pm-lifeadmin/reference-letter/reference-letter.md` |
 | Reference Request Kit | `pm-layoff` | `pm-layoff/reference-request-kit/reference-request-kit.md` |
 | Referral Program | `pm-growth` | `pm-growth/referral-program/referral-program.md` |
@@ -611,10 +624,12 @@
 | Self-Review | `pm-career` | `pm-career/self-review/self-review.md` |
 | SEO Content Brief | `pm-gtm` | `pm-gtm/seo-content-brief/seo-content-brief.md` |
 | Sequence Diagram | `pm-visuals` | `pm-visuals/sequence-diagram/sequence-diagram.md` |
+| Server Training Guide | `pm-hospitality` | `pm-hospitality/server-training-guide/server-training-guide.md` |
 | Service Catalog Entry | `pm-engineering` | `pm-engineering/service-catalog-entry/service-catalog-entry.md` |
 | Session Handoff | `pm-tokens` | `pm-tokens/session-handoff/session-handoff.md` |
 | Severance Agreement Decoder | `pm-layoff` | `pm-layoff/severance-agreement-decoder/severance-agreement-decoder.md` |
 | Shared Drive Cleanup | `pm-cowork` | `pm-cowork/shared-drive-cleanup/shared-drive-cleanup.md` |
+| Shift Schedule Builder | `pm-hospitality` | `pm-hospitality/shift-schedule-builder/shift-schedule-builder.md` |
 | Short-Form Script | `pm-creator` | `pm-creator/short-form-script/short-form-script.md` |
 | Shutdown Ritual | `pm-cowork` | `pm-cowork/shutdown-ritual/shutdown-ritual.md` |
 | Side Business Setup | `pm-sidehustle` | `pm-sidehustle/side-business-setup/side-business-setup.md` |
@@ -634,6 +649,8 @@
 | Solar Breakeven | `pm-calculators` | `pm-calculators/solar-breakeven/solar-breakeven.md` |
 | S&OP Meeting Prep | `pm-supplychain` | `pm-supplychain/sop-meeting-prep/sop-meeting-prep.md` |
 | SOP Writer | `pm-operations` | `pm-operations/sop-writer/sop-writer.md` |
+| Source Interview Prep | `pm-journalism` | `pm-journalism/source-interview-prep/source-interview-prep.md` |
+| Source Protection Plan | `pm-journalism` | `pm-journalism/source-protection-plan/source-protection-plan.md` |
 | Source Triangulation | `pm-cowork` | `pm-cowork/source-triangulation/source-triangulation.md` |
 | Sourcing Strategy | `pm-recruiting` | `pm-recruiting/sourcing-strategy/sourcing-strategy.md` |
 | Sports Scores | `pm-live` | `pm-live/sports-scores/sports-scores.md` |
@@ -654,6 +671,7 @@
 | Statement of Work | `pm-consulting` | `pm-consulting/statement-of-work/statement-of-work.md` |
 | Status Report Pipeline | `pm-cowork` | `pm-cowork/status-report-pipeline/status-report-pipeline.md` |
 | Stock Snapshot | `pm-live` | `pm-live/stock-snapshot/stock-snapshot.md` |
+| Story Pitch | `pm-journalism` | `pm-journalism/story-pitch/story-pitch.md` |
 | Strategic Narrative Generator | `pm-strategy` | `pm-strategy/strategic-narrative-generator/strategic-narrative-generator.md` |
 | Strategy Memo | `pm-business` | `pm-business/strategy-memo/strategy-memo.md` |
 | Student Feedback | `pm-education` | `pm-education/student-feedback/student-feedback.md` |
@@ -715,6 +733,7 @@
 | ToS Decoder | `pm-decoders` | `pm-decoders/tos-decoder/tos-decoder.md` |
 | Transcreation | `pm-localization` | `pm-localization/transcreation/transcreation.md` |
 | Travel Brief | `pm-cowork` | `pm-cowork/travel-brief/travel-brief.md` |
+| Treatment Plan Estimate | `pm-veterinary` | `pm-veterinary/treatment-plan-estimate/treatment-plan-estimate.md` |
 | Unblock Protocol | `pm-cowork` | `pm-cowork/unblock-protocol/unblock-protocol.md` |
 | Underwriting Narrative | `pm-insurance` | `pm-insurance/underwriting-narrative/underwriting-narrative.md` |
 | Unit Economics | `pm-calculators` | `pm-calculators/unit-economics/unit-economics.md` |
@@ -743,6 +762,7 @@
 | Wedding Speech | `pm-lifeadmin` | `pm-lifeadmin/wedding-speech/wedding-speech.md` |
 | Wedding Vendor Contract Decoder | `pm-wedding` | `pm-wedding/wedding-vendor-contract-decoder/wedding-vendor-contract-decoder.md` |
 | Weekly Review Ritual | `pm-cowork` | `pm-cowork/weekly-review-ritual/weekly-review-ritual.md` |
+| Wellness Plan | `pm-veterinary` | `pm-veterinary/wellness-plan/wellness-plan.md` |
 | What To Ask | `pm-decoders` | `pm-decoders/what-to-ask/what-to-ask.md` |
 | When Someone Dies | `pm-estate` | `pm-estate/when-someone-dies/when-someone-dies.md` |
 | Which Skill Router | `pm-essentials` | `pm-essentials/which-skill/which-skill.md` |

package/exports/aider/pm-devrel/deprecation-comms-plan/deprecation-comms-plan.md

@@ -0,0 +1,65 @@
+# Deprecation Comms Plan Skill
+
+Deprecations go wrong in two ways: too fast (customers get broken and churn angry) or too quiet (they find out when it breaks). This skill plans the wind-down as a *communications program*, not an announcement — enough runway, messaging matched to how much each customer depends on the thing, a real migration path, and a plan for the accounts that will need a human.
+
+## Working from a brief
+
+Given what's being deprecated and why, **produce the full plan** — infer the risk tiers from usage and contract exposure. Right-size the runway to how hard the migration is (an internal flag flip is weeks; a public API is many months). If there's no migration path yet, flag that as a blocker before any announcement.
+
+## Required Inputs
+
+Ask for (if not provided, else infer and label the assumption):
+- **What's being deprecated** and **why** (cost, security, strategy, replaced-by)
+- **Who depends on it** — rough usage, and which segments/contracts are exposed
+- **The replacement / migration path** (or that there isn't one yet)
+- **Hard constraints** — a forcing date (security, legal, contract), team capacity
+
+## Output Format
+
+### Deprecation policy in one line
+The principle you're committing to (e.g. _"announce → N months deprecated (works, warns) → sunset, with a migration path live before we announce"_).
+
+### Timeline
+
+| Phase | Date / window | What changes | What customers can still do |
+|---|---|---|---|
+| Announce | | nothing breaks; docs + warnings | full use, start migrating |
+| Deprecated | | warnings, no new adoption | migrate |
+| Sunset | | turned off | must have migrated |
+
+Include grace periods and any extension policy for large accounts.
+
+### Tiered messaging
+Segmented by dependence, not one blast:
+- **Tier 1 — heavy/contractual users:** proactive, human (CSM/AM), often a call + tailored plan.
+- **Tier 2 — active users:** direct email + in-product warning + migration guide.
+- **Tier 3 — light/dormant:** changelog, docs banner, deprecation headers.
+
+For each: the core message (what, when, why, what to do), the ask, and the escalation path.
+
+### Migration guide outline
+The structure of the how-to: before/after, step-by-step, code/config examples, a mapping table (old → new), FAQ, and where to get help.
+
+### Channel plan
+Which channels fire at which phase — email, in-product, docs/changelog, API deprecation headers/`Sunset` header, status page, community/social — and the cadence (announce, reminders at intervals, final notice).
+
+### Internal escalation playbook
+The at-risk account list, who owns each, the CSM talking points, the "customer can't migrate in time" decision tree, and the exception/extension approval path.
+
+## Quality Checks
+
+- [ ] A migration path exists and is referenced everywhere before any customer message goes out
+- [ ] Runway is sized to migration difficulty, with grace periods stated
+- [ ] Messaging is tiered by dependence; Tier-1 accounts get a human, not a blast
+- [ ] Every message says what, when, why, and the exact next step
+- [ ] The channel cadence includes reminders and a final notice, not a single announcement
+- [ ] High-risk accounts have a named owner and an escalation/extension path
+
+## Anti-Patterns
+
+- Too little runway for the migration actually required
+- A silent breaking change, or burying it in a changelog nobody reads
+- Announcing before the migration path is live
+- One-size messaging that treats a whale like a dormant free user
+- No plan for the accounts that physically can't migrate in time
+- "Why" that blames the customer or the old system instead of owning the change

package/exports/aider/pm-hospitality/guest-incident-log/guest-incident-log.md

@@ -0,0 +1,55 @@
+# Guest Incident Log Skill
+
+When a guest slips, has a reaction, or complains of illness, what you write in the next hour can protect both the guest and the business — or sink it. This skill captures the facts objectively, records the response, and routes the notifications, without the speculation or apologies-as-admissions that create legal exposure.
+
+## Working from a brief
+
+Given what happened, **produce the full record** — capture only observed facts, mark anything reported-by-guest as such, and never invent details. Flag anything that requires immediate medical, legal, or regulatory action.
+
+## Required Inputs
+
+Ask for (if not provided, else infer and label):
+- **What happened** — the incident type and a factual account
+- **Who** — guest, staff involved, witnesses (and contact info if available)
+- **When/where** and the **immediate actions** already taken
+
+## Output Format
+
+### Immediate response (if still unfolding)
+The right-now checklist: ensure safety/medical aid, secure the area/preserve evidence (the spilled item, the food, photos), don't move hazards until documented, get witness details.
+
+### Incident report
+
+| Field | Detail |
+|---|---|
+| Date / time / location | |
+| Incident type | injury / illness / foodborne / altercation / property |
+| Persons involved | guest, staff, witnesses (contacts) |
+| Factual account | observed facts, in sequence |
+| Guest statements | quoted, marked "as reported by guest" |
+| Actions taken | aid given, area secured, who was notified |
+| Evidence | photos, retained item, CCTV reference |
+
+### Notification & escalation
+Who to inform and when — manager on duty, owner/GM, insurance carrier, and any mandatory reporting (a suspected foodborne illness may require the health department).
+
+### Follow-up
+Guest follow-up (care, not admission), corrective action to prevent recurrence, and where the record is retained.
+
+## Quality Checks
+
+- [ ] The account is factual and objective; guest claims are marked as reported, not asserted
+- [ ] Witnesses and their contact details are captured while fresh
+- [ ] Immediate safety/medical response is documented, and evidence preserved
+- [ ] Notifications/escalation (incl. any mandatory health-dept reporting) are listed
+- [ ] No admissions of fault or speculation about cause
+- [ ] Follow-up includes a corrective action to prevent recurrence
+
+## Anti-Patterns
+
+- Speculating on cause or fault ("we should have mopped sooner") in the record
+- Apologies phrased as admissions of liability
+- Vague account with no times, witnesses, or actions
+- Losing the evidence (throwing out the food, mopping before photos)
+- Forgetting mandatory reporting for a suspected foodborne illness
+- Filing it nowhere retrievable when insurance/legal needs it later

package/exports/aider/pm-hospitality/health-inspection-prep/health-inspection-prep.md

@@ -0,0 +1,50 @@
+# Health Inspection Prep Skill
+
+Inspectors don't fail you on dust — they fail you on the handful of **priority violations** that make people sick: temperature abuse, cross-contamination, bare-hand contact, handwashing, and pest activity. This skill runs the self-audit the way an inspector scores it, so the critical stuff is fixed before they walk in.
+
+## Working from a brief
+
+Given the establishment type, **produce the full self-audit** — prioritize by public-health risk, not by what's easiest to see. Base it on standard food-code categories; note that local codes vary and the operator should confirm specifics.
+
+## Required Inputs
+
+Ask for (if not provided, else infer and label):
+- **Type of establishment** (full-service, quick-service, bar, food truck, commissary) and menu risk (raw proteins, sushi, etc.)
+- **Known problem areas** or a prior inspection's violations
+- **When** the inspection window is / how much time to prep
+
+## Output Format
+
+### Critical / priority items (fix first)
+The violations that shut kitchens — each with the standard and a pass/fail check:
+- **Temperature:** cold holding ≤ 41°F, hot holding ≥ 135°F, cooking temps, cooling (135→70°F in 2h, 70→41°F in 4h), thermometer calibrated.
+- **Cross-contamination:** raw-above-ready storage order, separate boards/utensils, sanitizer concentration.
+- **Hygiene:** handwash sinks stocked & accessible, no bare-hand contact with ready-to-eat food, sick-employee policy.
+- **Pests:** no activity/harborage, entry points sealed.
+
+### Non-critical (address, won't close you)
+Facility, labeling, storage, cleaning cadence.
+
+### Fix list
+
+| Item | Risk | Fix | Owner | By when |
+|---|---|---|---|---|
+
+### On the day
+How to receive the inspector: cooperate, don't argue, know where the logs and permits are, correct-on-the-spot where possible, and how to respond to a violation professionally.
+
+## Quality Checks
+
+- [ ] Critical/priority items are separated from cosmetic ones and listed first
+- [ ] Temperature holding, cooling, and cross-contamination are all covered with specific thresholds
+- [ ] Handwashing and no-bare-hand-contact are explicitly checked
+- [ ] Every found gap has a fix, an owner, and a deadline
+- [ ] A note that local food codes vary and specifics should be confirmed
+
+## Anti-Patterns
+
+- Deep-cleaning visible surfaces while ignoring cold-holding temps
+- Treating all violations as equal (a critical temp violation ≠ a scuffed floor)
+- No thermometer calibration or temperature logs
+- Blocking or arguing with the inspector on the day
+- Prepping once instead of building the habits that pass every time

package/exports/aider/pm-hospitality/menu-cost-engineer/menu-cost-engineer.md

@@ -0,0 +1,51 @@
+# Menu Cost Engineer Skill
+
+Restaurants don't fail on bad food — they fail on math they never did. A dish that "feels" priced right can quietly run a 45% food cost. This skill costs the plate honestly (accounting for yield loss and waste), sets a price to the margin the operator actually needs, and flags where the menu is leaking money.
+
+## Working from a brief
+
+Given a recipe and ingredient prices, **produce the full costing** — estimate yields and waste where not given (label the assumption). If prices are missing, ask or use a stated regional estimate and flag it.
+
+## Required Inputs
+
+Ask for (if not provided, else infer and label):
+- **The dish** — ingredients and portion sizes (recipe)
+- **Ingredient costs** — as purchased, with pack size/unit
+- **Target food-cost %** (default ~28–32%) or target margin, and current menu price if repricing
+
+## Output Format
+
+### Plate cost breakdown
+
+| Ingredient | As-purchased cost/unit | Yield % | Portion | Plate cost |
+|---|---|---|---|---|
+| | | | | |
+
+Include a line for waste/trim and any garnish/consumables.
+
+### The numbers
+- **Total plate cost**, target food-cost %, and **suggested price** = plate cost ÷ target food-cost %.
+- Actual food-cost % at the current price (if repricing) and the gap.
+- Contribution margin per plate (price − plate cost).
+
+### Menu-engineering flag
+Given popularity (if provided) and margin, classify: **Star** (high both — feature it), **Plow-horse** (popular, low margin — reprice/re-engineer), **Puzzle** (high margin, low sales — promote/reposition), **Dog** (low both — cut or rework).
+
+### Levers
+2–3 concrete moves — portion, spec, supplier, price, or plate composition — to hit the target without hurting the guest experience.
+
+## Quality Checks
+
+- [ ] Plate cost accounts for yield loss and waste, not just as-purchased price
+- [ ] Suggested price is derived from the target food-cost %, shown explicitly
+- [ ] Contribution margin (not just %) is reported — a high % on a cheap dish can still lose
+- [ ] Assumptions (yields, missing prices) are labeled, not hidden
+- [ ] The menu-engineering flag drives a concrete recommendation
+
+## Anti-Patterns
+
+- Costing on as-purchased price and ignoring yield/waste (understates true cost)
+- Chasing food-cost % while ignoring contribution margin per plate
+- Pricing on gut instead of the target margin
+- Repricing a plow-horse so hard it becomes a dog
+- Treating supplier prices as fixed when spec/portion are the real levers

package/exports/aider/pm-hospitality/server-training-guide/server-training-guide.md

@@ -0,0 +1,52 @@
+# Server Training Guide Skill
+
+Most restaurants "train" by throwing a new hire on the floor with a tray and hoping. The result is inconsistent service and quick turnover. This skill builds a real ramp: a new server learns the steps of service, the menu, and the systems in a sequence, with a clear bar for when they're ready to run a section solo.
+
+## Working from a brief
+
+Given the restaurant type, **produce the full guide** — infer the service style (fine dining, casual, fast-casual, bar) and scale the depth and standards to it.
+
+## Required Inputs
+
+Ask for (if not provided, else infer and label):
+- **Restaurant type / service style** and the **role** (server, host, bartender, busser)
+- **Menu complexity** and any signature service points (tableside, wine program, allergen protocol)
+- **Systems** — POS, reservation/waitlist, payment, and how long the ramp should be (e.g. 3–5 shifts)
+
+## Output Format
+
+### Training phases
+A staged ramp with what happens and who owns it:
+1. **Orientation** — culture, standards, safety, sanitation basics.
+2. **Shadow** — follow a trainer, observe the full service sequence.
+3. **Hands-on with a trainer** — take tables with support.
+4. **Solo with a safety net** — own a small section, trainer on call.
+5. **Sign-off** — cleared for a full section.
+
+### Service-sequence standards
+The steps of service for this restaurant (greet time, drink/order timing, check-backs, pre-bussing, the close), with the specific standards (e.g. "greet within 2 minutes").
+
+### Knowledge checks
+Menu and allergen quiz points, upsell/pairing basics, and the "86 / substitution / allergy" protocol every server must know cold.
+
+### Systems & side-work
+POS order flow, payment and comps/voids policy, opening/closing side-work, and section/station setup.
+
+### Sign-off checklist
+The observable competencies a trainer checks before solo — greeting, order accuracy, timing, allergen handling, POS, closing.
+
+## Quality Checks
+
+- [ ] Training is phased (shadow → supported → solo), not sink-or-swim
+- [ ] Service-sequence standards are specific and observable (times, steps)
+- [ ] Allergen and 86/substitution protocol is explicitly trained and checked
+- [ ] A sign-off checklist defines "ready for a section alone"
+- [ ] Depth matches the service style (fine dining ≠ fast-casual)
+
+## Anti-Patterns
+
+- Day-one solo with no shadow or support
+- Service "standards" too vague to observe or coach
+- Skipping the allergen/86 protocol (a safety and liability gap)
+- No defined bar for readiness — trainers guessing
+- A binder no one uses instead of hands-on, checked practice

package/exports/aider/pm-hospitality/shift-schedule-builder/shift-schedule-builder.md

@@ -0,0 +1,47 @@
+# Shift Schedule Builder Skill
+
+A schedule is a bet on demand: overstaff and you burn margin, understaff and service (and your best people) walk. This skill builds coverage from the demand curve out — enough hands at the rush, lean in the lulls — then checks the labor cost and the human constraints before it's posted.
+
+## Working from a brief
+
+Given the team, hours, and demand pattern, **produce the full schedule** — infer the day-part demand shape from the business type if no forecast is given (label it). Respect stated availability and time-off; never schedule someone into a conflict you were told about.
+
+## Required Inputs
+
+Ask for (if not provided, else infer and label):
+- **Team** — names/roles, pay rates or an average, and availability/time-off
+- **Operating hours** and the **demand pattern** (covers by day-part, peak times, events)
+- **Labor-cost target** (% of revenue or a dollar cap) and any rules (max hours, required rest, minors)
+
+## Output Format
+
+### Coverage plan
+Demand mapped to required heads per role per day-part:
+
+| Day-part | Forecast demand | Cooks | Servers | Support | Notes |
+|---|---|---|---|---|---|
+
+### The schedule
+Person-by-person shifts across the week (start–end, role, station), with total hours per person.
+
+### Labor cost check
+Projected labor hours × rates → labor cost, as a % of forecast revenue vs. the target, with the gap and where to trim/add.
+
+### Guardrails flagged
+Overtime risk, insufficient rest between close/open ("clopening"), availability conflicts, minor-hour limits, and anyone over/under their expected hours.
+
+## Quality Checks
+
+- [ ] Staffing per day-part is driven by the demand pattern, not flat coverage
+- [ ] Projected labor cost is computed and compared to the target
+- [ ] No one is scheduled against stated availability or time-off
+- [ ] Rest-between-shifts, overtime, and minor-hour rules are checked and flagged
+- [ ] Hours are distributed with an eye to fairness, not just cost
+
+## Anti-Patterns
+
+- Flat staffing that ignores the rush-and-lull demand curve
+- Posting a schedule without checking the labor-cost %
+- Scheduling "clopens" or overtime by accident
+- Ignoring stated availability (the fastest way to lose staff)
+- Cutting so lean that service and food quality collapse at peak

package/exports/aider/pm-journalism/fact-check-pass/fact-check-pass.md

@@ -0,0 +1,52 @@
+# Fact-Check Pass Skill
+
+Everything in a published piece is a claim someone can be wrong about — a date, a number, a quote, an implication. This skill does what a good fact-checker does: it pulls every checkable assertion out of the prose, verifies each against a source, and stops the high-risk ones (stats, quotes, anything defamatory) from going out on a "probably right."
+
+## Working from a brief
+
+Given the draft, **produce the claim inventory and status** — check what you can against the provided/known sources, and for anything you can't verify, mark it clearly rather than guessing. Never assert a fact is confirmed without a basis.
+
+## Required Inputs
+
+Ask for (if not provided, else infer and label):
+- **The draft** (article, script, report)
+- **Available sources** — the reporter's notes, documents, links, transcripts
+- **Risk level / venue** — where it publishes and how litigious/high-stakes the subject is
+
+## Output Format
+
+### Claim inventory
+Every checkable assertion extracted:
+
+| # | Claim (as written) | Type | Status | Source / basis | Fix |
+|---|---|---|---|---|---|
+
+- **Type:** number/stat · quote · name/title · date · causal/implied · characterization.
+- **Status:** ✅ confirmed · 🟡 needs sourcing · ⚠️ unverifiable · 🔴 wrong/misleading.
+
+### High-risk flags
+The claims that must not publish unverified — statistics, direct quotes and their attribution, named individuals (especially any allegation), superlatives ("first," "only," "largest"), and anything potentially defamatory. Each with what's needed to clear it.
+
+### Fixes
+For every 🔴/⚠️: the correction, a hedge to the supportable version, or "cut it." For 🟡: the source to obtain.
+
+### Sign-off
+What's still open before this can publish, and a note that quotes should be confirmed with the speaker/transcript and legal review sought for anything defamatory.
+
+## Quality Checks
+
+- [ ] Every checkable claim is inventoried, not just the obvious ones
+- [ ] Each claim has a status and a named source/basis (or is marked unverifiable)
+- [ ] Numbers, quotes, names, and superlatives are treated as high-risk and flagged
+- [ ] Potentially defamatory statements are flagged for verification and legal review
+- [ ] Nothing is marked confirmed without an actual basis
+- [ ] Every problem claim has a concrete fix (correct / hedge / cut)
+
+## Anti-Patterns
+
+- Reading for tone instead of extracting discrete claims
+- Marking something "confirmed" on memory or vibes
+- Letting a round number or a paraphrased quote through unchecked
+- Missing implied/causal claims because they're not stated as facts
+- Waving through a defamatory line without verification or legal input
+- Rewriting the prose instead of flagging and sourcing the facts