jochenyang/product-manager
skills/product-manager/SKILL.md
Product requirements analysis and planning for structured PRD outputs. Use when requirements are mostly known and user needs prioritization, PRD refinement, roadmap, and product tradeoff decisions.
$ install --global
skillsauthnpx skillsauth add jochenyang/jochen-ai-rules product-managerInstall 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: Apr 20, 2026, 10:14 AM61.7s1 file scanned
SKILL.md
- name:
- product-manager
- description:
- Product requirements analysis and planning for structured PRD outputs. Use when requirements are mostly known and user needs prioritization, PRD refinement, roadmap, and product tradeoff decisions.
Product Manager
Analyze user requirements, plan product features, output structured PRD documents.
Boundary With Other Skills
- Use
product-managerfor planning, prioritization, market framing, and PRD refinement. - Use
requirements-interviewfirst when requirements are unclear and need multi-round Q&A discovery. - If both are needed: run
requirements-interviewto clarify scope, then useproduct-managerto finalize priorities and roadmap.
Core Capabilities
- Requirements Analysis: Gather and analyze user needs through research and interviews
- Market Research: Search and analyze market trends, competitors, and industry data
- Competitive Analysis: Research competitors' products, features, pricing strategies
- PRD Writing: Create structured product requirement documents
- User Stories: Break down features into actionable user stories with acceptance criteria
- Feature Prioritization: Use frameworks like RICE, MoSCoW for prioritization
- MVP Definition: Define minimum viable product scope and roadmap
Common Request Patterns
- Competitive Research: Compare onboarding UX, pricing tiers, and positioning
- Tech Tradeoffs: Evaluate stack choices with scalability, cost, and developer experience
- Risk & Compliance: Identify regulatory risks for new features
- Feedback Synthesis: Turn feedback into feature ideas and priorities
- Experiment Planning: Propose A/B tests with hypotheses and success metrics
- Launch Communication: Draft release notes, GTM FAQ, and value propositions
PRD Core Structure
- Product Overview: Background, goals, users, scenarios
- Market Analysis: Competitive analysis, differentiation advantages
- User Research: User personas, pain point analysis
- Functional Requirements: Feature list, priorities, user stories
- Non-Functional Requirements: Performance, security, compatibility
- Implementation Plan: Milestones, risk assessment
Research Capabilities
Market Research
Use web search to gather:
- Industry trends and market size data
- Competitor product features and strategies
- User behavior patterns and preferences
- Regulatory and compliance requirements
Competitive Analysis
Analyze competitors across:
- Product features and positioning
- Pricing models and monetization strategies
- User reviews and feedback
- Strengths and weaknesses
User Research
Search for:
- User pain points and unmet needs
- Similar solutions and alternatives
- Best practices and design patterns
- User feedback and testimonials
Quality Standards
- Provide confidence level (0-100%) for requirements analysis
- Avoid exaggerated terms like "best" or "perfect"
- Clearly state assumptions, uncertainties, potential risks
- Cite sources for market data and competitive analysis
- Distinguish between verified facts and hypotheses
Boundaries
Focus on requirements analysis and product planning, not UI design or technical implementation.
When NOT to Use
- Requirements are unclear → use
requirements-interviewfirst - Writing implementation code → use
developer - Frontend UI design → use
frontend-design - API design → use
api-designer - Database schema design → use
database-engineer - Technical architecture planning → use
dev-planner
Helper Scripts
Always run --help first to see usage.
scripts/analyze-market.sh- Market research and competitive analysisscripts/generate-stories.sh- Generate user stories from requirements
Detailed References
./workflows/prd-template.md- PRD template guide./workflows/user-story-mapping.md- User story mapping workshop guide
Escalation Rules
Pause and ask the owner before:
- reframing roadmap or priority decisions that materially change product direction
- filling in missing market or user evidence as if it were confirmed fact
- expanding planning work into design or implementation commitments outside this skill's boundary
Final Output Contract (MANDATORY)
Every use of this skill should end with:
Skill Fit- why product planning is the right modePrimary Deliverable- PRD, prioritization, roadmap, or story outputExecution Evidence- assumptions, inputs, and analysis usedRisks / Open Questions- evidence gaps, priority tradeoffs, or dependency concernsNext Action- the next clarification, review, or execution step
Related Skills
jochenyang/reflect
databases
VerifiedTrustedCommunity
Review current conversation, analyze tasks, errors, and user feedback, extract learning opportunities for skill improvement. Use when user says "reflect", "review session", "what did we learn", "session summary", or after completing a complex task.
20SKILL.mdUpdated Apr 6, 2026
jochenyang/handoff
development
VerifiedTrustedCommunity
Create and resume structured manual session handoffs for long-running development work. Use when approaching context limits, before manual reset, before switching models or IDEs, after a milestone, or when automatic compact would lose important implementation state.
20SKILL.mdUpdated Apr 6, 2026
jochenyang/frontend-design
development
VerifiedTrustedCommunity
Implement distinctive, production-grade frontend UI code with strong visual direction, motion systems, local media asset generation, conversion-aware copy, and polished frontend execution. Use when building landing pages, marketing sites, product pages, dashboards, motion-heavy interfaces, or frontend experiences that need real assets and compelling copy.
20SKILL.mdUpdated Apr 6, 2026
jochenyang/context-codebase
development
VerifiedTrustedCommunity
Project context engine for repo orientation, cached handoff, and task-focused code retrieval.
20SKILL.mdUpdated Apr 6, 2026