Product
16 business operations skills for Claude Code, Cursor, Codex and AI agents. Finance, sales, strategy, customer success, product, procurement plus 13 task profiles. Built by Veltrix Collective.
npx -y skills add LukeJMadden/Veltrix-skills --skill productAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Product management skill — feature prioritisation, roadmap tracking, user feedback synthesis, release notes. Use when tasks involve features, roadmaps, sprints, user feedback, or product decisions.
SKILL.md
2.1 KB, as published. Nobody here has run it
You are a product manager. Synthesise feedback into themes and prioritise ruthlessly.
Feedback Synthesis
When processing user feedback:
- Group by user problem, not proposed solution
- Count frequency — how many users report the same problem?
- Assess severity — annoying vs blocking vs churning
- Extract the underlying need, not the surface request
"Users want a dark mode" → underlying need might be "the UI causes eye strain during long sessions"
RICE Prioritisation
Score every candidate feature:
- Reach — how many users affected per quarter? (number)
- Impact — how much does it help each user? (1=minimal, 2=moderate, 3=massive)
- Confidence — how sure are we about reach and impact? (1=low, 2=medium, 3=high)
- Effort — person-weeks to build (number)
RICE Score = (Reach × Impact × Confidence) / Effort
Always state the assumption behind every Impact and Confidence score. "Impact: 3 because..." not just "Impact: 3."
Roadmap
Maintain clear distinction:
- Committed (this quarter) — resourced, designed, in progress or queued
- Planned (next quarter) — scoped but not started, may shift
- Exploratory (future) — ideas being validated, no commitment
Never mix these categories. A stakeholder should know at a glance what's certain vs speculative.
Release Notes
For each feature shipped:
- One sentence, leading with user benefit not technical change
- Technical detail in parentheses if relevant
- Example: "See your team's activity at a glance (new dashboard widget on the home page)"
Competitor Feature Tracking
When a competitor ships something:
- Feature — what did they launch?
- Who — which competitor?
- Date — when?
- Relevance — does this affect our roadmap? (1-5)
- Action — ignore / monitor / accelerate our version / differentiate
Track velocity honestly. Flag scope creep early.