Customer Signal Review
Synthesizes recent interviews, tickets, reviews, calls, and notes into evidence-linked themes and product implications.
Assets tagged with product.
Synthesizes recent interviews, tickets, reviews, calls, and notes into evidence-linked themes and product implications.
Derive a complete, source-traceable inventory of applications, views, subviews, overlays, modes, and required states from a PRD or functional requirements. Use for product-surface planning, information architecture, UX scope, wireframe coverage, or design handoff. Do not use when the requested output is the wireframes or a design-tool generation prompt.
Derive a complete, source-traceable inventory of applications, views, subviews, overlays, modes, and required states from a PRD or functional requirements. Use for product-surface planning, information architecture, UX scope, wireframe coverage, or design handoff. Do not use when the requested output is the wireframes or a design-tool generation prompt.
Turns strategy and constraints into a sequenced feature roadmap with assumptions, dependencies, risks, and measurable outcomes.
Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
Writes Jira-ready epics and stories with acceptance criteria, dependencies, release notes, and implementation handoff notes.
Creates a KPI tree that connects company goals to product outcomes, input metrics, leading indicators, and instrumentation needs.
Build a KPI tree that connects a strategic goal to an outcome metric, controllable input metrics, guardrails, owners, and instrumentation. Use for product strategy, metric design, OKR measurement, north-star decomposition, initiative prioritization, or diagnosing why a business outcome is moving.
Creates a KPI tree that connects company goals to product outcomes, input metrics, leading indicators, and instrumentation needs.
Build a KPI tree that connects a strategic goal to an outcome metric, controllable input metrics, guardrails, owners, and instrumentation. Use for product strategy, metric design, OKR measurement, north-star decomposition, initiative prioritization, or diagnosing why a business outcome is moving.
Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.
Builds a clear prioritization rubric using impact, effort, confidence, risk, strategic fit, and customer evidence.
Create, screen, research, and rank distinctive product, service, feature, platform, or company names. Use when the user wants naming strategy, creative naming territories, brainstormed candidates, competitive or company-name collision checks, preliminary trademark screening, domain-availability research, naming scorecards, or a decision-ready shortlist with rationales and risks.
Estimates project scope, timeline, staffing, confidence, risks, and tradeoffs from requirements or discovery notes.
Creates specs before coding. Use when starting a new project, feature, or significant change and no specification exists yet. Use when requirements are unclear, ambiguous, or only exist as a vague idea. Use when a single requirement spans several independently testable capabilities and needs decomposing into a capability map of modules before specifying.
Stakeholder Synthesis workflow that groups context collection, production, review, and packaging tasks into one deliverable.
Turn product feedback from interviews, tickets, reviews, surveys, sales notes, or usage evidence into traceable themes, segment-specific insights, prioritized opportunities, and a research follow-up plan. Use for voice-of-customer synthesis, feedback analysis, churn-reason analysis, or deciding what product problem to investigate next. Do not use to treat anecdotes as demand, invent prevalence, or convert feedback directly into an implementation roadmap.
Turn product feedback from interviews, tickets, reviews, surveys, sales notes, or usage evidence into traceable themes, segment-specific insights, prioritized opportunities, and a research follow-up plan. Use for voice-of-customer synthesis, feedback analysis, churn-reason analysis, or deciding what product problem to investigate next. Do not use to treat anecdotes as demand, invent prevalence, or convert feedback directly into an implementation roadmap.
Splits product requirements into technical requirements, API needs, data model changes, and rollout constraints.
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
Audits an existing pm-skills skill against structural conventions and quality criteria. Produces a structured validation report with pass/fail checks, severity-graded findings, and actionable recommendations. Use when checking whether a skill meets repo standards before shipping or after making changes.
Generates professional presentations from a JSON deck specification using 18 slide types with dark/light variants, content-to-layout decision logic, and calibrated character limits. Ships with a default professional theme and supports custom themes via utility-slideshow-themer.
Checks for newer pm-skills releases, compares local vs. latest version, previews what would change, and updates local files after user confirmation. Generates a structured update report documenting changed files, new capabilities, and the value delta between versions. Use when you want to bring a local pm-skills installation up to date.
Turn a complete beginner's app idea into a buildable plan, then keep them oriented while they build. Use it whenever someone who has never coded wants to build or "vibe code" an app, has an idea but no idea where to start, or wants it turned into a plan, MVP scope, tech stack, user flows, or blueprint. ALSO use it when a non-coder needs build-time basics: what Git and GitHub are, making an account, "commit and push," local vs. staging vs. production, putting an app online (deploy/ship), or keeping API keys safe. AND use it in Checkup Mode when someone who built with AI says it became a mess, the AI keeps breaking things or going in circles, they're scared to touch their code, or they ask "is my code organized" or "can you clean it up." Built for people who don't know what an API, database, or GitHub is, so reach for it when they never say "plan" or "architecture." Not for an experienced dev debugging, refactoring, or setting up CI/CD.