rai-epic-run

Name: rai-epic-run
Availability: InStock
Author: HumanSys

Orchestrate epic lifecycle phases with delegation gates in repository workflows.

71|8|Updated Feb 13, 2026

Search Tags:#automation #git #workflow #skills #delegation #orchestrator #epic

Ready to run

npx skills add https://github.com/humansys/raise --skill rai-epic-run

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rai-epic-run
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-epic-run
Command: npx skills add https://github.com/humansys/raise --skill rai-epic-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate and resume the end-to-end epic lifecycle in repository-based engineering workflows so teams can run epics consistently, enforce delegation gates, and avoid ad-hoc, error-prone manual sequencing.

Core Features & Use Cases

Phase detection and resumption: Detect the most advanced epic phase from repository artifacts and resume execution from that phase.
Gate-driven orchestration: Apply delegation rules (REVIEW/NOTIFY/AUTO) after design, architecture review, and planning and stop when human review or simplification is required.
Story handoff and safety: Parse progress tables, present pending stories, and mandate separate story-run sessions to preserve context quality (ADR-043).

Quick Start

Invoke the epic orchestrator with the epic identifier to resume or run the full lifecycle, for example run /rai-epic-run E325.

Frequently Asked Questions about rai-epic-run

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate epic lifecycle orchestration in git workflows?▼

Epic lifecycle orchestration automates phase-by-phase execution in repository-based engineering workflows by detecting the current phase from git artifacts and resuming execution from that point. It coordinates design, planning, and story handoff automatically.

What are delegation gates in epic workflow automation?▼

Delegation gates are checkpoint rules (REVIEW, NOTIFY, AUTO) applied after design, architecture review, and planning phases. They stop automated execution when human review or scope simplification is required before proceeding to the next phase.

How do I resume an interrupted epic from the correct phase?▼

Resuming an interrupted epic works by detecting the most advanced phase from existing repository artifacts and continuing execution from that detected phase, eliminating manual sequencing and avoiding duplicate work.

Do I need a developer profile to enforce delegation rules in git workflows?▼

Yes, a developer profile (~/.rai/developer.yaml) is required to define and enforce delegation rules. The orchestrator reads this profile alongside skill SKILL.md files to determine gate behavior during epic execution.

Why does epic orchestration mandate separate story-run sessions?▼

Separate story-run sessions are mandated to preserve context quality per ADR-043. The orchestrator parses progress tables from scope.md, presents pending stories, and hands them off for independent execution rather than running them inline.

What's the best way to manage scope.md progress tables for epic stories?▼

Managing scope.md progress tables is handled by parsing them to track story status and present pending stories for execution. The orchestrator reads these tables to determine which stories remain and coordinates handoff accordingly.