Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 26 additions & 0 deletions .agents/skills/media-motion-graphics/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -161,6 +161,32 @@ use new output names for iterations instead of deleting them preemptively.
For spoken footage, follow `media-subtitle-pipeline`'s project glossary and cached
transcript correction guidance before using transcript copy in the storyboard.

## Generated footage with TTV

Use TTV when a reviewed scene needs generated footage. Export the selected
`STORYBOARD.md` scenes to `$PROJECT_DIR/storyboards/<revision>.json` using the
scene shape in `docs/generated-media.md`. Preserve scene IDs, scene order,
durations, entry/exit intent, references, delivery dimensions, and continuity.
Include a `motion_review` record with review mode, reviewer, disposition, and
paths and SHA-256 hashes of the storyboard, review images, and `review.md`.
Archive those files alongside the JSON revision. Mark `approved: true` only
after the selected review process has passed.

Creative review and spending permission are separate records. Carry the user's
existing permission to use providers and the agreed budget into `DECISIONS.md`;
auto review alone does not authorize paid generation. Review the returned TTV
plan's exact prompts, model, variants, duration, references, and costs before
creating `media-generated approve`. Use a keyframe-only approval and a cited
keyframe result when first/last frames need visual review before video generation.

Import approved results and select their takes through `media-generated`.
Use the imported clips as content layers in HyperFrames; keep text, UI, layout,
crop, timing, and overlays editable in the composition. Director notes on those
elements revise HyperFrames source. Notes that change generated footage create a
new TTV request for the affected scene IDs. Keep neighboring takes and resolve
any stale continuity dependencies. See `docs/generated-media.md` for the handoff
example, selection provenance, and portrait EDL options.

## Verification and handoff

Use `lint` for early feedback and `check --snapshots --at-transitions` for the
Expand Down
18 changes: 18 additions & 0 deletions .agents/skills/media-render-pipeline/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,14 @@ Delegate to the appropriate sub-skill when a step's work falls entirely within
its scope. This skill adds the conversation, strategy, self-evaluation, and
iteration layers that the sub-skills do not cover.

For generated footage, export reviewed `media-motion-graphics` storyboard scenes
using `docs/generated-media.md`, preserve stable IDs and visual review evidence,
and use `media-generated` for provider plan approval, import, and take selection.
Carry existing spending permission and budgets into the plan approval. Use
imported clips as HyperFrames content layers and retain editable motion source.
`select --edl-options` preserves portrait reframing and transcript paths together
with grading, overlays, and subtitles.

## Worker/subagent protocol

If the harness supports workers, use them for independent, bounded side work to
Expand Down Expand Up @@ -396,6 +404,15 @@ Step 8: Iterate on feedback and persist session memory.

## Toolkit commands

For TTV-generated scenes, use `media-generated` to author an approved-storyboard
request, review the provider plan, record exact variant approval, and import the
terminal result. Keep scene IDs and explicit order stable. `media-generated select`
freezes reviewed takes, trims and an ordinary EDL. `media-generated render` checks
source hashes, calls the existing renderer, and records `media-verify` findings.
Use `regenerate` for selected scene subsets and `inspect` for stale continuity.
Documents stay under `rough-cuts/manifests/`. The file/HTTP workflow is documented
in `docs/generated-media.md` in the toolkit repository.

| Command | Pipeline step |
|---------|--------------|
| `media-subtitle` | Step 1 (transcribe) |
Expand All @@ -404,6 +421,7 @@ Step 8: Iterate on feedback and persist session memory.
| `media-tts` | Step 5 (narration) |
| `media-timeline-view` | Steps 1, 5, 6 (on-demand visual drill-down) |
| `media-edl-render` | Steps 5, 8 (render with EDL) |
| `media-generated` | Steps 4-8 (TTV review, imports, selections and verified EDL renders) |
| `media-fcpxml-export` | Step 8 (optional Resolve layer handoff) |
| `media-burn-subtitles` | Step 5 (subtitle burning, usually via EDL render) |
| `media-grade` | Step 5 (standalone grading outside EDL workflow; not needed when using `media-edl-render`) |
Expand Down
108 changes: 0 additions & 108 deletions .github/workflows/ai-pr-review.yml

This file was deleted.

4 changes: 4 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
# Media Tooling

[TTV generated-media integration](docs/generated-media.md) adds reviewed generation
requests, verified imports, immutable take selections and reproducible EDL renders
through `media-generated`.

Media Tooling helps an agent harness turn raw media into planning and editing artifacts while keeping the user centered in the project workspace.

User-facing execution context lives in a project-local `AGENTS.md` generated by `media-tooling-init`. The repo-root [`AGENTS.md`](./AGENTS.md) is intentionally minimal and only supports toolkit development. Developer-only maintenance notes and quality gates live in [`docs/DEVELOPMENT.md`](./docs/DEVELOPMENT.md).
Expand Down
5 changes: 5 additions & 0 deletions docs/DEVELOPMENT.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,6 +41,11 @@ uv run --group dev mypy src tests

## When editing the toolkit

The TTV adapter is `src/media_tooling/generated_media.py`. Its contract schemas
and golden fixtures are pinned data under `src/media_tooling/contracts/`. Keep
the renderer and verifier independent of TTV. See [generated-media.md](generated-media.md)
for the workflow and offline acceptance command.

- prefer updating shared helpers instead of duplicating batch logic
- keep user-facing execution guidance in `src/media_tooling/templates/project_AGENTS.md` rather than the repo root
- keep implementation notes and maintenance guidance here or in other files under `docs/`
Loading