rai-story-run

Orchestrate RaiSE story lifecycles across detection, design, implementation, review, and closure phases.

71|8|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/humansys/raise --skill rai-story-run
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rai-story-run
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-story-run
Command: npx skills add https://github.com/humansys/raise --skill rai-story-run

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates and automates the complete story lifecycle so developers don't have to manually invoke each phase, detect progress, or manage delegation gates across design, implementation, review, and close. It reduces human error, preserves a thin orchestrator, and resumes work from the most advanced artifact found in the repo.

Core Features & Use Cases

  • Phase detection & resume: Inspects repository artifacts and story branches in reverse order to resume at the correct phase automatically.
  • Forked subagent orchestration: Spawns isolated Agent subagents for each phase using the skill's SKILL.md as the prompt, verifying artifacts and merge commits produced by each fork.
  • Delegation gates & guardrails: Applies REVIEW/NOTIFY/AUTO gates after key phases, enforces close-phase scope constraints, and stops on critical failures or failing AR/QR verdicts.
  • Use case: Run a full story workflow for S325.6 to produce design, plan, implementation artifacts, pass architecture and quality reviews, and merge the story branch with verification.

Quick Start

Run rai-story-run for story S325.6 to execute all phases, apply delegation gates, and produce the merge commit and artifacts.

Frequently Asked Questions about rai-story-run

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

FAQPage Schema
How do I automate the full story workflow lifecycle from design to merge?

Story workflow orchestration automates the complete lifecycle by detecting repository artifacts and spawning isolated subagents for each phase. It applies delegation gates, verifies file artifacts and merge commits, and resumes from the most advanced phase found.

How does phase detection and resume work for interrupted git story branches?

Phase detection inspects repository artifacts and story branches in reverse order to automatically resume at the correct phase. This prevents manual progress tracking and ensures the workflow continues from the most advanced artifact found in the repository.

What delegation gates are applied during story workflow orchestration?

Story workflow orchestration applies REVIEW, NOTIFY, and AUTO delegation gates after key phases. It enforces close-phase scope constraints and stops the workflow automatically on critical failures or failing architecture and quality review verdicts.

Do I need an Agent tool to run end-to-end story workflows?

Yes, you need an Agent tool capable of spawning subagents to run end-to-end story workflows. The orchestrator also requires repository git access and SKILL.md files for each skill to verify artifacts and execute branch merges.

What happens when architecture or quality reviews fail during automated story closure?

When architecture or quality reviews fail during automated story closure, the orchestration stops on critical failures or failing AR/QR verdicts. This guardrail prevents merging unverified branches and ensures only compliant artifacts progress.