pmos-integration

Connects Foundations and PMOS repositories through a read-only cross-repo skill manifest.

33|12|Updated Sep 24, 2024
One-click install
npx skills add https://github.com/bgaldino/rlm-base-dev --skill pmos-integration-bgaldino
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pmos-integration
Source: https://github.com/bgaldino/rlm-base-dev/tree/main/.cursor/skills/pmos-integration
Command: npx skills add https://github.com/bgaldino/rlm-base-dev --skill pmos-integration-bgaldino

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Maintainers working across the Foundations (rlm-base-dev) and PMOS (pmos-revenue-cloud) repositories need to consume content from the other repo without forking, duplicating, or using fragile git submodules and symlinks. ## Core Features & Use Cases - Cross-repo manifest pattern: Declares which skills and grounding artifacts (ERD, Help mirror, qb-scenario reference, API reference) each repo exposes to the other via .claude/skill-manifest.yml. - Filesystem-level resolver: Uses scripts/ai/skill_manifest.py with $FOUNDATIONS_REPO_ROOT / $PMOS_REPO_ROOT env vars or sibling-directory fallback, degrading gracefully when the other clone is absent. - Temporal split governance: PMOS is canonical for future state (PRDs, roadmap, capability map); Foundations is canonical for current state (built schema, deployed flags, real records). - Use Case: A PMOS prd skill reads the Foundations ERD through the resolver to cite real schema instead of stale narrative summaries, while Foundations' qb-demo-script skill optionally invokes PMOS narrative-voice skills as upgrades. ## Quick Start Run python scripts/ai/skill_manifest.py --check to verify the manifest resolves both repository clones and lists available skills.

Frequently Asked Questions about pmos-integration

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

FAQPage Schema
How do I share skill content between two repositories without duplicating it?

Use a cross-repo skill manifest that declares which skills and grounding artifacts each repo exposes. A Python resolver locates the sibling clone via environment variables or sibling-directory paths and reads content as static files, so nothing is copied or forked.

How does the PMOS and Foundations repo integration work?

Each repo keeps a declarative YAML manifest listing consumable skills and artifacts. The resolver script resolves local clone paths and returns file paths or None, letting consumer skills read the other repo read-only while each maintainer keeps full ownership.

What happens if the PMOS repository clone is not present locally?

The consumer skill degrades gracefully and operates standalone. The resolver returns None when the sibling clone cannot be found, so nothing breaks; the cross-repo upgrade simply is not available.

Why not use git submodules or symlinks for cross-repo grounding?

Submodules and symlinks are operationally fragile across OS layouts and break Claude Code skill discovery. The manifest pattern uses plain filesystem paths resolved at runtime, which works across environments without CI or auth dependencies.

Which repository is canonical for schema versus roadmap content?

Foundations is canonical for current state: built schema, deployed feature flags, real records, and mirrored Help articles. PMOS is canonical for future state: PRDs, roadmap, and the capability map. Do not treat PMOS proposals as runtime truth.