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.