Claude skillsfor prds, specs & docs

The 6 skills and connectors we'd install first, in order. Hand-picked from product managers tools reviewed on SkillHub.

Task

PRDs, specs & docs

6 picks · install in this order

Prd DevelopmentSkill
Build a structured PRD that connects problem, users, solution, and success criteria. Use when turning discovery notes into an engineering-ready document for a major initiative.
Prd WriterSkill
The PRD isn't dead. The bad PRD is dead. AI killed the 10-page PRD — no one read those. The modern PRD is lighter, sharper, and example-heavy. The PRD evolves through stages.
PrdSkill
Generate a concise, structured PRD from a product idea. NOT a 20-page doc — 1-2 pages that force clarity.
Refine SpecSkill
Review a PRD or spec for completeness, ambiguity, edge cases, and acceptance criteria quality. Present structured findings by severity and offer to fix issues directly.
Working BackwardsSkill
Use when asked to "working backwards", "PR/FAQ", "Amazon PR/FAQ", "write a press release", "define a new product", or "write a customer-focused PRD".
Problem StatementSkill
Write a user-centered problem statement with who is blocked, what they are trying to do, why it matters, and how it feels. Use when framing discovery, prioritization, or a PRD.

02Workflow recipes

Turn a gut feeling into a problem worth solving, backed by customer interviews and a clear opportunity map.

Go from an approved idea to a reviewed spec and ready-to-build tickets in your tracker.

Turn a week of scattered work into a clean 3P (Progress / Plans / Problems) update your team will actually read.

We're actively curating this list. If your skill or MCP server belongs here, submit it and we'll review within a few days.