ooiyeefei/product-management
plugins/product-management/skills/product-management/SKILL.md
This skill should be used when the user asks to "analyze my product", "research competitors", "find feature gaps", "create feature request", "prioritize backlog", "generate PRD", "plan roadmap", "what should we build next", "competitive analysis", "gap analysis", "sync issues", or mentions product management workflows. Provides AI-native PM capabilities for startups with signal-based feature tracking, the WINNING prioritization filter, and GitHub Issues integration with deduplication.
$ install --global
skillsauthnpx skillsauth add ooiyeefei/ccc product-managementInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 6, 2026, 6:27 AM247.0s7 files scanned
SKILL.md
- name:
- product-management
- description:
- This skill should be used when the user asks to "analyze my product", "research competitors", "find feature gaps", "create feature request", "prioritize backlog", "generate PRD", "plan roadmap", "what should we build next", "competitive analysis", "gap analysis", "sync issues", or mentions product management workflows. Provides AI-native PM capabilities for startups with signal-based feature tracking, the WINNING prioritization filter, and GitHub Issues integration with deduplication.
- version:
- 0.2.0
Product Management Skill
AI-native product management for startups. Transform Claude into an expert PM that processes signals, not just feature lists.
Core Philosophy
WINNING = Pain × Timing × Execution Capability
Filter aggressively from 50 gaps to 3-5 high-conviction priorities. Expert PMs track signals with confidence scores, timestamps, and velocity.
Commands Quick Reference
| Command | Purpose |
|---------|---------|
| /pm:analyze | Scan codebase + interview for product inventory |
| /pm:landscape | Research competitor landscape |
| /pm:gaps | Run gap analysis with WINNING filter |
| /pm:file | Batch create GitHub Issues for approved gaps |
| /pm:prd | Generate PRD and create GitHub Issue |
| /pm:sync | Sync local cache with GitHub Issues |
Agents
This plugin provides specialized agents for autonomous tasks:
| Agent | Triggers On | Purpose |
|-------|-------------|---------|
| research-agent | "research [competitor]", "scout [name]" | Deep autonomous web research |
| gap-analyst | "find gaps", "what should we build" | Systematic gap identification with scoring |
| prd-generator | "create PRD for [feature]" | Generate PRD + create GitHub Issue |
Data Storage
All data stored in .pm/ folder at project root:
.pm/
├── config.md # Positioning, scoring weights
├── product/ # Product inventory, architecture
├── competitors/ # Competitor profiles
├── gaps/ # Gap analyses with scores
├── requests/ # Synced GitHub Issues (for dedup)
├── prds/ # Generated PRDs
└── cache/last-updated.json # Staleness tracking
See references/data-structure.md for complete file templates.
WINNING Filter Scoring
Hybrid scoring approach - Claude suggests researchable criteria, user scores domain-specific:
| Criterion | Scorer | Source | |-----------|--------|--------| | Pain Intensity (1-10) | Claude | Review sentiment, support data | | Market Timing (1-10) | Claude | Search trends, competitor velocity | | Execution Capability (1-10) | User | Architecture fit, team skills | | Strategic Fit (1-10) | User | Positioning alignment | | Revenue Potential (1-10) | User | Conversion/retention impact | | Competitive Moat (1-10) | User | Defensibility once built |
Total: X/60 → Recommendation:
- 40+ → FILE (high conviction)
- 25-39 → WAIT (monitor)
- <25 → SKIP (not worth it)
See references/winning-filter.md for detailed scoring criteria.
Deduplication & Sync
Prevent duplicate feature requests by syncing with GitHub Issues:
On Session Start
- Check
.pm/cache/last-updated.jsonfor staleness - If >24 hours since last sync, prompt for
/pm:sync
/pm:sync Process
- Fetch all GitHub Issues with
pm:*labels viagh issue list --json - Update
.pm/requests/[issue-number].mdfor each issue - Update
last-updated.jsontimestamp
Deduplication During Gap Analysis
- Load existing issues from
.pm/requests/ - For each new gap, fuzzy match against existing:
- Title similarity (Levenshtein): 40% weight
- Keyword overlap: 30% weight
- Label match: 20% weight
- Description similarity: 10% weight
- Mark gaps as:
- EXISTING (>80% match) → Show linked issue
- SIMILAR (50-80%) → Warn, ask user
- NEW (<50%) → Proceed normally
Output Format
| Gap | WINNING | Status | Match |
|-----|---------|--------|-------|
| OAuth support | 47/60 | EXISTING | #42 (95%) |
| Dark mode | 38/60 | NEW | - |
Flow Summaries
Product Analysis (/pm:analyze)
- Scan codebase for features (routes, components, APIs, models)
- Interview user for business context
- Generate inventory with technical moats and debt flags
- Save to
.pm/product/
Competitive Intelligence (/pm:landscape, /pm:scout [name])
- Research competitors via WebFetch/WebSearch
- Categorize features: Tablestakes, Differentiators, Emerging, Deprecated
- Save profiles to
.pm/competitors/
Gap Analysis (/pm:gaps)
- Load product inventory + competitor profiles
- Check staleness (>30 days → prompt refresh)
- Sync with GitHub Issues for deduplication
- Identify all gaps, score with WINNING filter
- Mark as NEW/EXISTING/SIMILAR
- Save to
.pm/gaps/[date]-analysis.md
Feature Filing (/pm:review, /pm:file)
/pm:review- Walk through gaps, decide FILE/WAIT/SKIP/pm:file- Create GitHub Issues for approved gaps (skips duplicates)- Apply labels:
pm:feature-request,winning:*,priority:*
PRD Generation (/pm:prd [feature])
- Load feature context from gap analysis or GitHub Issue
- Generate PRD: Problem, User Stories, Acceptance Criteria, etc.
- Save to
.pm/prds/[slug].md - Create GitHub Issue with PRD content as feature request
Backlog & Roadmap (/pm:backlog, /pm:roadmap)
- Fetch open issues with
pm:labels - Sort by WINNING score or RICE
- Organize into Now/Next/Later priorities
GitHub Integration
Labels (Auto-Created)
pm:feature-request pm:gap-identified pm:competitor-intel
priority:now priority:next priority:later
winning:high (40+) winning:medium (25-39) winning:low (<25)
Prerequisites
- GitHub CLI (
gh) installed and authenticated - Run
gh auth statusto verify
See references/github-labels.md for label definitions.
See references/issue-template.md for issue format.
Integration with spec-kit
This plugin handles WHAT to build and WHY (product discovery). For HOW to build it, use spec-kit:
PM Plugin → GitHub Issue → spec-kit
/pm:file Creates issue /speckit.specify
/pm:prd Creates issue /speckit.plan → /speckit.implement
The GitHub Issue IS the handoff—no separate command needed.
Staleness Handling
PM data ages. Handle proactively:
- Competitor data >30 days: Prompt refresh before gap analysis
- Gap analysis >14 days: Warn when viewing backlog
- GitHub sync >24 hours: Suggest
/pm:syncon session start
⚠️ Competitor data is 45 days old. Run `/pm:landscape` to refresh.
Additional Resources
Reference Files
references/winning-filter.md- Detailed WINNING scoring criteriareferences/github-labels.md- Label definitions and colorsreferences/issue-template.md- GitHub Issue templatereferences/data-structure.md- Complete.pm/folder structure
Example Files
examples/gap-analysis.md- Sample gap analysis outputexamples/competitor-profile.md- Sample competitor profile
Related Skills
ooiyeefei/self-improving-systems
testing
VerifiedTrustedCommunity
Decide whether your agent actually needs persistent memory, feedback loops, or closed-loop learning, then design the smallest thing that pays for itself. Use when the user says "add memory", "give my agent context management", "make my agent learn", "self-improving / closed-loop", "Reflexion / mem0 / Letta / MemGPT", "AriGraph", "agent memory architecture", "long-term memory for chatbot", "why does my agent keep forgetting / making the same mistake", "fine-tune from agent traces", or asks for a memory schema / experience store / reward model. Filters ruthlessly — most teams want a state cache, not memory + learning. Default position is scratchpad-only with a stateless agent shipped first.
441SKILL.mdUpdated May 9, 2026
ooiyeefei/agentic-system-design
tools
VerifiedTrustedCommunity
Prescriptive Q&A workflow for designing agentic pipelines, multi-model councils, sub-agent hierarchies, and tool-loop hardening for any domain. Use when the user asks to "design an agent", "design a multi-agent system", "should I use a council/debate", "build a [domain] review agent" (HAZOP, finance, tutorial, marketing, compliance, accounting), "real agency vs workflow", "how to add sub-agents", "AI for [domain] review", or names patterns like "orchestrator-worker", "evaluator-optimizer", "Magentic", "ReAct", "plan-and-execute", "handoffs". Walks the user through 12 stages one question at a time and emits a buildable design doc with citations. Do NOT use for general coding questions, single-shot prompt tuning, or bare "use Claude to do X" requests with no agency requirement.
441SKILL.mdUpdated May 9, 2026
ooiyeefei/landing-page-gtm
development
VerifiedTrustedCommunity
Build and update high-converting SaaS landing pages with GTM-aware marketing copy, competitive positioning, and sales psychology. Use when creating new landing pages, rewriting feature cards, updating marketing copy, launching product pages, or transforming technical features into customer-facing sales language. Triggers on "build landing page", "update feature cards", "rewrite marketing copy", "create product page", "launch page", "GTM", "sales copy", "competitive positioning", or when converting product features into conversion-focused web pages.
441SKILL.mdUpdated May 6, 2026
ooiyeefei/htmldrop
development
VerifiedTrustedCommunity
This skill should be used when the user asks to "share this HTML", "publish HTML", "get a link for this file", "share this report", "make this shareable", "upload this HTML", or wants to publish any HTML artifact for others to view. ALSO use it for collaborative review on an HTML doc/spec/report — triggers include "get feedback on this", "let reviewers comment", "collect feedback", "share for review", "let people annotate this", "synthesize the feedback", "converge the feedback", "what did reviewers say", "incorporate the comments", or "improve this from the feedback". Wraps Surge.sh for zero-cost hosting with guided privacy options, plus an embedded annotation + AI converge workflow.
428SKILL.mdUpdated May 15, 2026