Spike: Discover UXD marketplace requirements and cross-team skill distribution model

[patternfly-jira-sync]

Investigate how UXD wants to organize their AI skills marketplace and what capabilities are needed for cross-team skill distribution. Determine the requirements for a downstream marketplace that can source skills from multiple upstream teams (PF, ODH, others) while maintaining its own plugin structure.

Acceptance Criteria:

• Determine how UXD wants to organize plugins — persona-based (developer, designer)? workflow-based? role-based?

• Document which external skill sources UXD wants to incorporate (e.g., OpenShift AI, official Claude plugins, Red Hat internal tools)

• Clarify ownership model — who controls plugin organization vs skill content?

• Identify requirements for cross-marketplace skill distribution (e.g., referencing skills from upstream repos without duplication, mixing remote and local skills within a plugin, same skill appearing in multiple plugins)

• Capture constraints or preferences from UXD leadership

• Deliver a written summary (google doc) of findings and requirements to inform next steps

---

Jira Issue: PF-4217

[coderabbitai]

🔗 Related PRs

#59 - chore(plugins): rename design-tokens to design-foundations, relocate skills [merged]
#67 - feat(design-mode): New design skills [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!