Loading...
Loading...
Found 101 Skills
Creates a comprehensive Product Requirements Document that aligns stakeholders on what to build, why, and how success will be measured. Use when specifying features, epics, or product initiatives for engineering handoff.
Expert platform and API product management guidance for developer-focused products. Use when planning API product strategy, designing APIs, improving developer experience (DX), creating developer documentation, building SDKs, planning API versioning and deprecation, building developer communities, creating integration marketplaces, or measuring platform health. Covers REST, GraphQL, webhooks, and platform ecosystems.
WooCommerce REST API - products, orders, customers, webhooks
This skill should be activated when the user requests to "create PRD", "write product requirements document", "generate PRD", "new PRD" (either in Chinese or English), or mentions "product requirements document" or "PRD template". It automatically generates comprehensive Chinese PRD documents in accordance with 2026 best practices.
Product management frameworks for business cases, market analysis, strategy, prioritization, OKRs/KPIs, personas, requirements, and user research. Use when building ROI projections, competitive analysis, RICE scoring, OKR trees, user personas, PRDs, or usability testing plans.
Prompt for creating Product Requirements Documents (PRDs) for new features, based on an Epic.
Structurally deconstruct competitors from four dimensions: strategy, functionality, experience, and growth, and output referenceable points, non-replicable points, and differentiation suggestions. Use this Skill when users say "competitor analysis", "competitor deconstruction", "help me analyze competitors", "take a look at these competitors", "compare with competitors", "benchmarking analysis", "how to do differentiation", or when users provide a list of competitors and require systematic analysis. Also applicable for: users upload competitor screenshots/links/experience reports and require structured deconstruction; users require comparison of gaps between their own products and competitors; users want to find differentiation entry points. Not applicable for: pure requirement document writing (use prd-writer), pure priority sorting (use prioritization-engine), pure user research design (use survey-designer).
Aha! integration. Manage data, records, and automate workflows. Use when the user wants to interact with Aha! data.
Creates a clear problem framing document with user impact, business context, and success criteria. Use when starting a new initiative, realigning a drifted project, or communicating up to leadership.
Specifies requirements for an analytics dashboard including metrics, visualizations, filters, and data sources. Use when requesting dashboards from data teams, defining KPI tracking, or documenting reporting needs.
Create or maintain STRATEGY.md - the product's target problem, approach, users, key metrics, and tracks of work. Use when starting a new product, updating direction, or when prompts like 'write our strategy', 'update the roadmap', 'what are we working on', or 'set up the strategy doc' come up. Also triggers when ce-ideate, ce-brainstorm, or ce-plan need upstream grounding and no strategy doc exists yet.
Framework for structured product decision-making. Use when facing complex tradeoffs, aligning stakeholders, documenting decisions, or choosing between multiple valid approaches.