plugins/pm-visuals/skills/org-chart/SKILL.md
Turn a team or reporting structure into a clean org chart. Use when asked to draw an org chart, show reporting lines, visualize team structure, or map who reports to whom. Produces a ready-to-render Mermaid org chart (renders live, exportable as PNG/SVG) plus headcount notes and any structural observations.
npx skillsauth add mohitagw15856/pm-claude-skills org-chartInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
A reporting structure described in prose is hard to hold in your head; an org chart makes the hierarchy, spans of control, and gaps obvious. This skill turns a described team into a clean Mermaid org chart — correct reporting lines, grouped functions, and dotted lines for matrix/indirect reports.
Ask for these only if they aren't already provided:
If only roles (not names) are given, chart the roles.
One line on scope (whole org, one department, etc.).
flowchart TD
CEO[CEO]
CPO[CPO]
CTO[CTO]
PM1[PM - Growth]
PM2[PM - Core]
EM[Eng Manager]
CEO --> CPO
CEO --> CTO
CPO --> PM1
CPO --> PM2
CTO --> EM
EM -.dotted.-> PM2
Headcount — totals by function or level, if known.
Observations (optional) — overloaded spans of control, vacant roles, single points of failure, unclear lines.
flowchart TD so the hierarchy reads top-down.--> report (arrow points down the hierarchy).-.dotted.-> for matrix/indirect reports so they're visually distinct.Organizational charting (reporting lines, spans of control, matrix relationships), as renderable Mermaid.
business
Analyze why deals are won and lost and turn it into an action plan. Use when asked to run a win/loss analysis, review closed-won and closed-lost deals, understand why the team is losing to a competitor, or summarize sales feedback into patterns. Produces a structured win/loss report with themes, win/loss rates by segment and competitor, representative quotes, and prioritized actions for product, marketing, and sales.
development
Route a fuzzy request to the right skill in this library. Use when the user is unsure which skill fits, asks 'which skill should I use for X', describes a task without naming a skill, or when a request could plausibly match several skills. Produces a best-fit recommendation with the inputs to gather, a runner-up with the tie-breaker, and a workflow recipe when the job spans multiple skills.
testing
Triage a vulnerability or scanner finding — assess real severity, exploitability, and how urgently to fix. Use when asked to triage a CVE, prioritize scanner/pentest findings, assess a vuln's risk, or decide what to patch first. Produces a triage verdict: CVSS-informed severity adjusted for your context, exploitability, real risk, a fix/mitigation, and an SLA — so you fix what matters, not just what's red.
development
Stand up a Voice of Customer (VoC) program that turns feedback into action. Use when asked to build a VoC program, design a customer feedback loop, consolidate feedback sources, or set up a closed-loop feedback process. Produces a VoC program design — objectives, feedback sources and channels, a taxonomy, collection and analysis cadence, closed-loop routing, ownership, and success metrics.