End-to-end test planning workflow for RHOAI: generate test plans from strategies, create test cases, implement executable automation code, verify UI tests against live clusters via Playwright, publish to GitHub with PR creation, resolve review feedback, and score quality with automated rubrics using parallel sub-agent analysis
Analyzes strategy and ADR to extract feature scope, test objectives, and API endpoints/methods under test. Use for extracting technical scope and API surface area from requirements documents.
Analyzes strategy and ADR to identify test environment configuration, test data, test users, infrastructure, and tooling requirements. Use for determining test execution prerequisites and infrastructure setup needs.
Analyze test cases and recommend placement (component repo vs downstream E2E repo). Use for determining where each test should be implemented based on test level, dependencies, and repository capabilities.
Analyzes strategy and ADR to determine test levels, test types, priority definitions, non-functional requirements, and risks with mitigations. Use for identifying what needs testing, how to prioritize test coverage, and what risks to mitigate.
Generate executable test automation code from test case specifications with intelligent placement in component or downstream repos. Use after test cases are reviewed to create production-ready pytest code that follows repository conventions.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
End-to-end test planning workflow for RHOAI: generate test plans from strategies, create test cases, implement executable automation code, verify UI tests against live clusters via Playwright, publish to GitHub with PR creation, resolve review feedback, and score quality with automated rubrics using parallel sub-agent analysis.
| Skill | Description |
|---|---|
/test-plan-create | Generate a test plan from a strategy (RHAISTRAT or RHOAIENG), with optional ADR |
/test-plan-create-cases | Generate individual test case files from an existing test plan |
/test-plan-update | Update test plan with new docs (ADR, API specs), re-analyze, bump version |
/test-plan-case-implement | Generate executable test automation code from TC specifications with intelligent placement |
/test-plan-ui-verify | Verify UI test cases from a PR against a live ODH/RHOAI cluster via Playwright |
/test-plan-publish | Publish test plan artifacts to GitHub — branch, commit, and open a PR |
/test-plan-resolve-feedback | Assess PR review comments, let the user decide what to apply, and push updates |
/test-plan-score | Score an existing test plan using quality rubric (without auto-revision) |
context: fork)| Skill | Description |
|---|---|
test-plan-analyze-endpoints | Extract feature scope, test objectives, and API endpoints from docs |
test-plan-analyze-risks | Analyze strategy/ADR to determine test levels, types, priorities, risks |
test-plan-analyze-infra | Identify test environment, data, infrastructure requirements |
test-plan-analyze-placement | Recommend test placement (component repo vs downstream) |
test-plan-merge | Intelligently merge new analyzer findings into existing test plan |
test-plan-resolve-gaps | Cross-reference gaps with new findings to determine what's resolved |
test-plan-review | Review test plan for completeness, consistency, and quality with auto-revision |
test-plan-generate-test-file | Generate complete test file with all functions, quality scoring and auto-revision |
test-plan-score-test-function | Score generated test function code using 5-criteria quality rubric |
Install from the opendatahub-io/skills-registry marketplace:
# Add the marketplace (one-time)
claude plugin marketplace add opendatahub-io/skills-registry
# Install test-plan plugin
/plugin install test-plan@opendatahub-skills
This clones the repository and makes skills immediately available. Then install Python dependencies:
cd ~/.claude/plugins/test-plan
uv sync --extra dev
Use skills:
# Will prompt for artifact location (default: ~/Code/opendatahub-test-plans)
/test-plan-create RHAISTRAT-400
# Auto-uses location from /test-plan-create
/test-plan-create-cases
# Auto-detects feature from /test-plan-create session
# Will prompt for publish target (default: opendatahub-io/opendatahub-test-plans)
/test-plan-publish
Clone the repository directly:
git clone https://github.com/opendatahub-io/odh-test-gen ~/Code/odh-test-gen
cd ~/Code/odh-test-gen
uv sync --extra dev
Skills are available from skills/ directory.
Note: Skills use symlinks for shared utilities (_common/scripts → ../../scripts). Both installation methods clone the full repository, so symlinks resolve correctly.
Each skill includes an argument-hint field in its frontmatter for autocomplete guidance when typing slash commands.
Important: Test plan artifacts are kept separate from the skill repository to maintain clean boundaries between code and data.
When you run /test-plan-create, it asks where to save artifacts:
Where should test plan artifacts be created?
Provide a directory path (e.g., ~/Code/opendatahub-test-plans/plans/<team-name>), or press Enter for: ~/Code/opendatahub-test-plans/plans/
Note: Replace <team-name> with your team name (e.g., ai-hub, dashboard, etc.)
~/Code/opendatahub-test-plans/plans/ai-hub)~/Code/opendatahub-test-plans/plans/ or any path outside the skill repo.claude/settings.json for future runsThe skill creates: <your-path>/<feature-name>/
Example: If you enter ~/Code/opendatahub-test-plans/plans/ai-hub, it creates ~/Code/opendatahub-test-plans/plans/ai-hub/mcp_catalog/
/test-plan-create-cases automatically uses the same location as /test-plan-create when run in the same session (no prompt needed).
npx claudepluginhub opendatahub-io/skills-registry --plugin test-planAgent and skill evaluation harness with MLflow integration
Site generation skills for the OpenDataHub Skills Registry
Assess RFEs against quality criteria using a structured rubric
Orchestrator skills, agent prompts, and state management for the Jira autofix pipeline
A plugin providing a subagent to scan a source code project for potential FIPS compliance issues
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Persistent file-based planning for AI coding agents. Crash-proof markdown plans (task_plan.md, findings.md, progress.md) that survive context loss and /clear, with an opt-in completion gate and multi-agent shared state. Manus-style. Works with Claude Code, Codex CLI, Cursor, Kiro, OpenCode and 60+ agents via the SKILL.md standard. Includes Arabic, German, Spanish, and Chinese (Simplified and Traditional).
Browser automation and end-to-end testing MCP server by Microsoft. Enables Claude to interact with web pages, take screenshots, fill forms, click elements, and perform automated browser testing workflows.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review