kb

Organize PMC project knowledge into a fixed .pmc/docs directory with YAML frontmatter.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/jayprimer/pmc-marketplace --skill kb-jayprimer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: kb
Source: https://github.com/jayprimer/pmc-marketplace/tree/main/plugins/pmc/skills/kb
Command: npx skills add https://github.com/jayprimer/pmc-marketplace --skill kb-jayprimer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Knowledge is often scattered across disparate documents and tools, hindering quick access and decision-making. This Skill provides a centralized, standardized structure for PMC project documentation to ensure session continuity and consistent governance across teams.

Core Features & Use Cases

  • Centralizes knowledge for session continuity across projects and teams.
  • Enforces a fixed directory layout (.pmc/docs/) and standardized formats for PRDs, SOPs, tickets (T0000N), patterns, decisions, code maps, research, and status.
  • Supports incremental learning, traceability, and governance through tickets, KB patterns, and code-maps.

Quick Start

Create and maintain your PMC knowledge base by aligning new docs to the .pmc/docs structure and frontmatter-defined SKILL entry points.

Frequently Asked Questions about kb

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

FAQPage Schema
How do I maintain project knowledge for session continuity across teams?

A structured knowledge base solves scattered documentation by centralizing PRDs, SOPs, and decisions into a fixed directory layout with standardized YAML frontmatter. This enforces consistent governance and traceability across teams and projects.

What is the best way to organize project documentation for quick lookup and governance?

Organize documentation by enforcing a fixed directory structure like .pmc/docs/ with YAML frontmatter defining name and description. This standardizes PRDs, patterns, and research for smooth context loading and governance.

How do I structure a knowledge base with YAML frontmatter for PRDs and tickets?

Structure your knowledge base by aligning new documents to a fixed directory layout and defining at least a name and description in YAML frontmatter. This enables smooth loading into context for PRDs, tickets, and code maps.

Does the structured knowledge base approach work for managing project tickets and code maps?

Yes, the structured knowledge base manages project tickets and code maps by applying a standardized directory format. It supports incremental learning and traceability across T0000N tickets, patterns, and decisions for consistent governance.

Why does project knowledge become scattered and how does a fixed directory layout help?

Project knowledge becomes scattered across disparate tools, hindering access. A fixed directory layout centralizes this knowledge, enforcing standardized formats for decisions and research to ensure quick lookup and session continuity.