Building alone means wearing every hat — including product manager. I keep hitting the same walls: competitor research is exhausting, feature prioritization feels like guesswork, and I don't have a PM team to lean on.
So I built a Product Management skill for Claude Code. It handles the PM workflow I was doing manually — researching competitors, scoring feature gaps, generating PRDs, and creating GitHub Issues — all from the terminal.
The key piece is a WINNING filter that scores every feature gap on pain, timing, execution capability, and defensibility. It takes 50+ potential features and narrows them to 3–5 high-conviction priorities. No more building something just because "it would be cool."
It also pairs with spec-kit for implementation handoff — the PRD creates a GitHub Issue, and spec-kit picks it up from there. One workflow, no context switching.
What it looks like in practice
I ran /pm:prd on a new feature module for one of my products. Claude analyzed the codebase, identified reusable components (approval workflows, audit trails, role-based access), and generated a full PRD with user stories, functional requirements, and architecture reuse analysis.
The PRD was saved locally and created as a GitHub Issue automatically — with MVP scope, P0/P1/P2 priorities, and a breakdown of what I could reuse vs. build new.
From "I want to add this feature" to a structured GitHub Issue with a technical spec ready to generate — in one session.
Full writeup
The full post covers all the commands (/pm:analyze, /pm:landscape, /pm:gaps, /pm:prd), the WINNING filter scoring breakdown, the spec-kit integration, data storage, and a step-by-step walkthrough with screenshots.
Read the full writeup on Build Signals
Links:
Top comments (0)