Loading...
Loading...
Found 209 Skills
Google Search Console indexing assistant. Use when the user wants to track page indexing status, compare sitemap against GSC indexed pages, manage submission tracking, or move false positives (pages indexed per URL Inspection but not yet in GSC export) to the indexed list. Maintains two tracking files (indexed.md, to-index.md) with prioritization support.
Guides director-level infrastructure capex accounting—capitalization policy and governance, WIP/CIP and project closeout, useful-life and impairment standards, capex forecast vs actual for data center and compute programs, board and audit narratives, SOX over fixed-asset and cloud-prepaid programs, and alignment with engineering and portfolio delivery. Use when setting capex accounting policy, reviewing material capitalization judgments, governing infrastructure asset programs, executive capex reporting, or audit steering for DC/compute investments—not for month-end JEs and CUR mapping (compute-accounting-manager), rack utilization (data-center-compute-supply-efficiency), facility design (data-center-design-execution-lead), or multi-site investment prioritization (data-center-portfolio-planning-execution-lead).
Systematic workflow for checking and responding to notifications. Use at session start and periodically. Covers prioritization, tone guidelines, and recording interactions.
Use Case 2.0 methodology by Ivar Jacobson. Covers use case slices, lightweight documentation, user story derivation, and value-driven prioritization. Modern approach to use case modeling for agile teams.
Triage CI failures and PR review comments using scripts/pr-status.js. Use when investigating failing CI jobs, flaky tests, or PR review feedback. Covers blocker-first prioritization (build > lint > types > tests), CI env var matching for local reproduction, and the Known Flaky Tests distinction.
Product Manager (Morgan). Use for PRD creation (greenfield and brownfield), epic creation and management, product strategy and vision, feature prioritization (MoSCoW, RICE), roa...
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).
Help non-technical stakeholders write clear, scoped requirements documents. Translates business needs into structured specs including user goals, workflows, and success criteria — but first guides the requester through prioritization, scope limits, and MVP phasing to prevent wishlist bloat. Output in Taiwan Traditional Chinese. Use this skill when your boss, PM, or stakeholder wants to define what a feature should do, write a PRD, plan a product, or describe requirements. It is also suitable when someone presents a large feature wishlist and needs help structuring and narrowing down its scope.
Expert product strategy and product marketing skill. Use when defining product vision, assessing product-market fit, sizing market opportunities, doing competitive positioning, building growth loops, designing PLG strategies, creating product marketing context, or using the Working Backwards methodology. Activates for: product strategy, product marketing, PMM, product manager, product management, growth product manager, working backwards, PR/FAQ, Amazon PR FAQ, product roadmap, product positioning, product-market fit, product launch, feature prioritization, TAM SAM SOM, market sizing, competitive moat, business model design, monetization strategy, north star metric, activation, retention, growth loops, freemium, PLG, product-led growth, growth experimentation, ICP context, marketing context document.
Structure a spoken PM product-sense answer with assumptions, segmentation, pain-point prioritization, and MVP tradeoffs. Use when practicing design, improve, or build-next interview questions.
Use when planning product roadmaps with Now/Next/Later horizons. Not for feature prioritization (use pm-prioritization).
Run a structured business analysis workflow: requirements elicitation with stakeholder interviews and MoSCoW prioritization, as-is/to-be process mapping with BPMN notation, data-driven analysis (CBA, SWOT, root cause), and production-ready documentation (BRD, FRD, user stories with INVEST acceptance criteria). Triggers on "gather requirements", "write user stories", "map business process", "BRD", "FRD", "gap analysis", "cost-benefit analysis", "facilitate workshop", "business requirements", "process mapping", "as-is to-be", "stakeholder interview", or "business analyst". For management consulting (issue trees, steerCo business cases, operating model), use business-consultant—not business-analyst. For business model canvas, market sizing, and unit economics research, use business-model-researcher. Human data / labeling platform PRDs: product-management-human-data-platform. Monetization PRDs and packaging: product-management-monetization.