HyperFleet Architecture
HyperFleet Architecture Skill
When to Use This Skill
Activate this skill when the user asks questions about:
- HyperFleet architecture, design patterns, or principles
- Versioning strategies (API, Sentinel, adapters, config)
- Status aggregation and cluster lifecycle
- Event-driven architecture and CloudEvents
- Adapter framework and config-driven deployment
- Git workflow, branching, or release processes
- Design decisions or trade-offs
Architecture Documentation Location
All HyperFleet architecture documentation is located in the architecture repository on GitHub at:
More from openshift-hyperfleet/hyperfleet-claude-plugins
jira story point estimator
Estimates story points for JIRA tickets by analyzing complexity, scope, and comparing to historical team data. Activates when users ask to estimate, point, or size a ticket, or ask "how many points should this be?
15jira ticket creator
Creates well-structured JIRA tickets in the HYPERFLEET project with required fields including What/Why/Acceptance Criteria, story points, and activity type. Activates when users ask to create a ticket, story, task, or epic.
13jira-story-pointer
Estimates story points for JIRA tickets by analyzing complexity, scope, and comparing to historical team data. Activates when users ask to estimate, point, or size a ticket, or ask "how many points should this be?
2review-pr
Review a PR with JIRA validation, architecture checks, impact analysis, and interactive recommendations
1architecture impact
Analyzes code changes in HyperFleet component repositories (API, Sentinel, Adapter, Broker) to determine if architecture documentation needs updates using directory-based scope and complete document reading with single comprehensive LLM analysis. Activates when users ask "analyze architecture impact", "check if docs need update", or use /architecture-impact.
1jira ticket triage
Validates JIRA tickets have required fields and quality standards for sprint planning.
1