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—PRDs, demo scripts, capability roadmaps, schema, Help articles—without forking, duplicating, or wiring fragile git submodules between them. ## Core Features & Use Cases - Cross-repo manifest pattern: A declarative YAML manifest (.claude/skill-manifest.yml) declares which skills and grounding artifacts each repo exposes, resolved via environment variables or sibling-directory layout. - Resolver and CLI diagnostics: scripts/ai/skill_manifest.py loads the manifest and resolves grounding paths, with --check and --list-skills commands for verification. - Temporal split governance: Documents which repo is canonical for future state (PMOS: PRDs, roadmap) versus current state (Foundations: built schema, deployed flags, real records). - Use Case: A maintainer authoring a PRD in PMOS uses the resolver to read the Foundations ERD and cite real object schema instead of stale narrative summaries. ## Quick Start Run the skill manifest resolver check to confirm both repository clones are discoverable and list the skills available from each side.
