fix(plugins): sync all 171 plugin SKILL.md files with fixed skills/ versions

Propagates Anti-Patterns sections, description rewrites, Required Inputs
additions, and Quality Checks format fixes from skills/ to matching plugin
SKILL.md copies.

https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt

plugins/pm-operations/skills/email-triage/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: email-triage
-description: Reads your Gmail inbox for a configurable window (default: last 8 hours) and surfaces only what needs action — replies, decisions, or follow-up. Filters out receipts, notifications, newsletters, and anything that doesn't need you.
+description: "Reads your Gmail inbox for a configurable window (default: last 8 hours) and surfaces only what needs action — replies, decisions, or follow-up. Filters out receipts, notifications, newsletters, and anything that doesn't need you."
 ---
 
 # Email Triage
@@ -169,6 +169,14 @@ Keep this to one line. Do not elaborate.
 - [ ] Output is scannable — no unnecessary prose, no padding
 - [ ] Financial statements and sensitive content were counted but not shown in full
 
+## Anti-Patterns
+
+- [ ] Do not surface FYI emails in the High or Medium priority sections — burying actionable items with informational ones defeats the purpose of triage
+- [ ] Do not write vague "What they need" summaries ("Sarah sent an email about the report") — every summary must state the actual ask, not a description of the email
+- [ ] Do not apply the same tone to every reply starter — a formal email from a client requires a different opener than a casual Slack-style email from a colleague
+- [ ] Do not include emails outside the requested time window — time window accuracy is the core trust signal for this skill
+- [ ] Do not omit the filtered-out count — users need to know how much was scanned, not just what was surfaced, to trust the triage is complete
+
 ## Dispatch / Mobile Usage
 
 This skill works from the Claude mobile app (Dispatch). On mobile, the output renders cleanly with the emoji priority markers serving as visual anchors for quick scanning. Recommended mobile trigger: "Check my emails" or "/email-triage".

plugins/pm-operations/skills/morning-intelligence/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: morning-intelligence
-description: "Run a 15-question interview to capture your role, topics, sources, exclusions, and format preferences — then write a master prompt you can drop into a scheduled task or Claude Code Routine to get a personalised news brief every morning. Use when asked to set up a morning intelligence brief, build a morning news prompt, or create a personalised news briefing."
+description: "Interviews you across 15 questions to capture your role, topics, sources, exclusions, and format preferences, then writes a master prompt you can paste into a scheduled task or Claude Code Routine. Use when you want to set up a personalised daily news brief, build a reusable morning news prompt, or create an automated intelligence briefing. Produces a confirmed summary of your preferences, a ready-to-paste master prompt, and setup instructions for both Cowork Scheduled Tasks and Claude Code Routines."
 ---
 
 # Morning Intelligence Skill
@@ -185,6 +185,14 @@ UPDATING YOUR BRIEF
 - [ ] The master prompt is inside a code block so it copies cleanly
 - [ ] Both setup options (Cowork and Claude Code Routines) are included
 
+## Anti-Patterns
+
+- [ ] Do not skip the interview and write a generic master prompt — a brief that is not tailored to the user's specific role and topics will be ignored after the first day
+- [ ] Do not proceed to write the master prompt without confirming the "What I Heard" summary — errors in the summary will silently propagate into a prompt that produces the wrong briefing every morning
+- [ ] Do not use broad topic labels in the master prompt (e.g. "AI", "tech news") — every topic must have a specific angle or focus to produce signal-to-noise ratio worth reading
+- [ ] Do not omit the NEVER INCLUDE section — without explicit exclusions, the briefing will fill with noise that the user said they wanted filtered out
+- [ ] Do not ask all 15 questions at once — the interview must run one question or small group at a time to produce specific, considered answers
+
 ---
 
 ## Example Trigger Phrases

plugins/pm-operations/skills/process-documentation/SKILL.md

@@ -83,6 +83,14 @@ Next review due: [Date]
 - [ ] Escalation path is named (specific people or roles, not just "your manager")
 - [ ] Review date is set
 
+## Anti-Patterns
+
+- [ ] Do not write steps without specifying who is responsible for each — ownership must be explicit throughout
+- [ ] Do not omit the escalation path — every process must say what happens when something goes wrong
+- [ ] Do not document the ideal process if the real process differs — document reality, then note improvements separately
+- [ ] Do not skip edge cases and exceptions — they are where most process failures actually occur
+- [ ] Do not produce documentation without a review date — undated process docs quickly become incorrect
+
 ## Example Trigger Phrases
 - "Document this process: [description]"
 - "Write a process guide for [workflow]"

plugins/pm-operations/skills/project-status-report/SKILL.md

@@ -111,6 +111,14 @@ RAG definitions:
 - [ ] Milestones are binary (complete or not complete — no "85% done")
 - [ ] Executive summary can stand alone for a stakeholder who reads nothing else
 
