doc-problem-statement
100 / 100 · Low risk
Fine to try.
Writes a Problem Statement naming who has the problem and in what situation, the evidence and cost behind it, what success looks like, and one "how might we" line. Use for "run doc-problem-statement", "write the problem statement", "what problem are we solving", "leadership saw a demo and wants it shipped", "the prototype is replacing the why", "frame the problem before the spec", "how might we", part of the Claude Docs for Product Managers Pack by 90n.
What this skill can do
We found nothing in the files we read that matches our rules. That does not prove the skill is safe: see the limits of static scanning.
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'doc-problem-statement' ] || [ -L ~/.agents/skills/'doc-problem-statement' ]; then echo 'A skill folder named doc-problem-statement already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/polar-bear-org/claude-skills' "$d" && git -C "$d" checkout --quiet '95f01806ca43f6ee788d0579743e35853b695930' -- 'packs/docs-for-product-managers-pack/skills/doc-problem-statement' && mkdir -p ~/.agents/skills && cp -R "$d"/'packs/docs-for-product-managers-pack/skills/doc-problem-statement' ~/.agents/skills/'doc-problem-statement' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'doc-problem-statement' ~/.claude/skills/'doc-problem-statement' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/polar-bear-org/claude-skills/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-07 | 95f0180 | 100 |