cmd-product-pm

Diagnose projects and surface PRDs, roadmaps, and launch plans.

2|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/jlaws/dotfiles --skill cmd-product-pm
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cmd-product-pm
Source: https://github.com/jlaws/dotfiles/tree/main/.agents/skills/cmd-product-pm
Command: npx skills add https://github.com/jlaws/dotfiles --skill cmd-product-pm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams often need structured guidance to rapidly define and validate product direction, capture requirements, and plan launches without getting bogged down in architecture or KPIs.

Core Features & Use Cases

  • Diagnostic context gathering to determine project type and relevant artifacts (PRD, requirements, roadmap, specs).
  • Artifact discovery and assessment by checking for analytics setups, user research artifacts, and scope overview.
  • Guided product management consultation to produce PRDs, roadmaps, and launch plans based on findings.

Quick Start

Describe your project area and ask me to prepare a PRD, roadmap, or launch plan.

Frequently Asked Questions about cmd-product-pm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a PRD for a new product feature?

To write a PRD, describe your project area and the tool will scan for existing analytics, user research, and specs to provide structured product management guidance and generate the requirements document.

How do I create a product roadmap from existing project artifacts?

Creating a product roadmap involves scanning your project for existing specs and user research artifacts to evaluate what to build, allowing the tool to structure your roadmap and launch planning based on those findings.

What do I need to prepare a product launch plan?

Preparing a launch plan requires describing your project area and scope, which triggers a diagnostic scan for relevant product artifacts like PRDs and analytics setups to guide the launch planning process.

What is the best way to define scope before writing requirements?

Defining scope requires diagnostic context gathering to assess project type and discover relevant artifacts like user research and analytics, ensuring your requirements and PRDs are validated before architecture planning.

Can I use this for evaluating what to build without existing KPIs?

Yes, evaluating what to build works by performing artifact discovery and assessment to check for analytics setups and user research, providing structured product direction guidance even without predefined KPIs.

Does this product management tool work for user research discovery?

User research discovery is supported through artifact scanning, checking your project for existing research and analytics setups to inform scope overview and guide subsequent PRD and roadmap generation.