Video 01b — Dana defines the task workflow
Protagonist: Dana (Dev Manager) Arc: Setup · deep-dive supplement to Video 01 Length: 7:41 Apps in frame: App Launcher · Workflow Studio YouTube: https://youtu.be/FzUQs7tWkOo Status: ✅ Published
Story beat
A focused close-up on the Workflow Studio step from Video 01. Dana defines the contract every later phase of the team will run on: issue types, workflow states, and the AI agent actions that fire on each state transition. Two paths — build a workflow type by hand, or describe the team in plain English and let RobOS draft the whole thing.
The workflow Dana saves here is what Pat’s stories author against (Phase 2), what Jordan’s CI gates fire transitions on (1.6 of his arc), and what Alex’s task workspaces auto-provision into (Phase 3).
Chapters
| Time | Section |
|---|---|
| 0:00 | Launch Workflow Studio |
| 0:04 | What Workflow Studio does — types, states, AI actions |
| 0:17 | AI Generate textarea |
| 0:22 | Add Issue Type |
| 0:29 | Configure label, color, states |
| 0:34 | Wire AI agent actions to transitions |
| 0:49 | Add a new state |
| 1:10 | Unsaved-changes guard |
| 1:24 | AI prompt — generate issue types from a description |
| 3:24 | Done — rich types with AI actions |
| 4:26 | Clear and re-generate seeded by a Jira project |
Source
- Source capture + cues + youtube metadata:
packages/robos-test/run/demos/model-problem/06-dana-workflow-studio/ - Regeneration: edit
cues.jsonand re-runnode packages/robos-test/demos/narrate-source.js …(full command in the per-folderyoutube.md).