Multiple teams (Firefly, UXD SDLC) are independently building skill libraries across separate repos. ai-helpers should be the shared foundation they build on top of — reviewed, maintained, and distributable through a governed contribution process.
Two-tier model already exists:
- patternfly/ai-helpers (GitHub) — public PF skills
- uxd/ai-helpers (GitLab) — UXD superset layered on top
No install/update mechanism exists today for downstream repos to consume ai-helpers skills automatically. This spike investigates what's technically possible and recommends an integration path.
Acceptance Criteria:
- Research how Claude Code plugins/marketplaces are consumed by downstream repos today (marketplace config, symlinks, git submodules, etc.)
- Identify viable integration paths and trade-offs of each
- Define what belongs in ai-helpers (shared foundation) vs what stays team-specific
- Validate the two-tier GitHub/GitLab model supports distribution without sync conflicts or internal content leaks
- Recommend an integration path — implementation is a separate issue
Jira Issue: PF-4034
Multiple teams (Firefly, UXD SDLC) are independently building skill libraries across separate repos. ai-helpers should be the shared foundation they build on top of — reviewed, maintained, and distributable through a governed contribution process.
Two-tier model already exists:
No install/update mechanism exists today for downstream repos to consume ai-helpers skills automatically. This spike investigates what's technically possible and recommends an integration path.
Acceptance Criteria:
Jira Issue: PF-4034