pm-collect

Collect and organize raw product discovery materials from multiple sources.

1|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/Wcof/PMSkill --skill pm-collect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-collect
Source: https://github.com/Wcof/PMSkill/tree/main/skills/discovery/pm-collect
Command: npx skills add https://github.com/Wcof/PMSkill --skill pm-collect

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the early-stage product discovery problem of fragmented, incomplete, and hard-to-trace input materials. It gathers raw context from conversation, URLs, project files, git history, and optional knowledge bases so a product manager can start refinement with a fuller evidence base instead of guesswork.

Core Features & Use Cases

  • Multi-source material collection: Scans four evidence sources in priority order: conversation context, project repository, extracted URLs, and an optional knowledge base.
  • Structured aggregation with traceability: Groups findings by material type, removes duplicates, records source paths, and explicitly marks supporting or conflicting relationships between materials.
  • Project-aware discovery support: Inspects README, docs, config files, commit history, TODO or FIXME markers, and directory structure to surface product-relevant signals before PRD work begins.
  • Use case: When a PM receives a vague request such as declining renewal rate, this Skill can consolidate user comments, internal docs, codebase clues, and public reference pages into organized research notes ready for downstream refinement.

Quick Start

Ask the agent to run pm-collect on your requirement description so it scans the current conversation, repository, linked URLs, and configured knowledge base, then saves grouped raw materials into the collect output folder.

Frequently Asked Questions about pm-collect

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

FAQPage Schema
How do I collect product discovery materials from multiple sources into one place?

Product discovery materials are collected by scanning conversation context, repository artifacts, extracted URLs, and optional knowledge bases in priority order, then grouping findings by material type with source paths recorded for traceable aggregation.

What is the best way to aggregate raw requirements and user feedback without losing the original context?

Requirements and feedback aggregation is achieved by deduplicating sources, mapping explicit relationships between materials, and marking conflicting or supporting evidence without rewriting the original inputs.

How do I scan a project repository for product signals before writing a PRD?

Repository analysis surfaces product signals by inspecting README files, docs, config files, commit history, TODO or FIXME markers, and directory structure to gather evidence before PRD refinement begins.

Can I trace conflicting research materials back to their original source paths?

Traceability is supported by recording source paths for all collected materials and explicitly marking supporting or conflicting relationships, ensuring every aggregated finding links back to its origin.

How do I consolidate scattered URLs and conversation notes into organized research for requirement intake?

URL scraping and conversation context extraction consolidate scattered inputs by removing duplicates and saving grouped raw materials into a configurable collect output folder, ready for downstream refinement.

Does requirement intake work without a configured knowledge base?

Requirement intake functions with the knowledge base as an optional source, relying primarily on conversation context, project repository artifacts, and extracted URLs for evidence collection.