Orchestrate epic lifecycle phases with delegation gates in repository workflows.
npx skills add https://github.com/humansys/raise --skill rai-epic-run
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
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.
Invoke the epic orchestrator with the epic identifier to resume or run the full lifecycle, for example run /rai-epic-run E325.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
humansysSequence epic stories into implementation plans with milestones and dependencies.
iltan987Automatically stage and commit changes after Spec Kit commands complete.
cuiossRoute change tasks into simple or complex tracks and write solution_outline.md.
ramontramontiniOrchestrate epic story batches with gate enforcement and topological ordering.
