pm-context-scan-docs

Extract structured knowledge from source documents into a centralized product wiki.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/pingmepi/pm-os --skill pm-context-scan-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pm-context-scan-docs
Source: https://github.com/pingmepi/pm-os/tree/main/skills/pm-context-scan-docs
Command: npx skills add https://github.com/pingmepi/pm-os --skill pm-context-scan-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the fragmentation of product knowledge by automatically synthesizing disparate source documents into a unified, structured wiki format, ensuring the entire team stays aligned on the same source of truth.

Core Features & Use Cases

  • Structured Extraction: Maps raw source content into standardized PM-OS wiki sections like success indicators, technical constraints, and stakeholder authority.
  • Conflict Detection: Automatically identifies and flags contradictory information across multiple source documents.
  • Confidence Scoring: Assigns confidence tiers to extracted data based on source reliability, ensuring PMs know which information requires verification.
  • Use Case: When starting a new project, use this skill to ingest meeting transcripts, research PDFs, and stakeholder emails to instantly generate a baseline product wiki.

Quick Start

Run the pm-context-scan-docs skill to extract and structure all knowledge from the registered source documents into the project wiki.

Frequently Asked Questions about pm-context-scan-docs

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

FAQPage Schema
How do I consolidate scattered product management documents into a single wiki?

To consolidate product management documents into a single wiki, this skill parses registered source documents and YAML configurations to extract structured knowledge and synthesize it into a centralized product wiki.

What is the best way to detect conflicting information across multiple project source documents?

The best way to detect conflicting information across project source documents is using automated conflict detection, which scans and flags contradictory details found within disparate inputs like research briefs and meeting transcripts.

Can I generate a product wiki directly from meeting transcripts and stakeholder emails?

Yes, you can generate a product wiki directly from meeting transcripts and stakeholder emails by registering them as source documents, allowing the skill to ingest and map the raw content into standardized wiki sections.

How does confidence scoring work for extracted product knowledge?

Confidence scoring for extracted product knowledge works by assigning reliability tiers to data based on the trustworthiness of the source document, helping product managers identify which information requires further verification.

Do I need YAML configuration files to extract structured knowledge from markdown documents?

Yes, you need YAML configuration files alongside markdown-based source documents, because the skill requires parsing these configurations to map raw content into standardized product wiki sections like success indicators and technical constraints.