---
name: B-Roll Runtime Planner
slug: b-roll-runtime-planner
category: Quality
description: B-Roll Runtime Planner reads and verifies legacy runtime planner handoffs from pre-v0.9 production records. It checks plan JSON, shot coverage, and preserved evidence without converting the record into a v1 workflow.
github: "https://github.com/erduo1998-cell/erduo-broll-loop-engineering/tree/main/erduo-broll-loop-engineering/stages/broll-runtime-plan"
language: TypeScript
stars: 168
forks: 31
install: "npx degit https://github.com/erduo1998-cell/erduo-broll-loop-engineering/tree/main/erduo-broll-loop-engineering/stages/broll-runtime-plan ~/.claude/skills/broll-runtime-plan"
installs_to: ~/.claude/skills/broll-runtime-plan
source_path: erduo-broll-loop-engineering/stages/broll-runtime-plan/SKILL.md
collection_size: 14
category_size: 1897
collection_url: "https://dirskills.com/collections/erduo1998-cell/erduo-broll-loop-engineering"
added: 2026-09-08T05:34:20.044Z
last_synced: 2026-09-08T05:34:20.044Z
canonical_url: "https://dirskills.com/skills/b-roll-runtime-planner"
---

# B-Roll Runtime Planner

B-Roll Runtime Planner reads and verifies legacy runtime planner handoffs from pre-v0.9 production records. It checks plan JSON, shot coverage, and preserved evidence without converting the record into a v1 workflow.

**Install:**

```bash
npx degit https://github.com/erduo1998-cell/erduo-broll-loop-engineering/tree/main/erduo-broll-loop-engineering/stages/broll-runtime-plan ~/.claude/skills/broll-runtime-plan
```

## README

# Legacy B-roll Runtime Planner

Treat this stage as read-only compatibility for old production records. Do not
dispatch it in a normal v1 production, do not create a new plan here, and do
not reinterpret or edit an existing plan.

In v1 the Parent runs `scripts/plan-runtime.mjs` directly with the Director's
validated Recipes, runtime selection, narrative envelope, visual system, and
new production root. The script validates those inputs, writes the immutable
runtime plan, and writes one minimal assignment packet per authoring unit.

When reading a legacy handoff, verify only that:

- its plan JSON passes `scripts/validate-runtime-plan.mjs` using
  `../../references/runtime/capability-matrix.json`;
- every Director shot appears exactly once in a backend block and authoring
  unit;
- time coverage is continuous and unit boundaries contain whole shots;
- evidence and warnings are preserved without subjective reinterpretation.

Return a compact recovery report to the Parent with the last trustworthy plan
identity, available artifacts, concrete mismatch, and safest next owner. Do not
repair the record, convert it into a v1 plan, or continue an old Planner →
Integrator → Render chain as though it were the current workflow.