rhoai-platform-planning

Use when planning, documenting, or reviewing the Red Hat OpenShift AI platform baseline for the demo: supported OpenShift versions, AWS self-managed posture, subscriptions, cluster-admin access, worker resources, default storage class, identity provider, registry access, object storage, component prerequisites, supported configurations, component support status, hardware and accelerator planning, and Red Hat AI Inference compatibility. Do NOT use for exact DSC fields (use rhoai-dsci-dsc-configuration), GPU implementation manifests (use rhoai-nvidia-gpu-accelerators), update channel policy (use rhoai-update-channels), or live environment validation (use env-deploy-and-evaluate).

Jump to install

Repository: adnan-drina/rhoai3-coding-demo
Last source activity: July 6, 2026 at 18:02
Detected SKILL.md language: English
Stars: 3
Forks: 2

Install options

The review-first prompt is selected by default. You can switch to a direct command or download a local copy.

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

A direct command skips the review prompt. Inspect the source before running it.

npx skills add https://github.com/adnan-drina/rhoai3-coding-demo --skill rhoai-platform-planning

The command stays on one line. Scroll horizontally to inspect it before copying.

Prefer a local copy? Download the files currently available to SkillsMP.

Review the source files

Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.

File Explorer

5 files

SKILL.md

Source instructions · Read-only preview

Back to search Back to installation

paved-road-m1

Use at M1 ANALYZE as the kind index. Pin only --skill paved-road-m1. Follow steps.json in order (skill_view subskills; native kanban_attach.py). Happy-path terminator is kanban_request_review, not kanban_complete. kanban_block for external/platform (MaaS 500, missing key, GPU). Do not pin derive-legacy-boot3, scan-with-mta, and inventory-legacy-surface on the card. Do not use for M2 PLAN, M3, or M4.

2026-08-29

paved-road-m2

Use at M2 PLAN as the kind index. Pin only --skill paved-road-m2. Follow steps.json in order (skill_view speckit-specify then plan/tasks, plan-migration-partition producer, check-spec-readiness, native check-partition-coverage.py and assert-m2-speckit-conformance.py, k4_convert.py, k4_mint.py). Happy-path terminator is kanban_request_review, not kanban_complete. kanban_block for external/platform (MaaS 500, missing key, GPU). Do not pin plan-migration-partition and check-spec-readiness on the card. Do not use for M1, M3, or M4.

2026-08-29

check-spec-readiness

Before kanban_create — lint SDD specs, story bodies (typed BODY_* codes), and partition coverage (HTTP 1:1 via story.endpoints as METHOD /path, dest_file 1:N with supersede; refuse invented HTTP paths vs inventory; K4 dest_file round-trip REFUSE dest-9 Application.java/GreetingResource.java; refuse AC HTTP tokens that diverge from endpoints; refuse mvn test whose pom parent has no test-toolchain claim). Do not use to mint Kanban children or assemble M3 bodies (K4 converter is .hermes/kernel/k4_convert.py).

2026-08-28

View all from this repository

name	rhoai-platform-planning
metadata	{"author":"rhoai3-demo","version":"1.0.0","platform-family":"rhoai","platform-baseline":"repo","ocp-baseline":"repo","skill-group":"RHOAI Platform"}
description	Use when planning, documenting, or reviewing the Red Hat OpenShift AI platform baseline for the demo: supported OpenShift versions, AWS self-managed posture, subscriptions, cluster-admin access, worker resources, default storage class, identity provider, registry access, object storage, component prerequisites, supported configurations, component support status, hardware and accelerator planning, and Red Hat AI Inference compatibility. Do NOT use for exact DSC fields (use rhoai-dsci-dsc-configuration), GPU implementation manifests (use rhoai-nvidia-gpu-accelerators), update channel policy (use rhoai-update-channels), or live environment validation (use env-deploy-and-evaluate).