pm-context-import

Name: pm-context-import
Availability: InStock
Author: pingmepi

Ingest project documents into a provenance-tagged context wiki with approval gates.

Updated Jun 8, 2026

Search Tags:#documentation #pipeline #product-management #knowledge-base #pdlc #context-import

Ready to run

npx skills add https://github.com/pingmepi/pm-os --skill pm-context-import

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pm-context-import
Source: https://github.com/pingmepi/pm-os/tree/main/skills/pm-context-import
Command: npx skills add https://github.com/pingmepi/pm-os --skill pm-context-import

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of fragmented project knowledge by ingesting disparate research, briefs, and design notes into a single, version-controlled, and verifiable context wiki.

Core Features & Use Cases

Context Synthesis: Automatically parses and normalizes arbitrary project documents (PDFs, DOCX, Markdown) into a structured, provenance-tagged knowledge base.
Pipeline Seeding: Maps existing PM work to the PM-OS stage pipeline, backfilling missing artifacts while maintaining strict approval gates.
Drift Detection: Uses modular hashing to ensure that once context is approved, any subsequent changes are surfaced as drift, keeping the project source of truth honest.

Quick Start

Run the pm-context-import skill by passing the path to your folder of project documents to ingest them into the pipeline.

Frequently Asked Questions about pm-context-import

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

FAQPage Schema

How do I consolidate fragmented project documentation into a single knowledge base?▼

To consolidate fragmented project documentation, this Skill ingests disparate research, briefs, and design notes into a structured, provenance-tagged context wiki. It parses arbitrary project documents and normalizes them into a version-controlled knowledge base.

How does drift detection work for product management artifacts?▼

Drift detection for product management artifacts uses modular hashing to monitor approved context. Once a context wiki is approved, any subsequent changes to source documents are surfaced as drift, keeping the project source of truth honest.

Can I map existing product briefs to a standardized pipeline?▼

You can map existing product briefs to a standardized pipeline by mapping PM work to the PM-OS stage pipeline. This process backfills missing artifacts while maintaining strict approval gates for pipeline-ready output.

What file formats are supported for importing project context?▼

Supported file formats for importing project context include PDFs, DOCX, and Markdown. The context synthesis feature automatically parses and normalizes these arbitrary project documents into a structured knowledge base.

Does pipeline seeding require local file system access?▼

Pipeline seeding requires local file system access to manage project state, artifact hashing, and gated approval workflows. This environment setup ensures the synthesized context wiki remains verifiable and version-controlled.

What is the best way to unify heterogeneous project specs without losing provenance?▼

The best way to unify heterogeneous project specs without losing provenance is ingesting them into a structured context wiki. The system synthesizes disparate research and design notes while tagging each artifact with its original source origin.