The 3 Claude Skills That Keep Product Work Moving
Product work has a documentation problem. You have an idea for a feature, you know what it needs to do, and then you spend a day writing a PRD that captures maybe 60% of what was in your head. Or you skip the document entirely and the engineers build something adjacent to what you meant.
The Product pack has 4 skills. Here are the three that close the gap between having an idea and actually shipping it.
/prd-writer
A product requirements document is one of those things everyone agrees matters and almost no one writes well. It takes too long, the structure is always slightly wrong for the specific feature, and by the time it's done you've lost the momentum you had when the idea was fresh.
/prd-writer takes a feature idea and writes a full PRD — problem statement, goals, user stories, requirements, edge cases, success metrics, and what's explicitly out of scope. Everything an engineer or designer needs to build the right thing without three follow-up conversations.
--technical goes deeper on implementation details and technical constraints for cases where the engineers need more specificity. --one-pager compresses everything into a single-page format for smaller features where a full PRD is more than the situation requires.
The PRD is the difference between building the right thing and building the thing you thought you described.
/user-story
Features that go into a backlog as vague descriptions come out of it as vague builds. "As a user I want to see my dashboard" is not a user story — it's a wish. A real story has acceptance criteria, edge cases accounted for, and a clear definition of done that both the engineer and the PM agree on before work starts.
/user-story breaks any feature into properly structured user stories with acceptance criteria and effort sizing. Each story is scoped tightly enough that one engineer can own it start to finish without ambiguity.
--epic groups related stories under an epic structure when the feature is large enough to need that hierarchy. --dev-brief adds a short technical context section to each story so engineers aren't starting cold.
Vague tickets produce vague software. This fixes the ticket before the work starts.
/feature-prioritization
Backlog grooming sessions where nothing actually gets cut are a particular kind of time waste. Everyone argues for their feature, the list stays long, and the team leaves without a real decision about what gets built next.
/feature-prioritization scores and ranks a backlog by impact and effort, then makes a hard call — build it or kill it — for every item. No hedging. The --ice flag uses the ICE framework (Impact, Confidence, Ease) if you want a structured scoring method behind the ranking.
What makes it useful is the constraint. When something has to give a definitive answer rather than a nuanced "it depends," you get a prioritized list you can actually act on instead of a framework you'll revisit next quarter.
The best backlogs are short. This helps you get there.
All four skills in the Product pack — including /launch-checklist for phased go-to-market planning from T-14 to T+3 — are available to Skills Pack members. They ship as SKILL.md files — drop them into ~/.claude/skills/ and invoke with the slash command in Claude Code, Cursor, or Codex.
Next up: the Legal pack — NDAs, contract review, privacy policies, and plain-English clause explanations.