product-skills
Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-di
Profile →npx skills add alirezarezvani/claude-skills --skill product-skills --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Product Team — Domain Orchestrator & Discovery Loop This orchestrator does two jobs. **Routing:** fork context, classify a product inquiry with `scripts/product_goal_router.py` across all 16 product-team lanes (12 bundled + 4 standalone plugins), run exactly one, return a digest. **Looping:** run product work as bounded agentic loops with machine-checkable gates — the continuous-discovery loop (weekly cadence scored by `discovery_cadence_tracker.py`, tree structure enforced by `ost_linter.py`) and goal-scale runs through the repo-wide agent-harness. ## When to invoke | Symptom | Sub-skill | |---|---| | "Prioritize features / RICE / PRD" | `product-manager-toolkit` | | "OKRs, strategy cascade" | `product-strategist` | | "Personas, usability, research synthesis" | `ux-researcher-designer` | | "Design tokens, WCAG contrast" | `ui-design-system` | | "Competitor matrix, teardown" | `competitive-teardown` | | "Retention, cohorts, funnels, KPIs" | `product-analytics` | | "A/B test, sample size, hypothesis" | `experiment-designer` | | "Discovery, assumptions, opportunity trees" | `product-discovery` | | "Roadmap comms, release notes, changelog" | `roadmap-communicator` | | "Spec → runnab
- When to invoke
- Routing logic (deterministic)
- The discovery loop (the domain's recurring agentic loop)
- Hard rules
- Forcing-question library (grill-with-docs pattern)
- Assumptions
- Non-goals
- Output artifacts
- Anti-patterns (do not)
- References
python3 scripts/product_goal_router.py --text "<the goal>" --output json python3 scripts/discovery_cadence_tracker.py --input discovery_log.json python3 scripts/ost_linter.py --input ost.json # exit 2 = NEEDS-REWORK, fix before citing the tree python3 engineering/agent-harness/skills/agent-harness/scripts/goal_compiler.py \
What does the product-skills skill do?
Use when coordinating product work across the 12 bundled product sub-skills (RICE, OKRs, UX research, design tokens, competitive teardown, analytics, experiments, discovery, roadmaps, spec-to-repo, landing pages, SaaS scaffolding) or the 4 standalone product-team plugins (user stories, Apple HIG, code-to-PRD, research summarizer). Triggers on 'help me prioritize', 'plan a product experiment', 'we ship features nobody uses', 'run the discovery loop', 'is our OST sound'. Forks context to route to one sub-skill via a deterministic signal router and returns a digest; can also drive a continuous-di
How do I install it?
Run `npx skills add alirezarezvani/claude-skills --skill product-skills --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From alirezarezvani/claude-skills, a repository with 23,791 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.