Skip to content

rai pipeline

Execute and manage declarative pipelines. Pipelines orchestrate skills into automated, gate-enforced sequences.

Not available in 3.0

The rai pipeline CLI commands described on this page are not yet available in RaiSE 3.0. Pipeline orchestration in 3.0 runs exclusively through the rai-workspace MCP server. Use the MCP tools (pipeline_start, pipeline_advance, pipeline_status, etc.) from Claude Code instead.

See Pipeline Quickstart for usage.

rai pipeline run

Execute a pipeline by name.

Flag Short Description
NAME Pipeline name (positional, required). E.g., story, epic, bugfix
--issue -i Issue ID for traceability (e.g., RAISE-1234)
--story-type -t Story type: code, docs, analysis. Default: code 
# Run a story pipeline
rai pipeline run story --issue RAISE-1234

# Run for a docs story (skips AR/QR phases)
rai pipeline run story --issue RAISE-1235 --story-type docs

# Run an epic pipeline
rai pipeline run epic --issue RAISE-1100

# Run a bugfix pipeline
rai pipeline run bugfix --issue RAISE-1300

Output shows each phase with status, duration, and gate results:

Pipeline: story (8 phases)
Issue:    RAISE-1234
Delegation: review

  [1/8] start.......................... PASSED  (12.3s)
  [2/8] design......................... PASSED  (45.1s)
        gate: PASSED
  [3/8] plan........................... PASSED  (28.7s)
  ...

COMPLETED  8/8 phases passed  (342.1s total)

rai pipeline list

List all available pipelines from the 3-tier loading hierarchy.

rai pipeline list

Available Pipelines
┌──────────┬──────────────────────────────────┬────────┬──────────┐
│ Name     │ Description                      │ Phases │ Source   │
├──────────┼──────────────────────────────────┼────────┼──────────┤
│ story    │ 8-phase story lifecycle pipeline  │ 8      │ built-in │
│ epic     │ 6-phase epic lifecycle pipeline   │ 6      │ built-in │
│ bugfix   │ 7-phase bugfix lifecycle pipeline │ 7      │ built-in │
│ hotfix   │ Minimal hotfix pipeline           │ 3      │ built-in │
│ deploy   │ 3-phase deployment pipeline       │ 3      │ project  │
└──────────┴──────────────────────────────────┴────────┴──────────┘

Sources: built-in (shipped), project (.raise/pipelines/), user (~/.rai/pipelines/).

rai pipeline resume

Resume a paused pipeline run after a HITL gate.

Flag Short Description
RUN_ID Run ID (positional, required)
--decision -d Decision: approve, revise, reject 
# Approve and continue to next phase
rai pipeline resume abc123 --decision approve

# Request revisions (re-runs current phase)
rai pipeline resume abc123 --decision revise

# Reject and stop the pipeline
rai pipeline resume abc123 --decision reject

The run ID is displayed when a pipeline pauses at a HITL gate.

Delegation Levels

Your delegation level is resolved from your developer profile (~/.rai/developer.yaml) and controls HITL gate behavior:

Level Gate behavior ShuHaRi
review Pauses at every HITL gate Shu
notify Proceeds, notifies you Ha
auto Proceeds silently Ri

Gates marked mandatory: true always pause, regardless of delegation level.

State Persistence

Pipeline state is stored in .rai-state/ as JSON. Runs survive:

  • Terminal restarts
  • Context compaction
  • MCP server restarts

Use rai pipeline resume to continue a paused run after any interruption.