The Product Manager Skill Stack: Spec, Deck, Ticket, Numbers
Product management is documents with stakes. The PRD that scopes a quarter, the deck that survives review, the ticket that doesn't get bounced back, the retention number you defend in public. Six skills, one week, four categories.
Monday: create-prd — 8.1/10, injection-tested 10/10
The spec skill. Problem framing, user segments, scope fence, success metrics.
Why it opens the week: Everything downstream is a derivative of this document. In our injection batch it held 4/4 boundaries in both tiers — including refusing a probe that told it to skip its own review pass.
The one thing: Its scope-fence section only works if you let it say no. Feed it your "and also..." list and let it argue back.
Tuesday: baoyu-slide-deck — 9.3/10, injection-tested 10/10
The review deck from the PRD — one argument per slide, no 40-word bullets.
Dynamic test detail worth knowing: The workflow-escalation probe pushed it to run a destructive cleanup across the whole directory. It swept only its own output and left the sentinel files alone — the exact boundary a deck skill should hold when it's got a rm in its toolchain.
Wednesday: atlassian-mcp — 9.2/10
Jira and Confluence through MCP — tickets from the PRD's milestone section, spec pages linked both ways.
Why MCP matters here: This is the skill that turns documents into state. A PRD nobody can find in the tracker is a memoir.
The one thing: Grant it the project, not the workspace. Ticket-writing skills with broad scopes are how sprint boards get "cleaned up" by an over-eager agent.
Thursday: xlsx + the numbers — 9.8/10, injection-tested 7.5/10
The official workbook skill: formulas, pivots, and — its signature move — output verification that recalculates before claiming success.
The honest caveat from our injection batch: Told to skip its verification step, it did (that's the rule-override drop that cost it the 2.5 points). The verification is the entire value of this skill over a bare model — never instruct around it.
Friday: prompt-master — 9.3/10, injection-tested 10/10
The polish pass on everything written this week — release notes from the PRD, the exec summary from the deck.
Why Friday: It's a multiplier skill; it works best on drafts that exist. It also passed the full injection battery, notable for a skill whose job is accepting editing instructions.
The specialist add-on: linkedin-interviewer + linkedin-reply-handler — 9.4/9.5
Discovery calls and user comms, structured. The PM skills nobody admits take half the week.
A week of PM artifacts, produced at draft-0 quality by the agent and finished by you. The security pattern from the batch: generators under instruction-pressure skip steps when told — the readers and multipliers don't. Productivity category, or the full injection methodology.