HyperFleet Operational Readiness Audit
HyperFleet Operational Readiness Audit Skill
CRITICAL: READ-ONLY MODE
This skill MUST NOT modify any files in the repository being audited. All operations are read-only analysis. The skill produces reports but never changes code, configuration, or documentation.
When to Use This Skill
Activate this skill when the user:
- Asks to "check operational readiness"
- Asks "is this repo operationally ready?"
- Asks to "audit for production readiness"
- Asks "what operational gaps does this repo have?"
- Asks to "run an operational readiness check"
- Asks about "production readiness"
- Asks "is this service ready for production operations?"
- Asks to "validate operational requirements"
Operational Readiness Requirements Source
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
1hyperfleet architecture
Answers questions about HyperFleet architecture, design patterns, versioning strategies, cluster lifecycle, event-driven architecture, adapter framework, and git workflow by fetching docs from the openshift-hyperfleet/architecture GitHub repository.
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.
1