+## Anti-Patterns
+
+- [ ] Do not rate project health as Green while listing unresolved critical blockers
+- [ ] Do not report milestone progress as a percentage — milestones are binary: complete or not complete
+- [ ] Do not bury risks at the bottom — if something is high risk, it belongs in the executive summary
+- [ ] Do not leave decisions required without specifying who must decide and by when
+- [ ] Do not write an executive summary that requires reading the full report to understand — it must stand alone
+
 ## Example Trigger Phrases
 - "Write a project status report for [project]"
 - "Generate a RAG status update for [project]"

plugins/pm-operations/skills/raci-matrix/SKILL.md

@@ -151,6 +151,14 @@ Please review the full matrix here: [Link]. Raise any concerns by [Date] — aft
 - [ ] A communication plan exists to share the RACI with all involved parties
 - [ ] Decision map covers the top 5–10 highest-stakes decisions in the project
 
+## Anti-Patterns
+
+- [ ] Do not assign more than one Accountable per task — shared accountability means no accountability
+- [ ] Do not create a RACI with more than 5–6 roles — it becomes unreadable and unenforceable
+- [ ] Do not include tasks so broad that the RACI cannot be acted upon — break down to decision-level granularity
+- [ ] Do not skip the conflict resolution process — RACI matrices without a process for disputes are unused after the first disagreement
+- [ ] Do not confuse Responsible with Accountable — document the distinction clearly for each role
+
 ## Example Trigger Phrases
 
 - "Build a RACI matrix for our product launch"

plugins/pm-operations/skills/risk-register/SKILL.md

@@ -209,3 +209,11 @@ A risk is closed when:
 - "What risks should I document for a data migration project?"
 - "Generate a risk register for our steering committee"
 - "Help me identify and score risks for our Q3 delivery plan"
+
+## Anti-Patterns
+
+- [ ] Do not assign risks to "the team" or "TBD" — every risk must have a named individual owner
+- [ ] Do not write mitigations as "monitor and review" — mitigations must describe what is actively being done to reduce likelihood or impact
+- [ ] Do not delete closed risks — they provide an audit trail; archive them instead
+- [ ] Do not confuse risks with issues — a risk is something that might happen; an issue is something that has already happened
+- [ ] Do not leave Critical or High risks without a contingency plan — what happens if the mitigation fails must be documented

plugins/pm-operations/skills/sop-writer/SKILL.md

@@ -92,3 +92,11 @@ NOTE: Steps must be written in imperative form. Each step must have one action o
 - "Write an SOP for [process]"
 - "Create a standard operating procedure for [task]"
 - "Write a work instruction for [process]"
+
+## Anti-Patterns
+
+- [ ] Do not write steps that contain more than one action — each step must be a single, auditable action in imperative form
+- [ ] Do not omit a role from any step — every action must be assigned to a specific role or the SOP cannot be enforced
+- [ ] Do not skip the non-conformance section — an SOP without a deviation process cannot meet audit or regulatory requirements
+- [ ] Do not produce an SOP without a review date and version history — undated documents cannot be relied upon for compliance
+- [ ] Do not use passive voice in procedure steps — write "Open the system" not "The system should be opened"

plugins/pm-operations/skills/vendor-evaluation/SKILL.md

@@ -73,6 +73,14 @@ Security: ISO 27001 / SOC 2 certified? Where is data stored? Breach notification
 - [ ] Runner-up rationale explains why they lost (enables future conversations)
 - [ ] Contract terms to negotiate are specified
 
+## Anti-Patterns
+
+- [ ] Do not weight all evaluation criteria equally — the scorecard must reflect the relative importance of each criterion
+- [ ] Do not evaluate vendors only on features — security, support, contract terms, and financial stability matter too
+- [ ] Do not produce a recommendation without explaining why the runner-up lost — this enables future vendor conversations
+- [ ] Do not skip contract terms to negotiate — identifying leverage points is part of the procurement decision
+- [ ] Do not recommend a vendor without stating the conditions under which the recommendation would change
+
 ## Example Trigger Phrases
 - "Help me evaluate vendors for [procurement]"
 - "Create a vendor scorecard for [software/service]"

plugins/pm-operations/skills/workshop-facilitation-guide/SKILL.md

@@ -140,6 +140,14 @@ End every session with:
 - [ ] Parking lot is used actively (not a graveyard)
 - [ ] Close captures decisions and actions before the room empties
 
+## Anti-Patterns
+
+- [ ] Do not design a workshop without explicitly linking every activity to a session goal — purposeless activities waste participant time
+- [ ] Do not schedule more than 90 minutes of continuous structured activity without a break
+- [ ] Do not close a workshop without capturing decisions and actions before the room empties — post-session follow-up is too late
+- [ ] Do not plan a workshop without considering psychological safety for sensitive topics — establish ground rules at the start
+- [ ] Do not underestimate timing — add 20% buffer to all activity estimates, especially for groups over 8 people
+
 ## Example Trigger Phrases
 
 - "Design a workshop for [goal] with [group]"