From pm-simulators
Read your team's messages the way opposing counsel would in litigation discovery — prevention training that makes communication hygiene visceral. Use when asked how would our Slack look in discovery, train my team on communication hygiene, review this thread like a plaintiff's lawyer, or what shouldn't we put in writing. Produces the highlighted-exhibit reading of sample messages, the patterns that create legal risk, and a debrief with the write-it-this-way rules — strictly for prevention, never for concealment.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-simulators:discovery-eyesThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Every message your team writes is a potential exhibit with a highlighter across it, read aloud years later, stripped of tone and context. This skill performs that reading on *sample* messages — jokes that become admissions, speculation that becomes knowledge, "delete this after reading" that becomes the whole case — as prevention training. Its purpose is writing carefully and acting properly, *...
Every message your team writes is a potential exhibit with a highlighter across it, read aloud years later, stripped of tone and context. This skill performs that reading on sample messages — jokes that become admissions, speculation that becomes knowledge, "delete this after reading" that becomes the whole case — as prevention training. Its purpose is writing carefully and acting properly, never hiding, deleting, or evading: concealment is both the crime and the cover-up, and this skill refuses to help with either.
Ask for these if not provided:
Prevention training — a plausible adversarial reading of sample messages. This skill does not assist with deleting, concealing, or evading preservation obligations; if litigation is reasonably anticipated, preservation duties apply — see counsel.
[message, quoted] Highlighted as: [how it reads in a filing] · The pattern: [which habit produced it]
[The 4–6 recurring habits in these samples, each with its risk mechanism]
| Instead of | Write | Why |
|---|---|---|
| [Plus: the pick-up-the-phone list (what belongs in synchronous conversation — decisions still get documented properly afterward), and the escalate-properly note: raised-and-fixed is the best exhibit there is] |
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-simulatorsGuides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.