---
name: story-yolo
description: Use when Alex invokes /story-yolo from Telegram to let Hermes autonomously direct and produce an AI video story without asking clarifying questions, using all supplied references and making creative decisions.
version: 1.0.0
author: Hermes Agent
license: MIT
metadata:
  hermes:
    tags: [story, yolo, video-story, telegram, ai-video]
    related_skills: [story, ai-video-story-pipeline]
---

# /story-yolo — Autonomous Story Director

## Overview

`/story-yolo` is the no-questions version of `/story`. Alex can send a vibe, a sentence, or a pile of Telegram references; Hermes decides the story, visual language, character usage, scene structure, and repair strategy.

## Rules

- Do **not** ask clarifying questions.
- Use every relevant Telegram reference image path surfaced in the message.
- Make explicit director decisions: genre, pacing, runtime, style, character roles, setting, and music/voice approach.
- Bias toward a short, reviewable cinematic artifact over an overlong unfinished project.
- Always request or build a director's cut with `SCENE N · SHOT M` overlays for review.

## Workflow

1. Extract all creative signal from text and images.
2. Decide the missing pieces yourself.
3. POST multipart to `http://localhost:4015/api/hermes/projects/create-and-run` with bearer `$HERMES_AUTOMATION_TOKEN`, field `prompt`, field `auto_yolo=true`, and field `images` for every relevant local reference path. This attaches references before generation starts.
4. Poll project/run status until the first reviewable export exists or a failure needs repair.
5. POST `/api/hermes/projects/:id/assemble-directors-cut` and poll `/api/hermes/projects/:id/directors-cut`.
6. Report project URL, director's cut URL/path, and a scene/shot review key.

## Prompt Requirements for create-and-run

The payload prompt should include:

- “YOLO mode: do not ask the user questions.”
- “Hermes is the director and continuity supervisor.”
- A numbered reference inventory: filename/path + interpretation.
- Story premise and tone chosen by Hermes.
- Character/wardrobe/setting continuity constraints.
- Output should be reviewable with director's cut scene/shot numbers.

## Failure Handling

If a scene fails generation, use `/api/hermes/projects/:id/repair` with a directive such as:

```json
{
  "instructions": "Repair failed or visually inconsistent shots. Keep the same character identity and setting from uploaded references. Simplify motion if needed.",
  "scene_numbers": [2],
  "regenerate_frames": true,
  "regenerate_video": true,
  "lipsync": true,
  "directors_cut": true
}
```

## Verification Checklist

- [ ] No clarification questions were asked.
- [ ] All relevant refs were inventoried and uploaded.
- [ ] Project creation was started.
- [ ] Director's cut was requested or exists.
- [ ] Alex gets scene/shot review instructions.