Skip to content

SPIKE-executor

Execute RHOAI SPIKE investigations through a 9-step human-in-the-loop lifecycle. Each step produces artifacts in the artifacts/ directory and pauses at a breakpoint for explicit user approval before continuing. Steps: (1) intake, (2) plan generation, (3) Jira preview, (4) Jira creation, (5) AI research enrichment with hallucination validation, (6) test plan + pytest suite generation, (7) test execution + rubric scoring, (8) RFE generation + approval, (9) completion summary. Supports --skip-tests (no OpenShift) and --skip-jira (no Jira credentials).

Plugin: spike-executor | User-invocable

Contract

Skill Contract canonical-skill-v1

Guide an engineer through the nine-step RHOAI SPIKE lifecycle for a named project (plan, Jira structure and sync, AI research enrichment and validation, test plan and pytest suite, cluster test run and feasibility scoring, RFE generation, final summary) by running the spike-executor CLI at each step and stopping at each of the skill's six breakpoints for human review.

Identity

Functions
orchestrate generate
Success
  • Each step writes the artifact the skill names for it under artifacts/ (SPIKE-Plan-<project>.md, SPIKE-Jira-Preview-<project>.md, SPIKE-Jira-Tickets-<project>.md and Jira-Links-<project>-spike.md, Research-Findings-<project>.yaml and .md, Research-Prompt-<project>.md, Research-Validation-<project>.md, Dockerfile.ubi-<project>, Test-Plan-<project>.md, test_suite_<project>.py, Test-Results-<project>.yaml, Feasibility-Report-<project>.yaml and .md, RFE-Input-<project>.md, SPIKE-Summary-<project>.md).
  • At each of the six breakpoints (plan, Jira structure, research, test plan, test execution, RFE) the artifacts generated for that gate are shown in full and the workflow advances only on the engineer's approval phrase; Step 4 (ticket creation) displays the created-tickets table and continues without a gate.
  • With cluster tests run, the feasibility decision (GO, PIVOT or NO-GO) follows the computed score and the security gate, and RFE generation is offered only for GO or PIVOT; with --skip-tests, Steps 6 and 7 are skipped, the RFE step runs without a score, and the skipped stages are reported upfront rather than silently omitted.

Optimization Targets

task_success judge SKILL.md @ 924ec48

Invariants

Must Preserve
  • At every breakpoint, display each generated .md artifact's complete content with the Read tool, never a summary, an excerpt or a path alone.
  • Never proceed past a breakpoint without the engineer's explicit approval phrase.
  • Report missing Jira credentials or OpenShift access before starting and continue with the steps that remain possible instead of blocking.
  • When tests run, any security check scoring 0 blocks GO, and a NO-GO result never offers RFE generation.
Fixed Context
toolsRead, Write, Edit, Glob, Grep, Bash, AskUserQuestion, WebSearch, WebFetch
clispike-executor, oc
knowledgerepository_contentpublic, task_inputtask_private, tool_outputtask_private

Traceability

Skill
.claude/skills/SPIKE-executor/SKILL.md
Supporting

Diagram

SPIKE-executor diagram

Arguments

/SPIKE-executor <project> [--skip-tests] [--skip-jira]
Argument Required Default Description
project - Name of the project/technology being investigated (e.g., AutoGluon, gRPC). Used as the suffix for all artifact filenames.
--skip-tests - Skip cluster tests and scoring (Steps 6-7). For environments without OpenShift access.
--skip-jira - Skip Jira sync steps (Steps 3-4, 5b). For testing without Jira credentials.

Usage

/SPIKE-executor AutoGluon
/SPIKE-executor gRPC --skip-tests
/SPIKE-executor my-project --skip-jira