wantsong
/
video-workbench
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
video-workbench/docs/workflows/slide-task-templates.md

12 KiB
Raw Blame History

Slide Task Templates

Status

  • Status: active template reference.
  • Companion workflow: docs/workflows/slide-task-orchestration.md.

Copy these structures into project-local task and slide files as needed. Keep them compact; do not turn production work into audit reports.

Use two lines:

  • production-light: normal production after the project look has been proven. Default review mode is none.
  • test/audit: core-shot proving, workflow debugging, failure investigation, or explicit user-requested review. Richer records are allowed.

Task Plan

Production-light form:

# <Task Title>

## Active Scope

- Line: production-light
- Worker profile:
- Running mode:
- Review mode: none
- Slides:
- Child session:
- Callback target:
- Write policy: append-only; overwrite allowed: no
- Status:

## Context To Use

## Stop Conditions

Use a longer plan only in test/audit.

# <Task Title>

## Status

- Task id:
- Worker profile:
- Running mode:
- Status:

## User Instruction

## Slide Scope

## Child Session Split

## Shared Context

## Visual-System Usage

## Generation Evidence Policy

## Rules

## Expected Outputs

## User Review / Sampling Plan

## Stop Conditions

Task Log

Production-light form:

# Task Log

## Status

## Dispatch / Callback Receipts

- YYYY-MM-DD HH:MM dispatch: <session>, <scope>, <line>, <review mode>, <callback target>
- YYYY-MM-DD HH:MM callback: <status>, <topology>, <versions>, <handoff path>, <image paths>, <needs_user>

## Slide Status Summary

## Open Decisions

Production Run Status

Use this for any production request that may continue across multiple child sessions or survive parent-session compression. Keep it current and compact.

# Production Run Status

## Status

- Project:
- Lifecycle phase:
- Line:
- Running mode:
- Review mode:
- Package size:
- User confirmation:
- Current status:

## Scope

- Total target units:
- Completed units:
- Active child session:
- Next cursor:

## Callback Target

- Parent thread:
- Callback mode:

## Latest Callback

- Status:
- Topology:
- Resolved versions:
- Handoff path:
- Image paths:
- Problems:
- Needs user:

## Stop Conditions

Field rules:

  • Package size records the default or the task-specific validation override.
  • Completed units should list only units completed in the current production run, not every historical accepted unit.
  • Next cursor is the next unresolved unit in the authorized target set.
  • User confirmation says whether a clean callback may continue automatically or must pause for user visual confirmation.
  • Latest Callback is updated by the parent after callback. A child session must not update project files after sending the callback.
  • Do not paste prompt text, full file inventories, or image review notes into this file.

Child Session Plan

Use this only when the child needs its own local plan. Normal production-light packages can proceed from the parent dispatch plus the compact handoff.

Production-light form:

# Child Session NN Plan

- Line: production-light
- Parent task:
- Parent callback target:
- Assigned slides:
- Running mode:
- Review mode: none
- Write policy: append-only; overwrite allowed: no
- Shared context:
- Visual-system files:
- Topology: direct-child; no Agent/SubAgent unless explicitly requested
- Stop conditions:
- Callback final action: after the child sends a successful callback, it must not write or verify additional project files.

Child Session Handoff

Production-light form:

# Child Session NN Handoff

- Status:
- Topology: direct-child | test/audit-with-agent | repair
- Callback: ready-to-send-as-final-action | blocked | not required
- Review mode: none
- Resolved versions:
- Image paths:
- Problems:
- Needs user:
- Observed elapsed/context:
- Parent summary:

Handoff field rules:

  • Status states complete, blocked, failed, or warning.
  • Topology is direct-child for normal production-light. Use test/audit-with-agent only when the task explicitly uses internal slide workers.
  • Review mode states none for production-light unless the task explicitly changed it.
  • Resolved versions and Image paths are the main continuation surface.
  • Observed elapsed/context is optional and should be filled only when visible to the child or reported by the user.
  • Parent summary should be short enough that the parent can continue without opening prompt, ledger, or image files when status is clean.
  • Do not include full file inventories, narrative timelines, or copied prompt text in a production-light handoff.

Callback payload rules:

  • Send the callback only after all allowed output files, slides/slides.md updates, narrow required checks, and child-session-handoff.md are complete.
  • The callback is the child session's final action. Do not update the handoff, run closeout checks, or write any project file after a successful callback.
  • The production-light callback should include status, topology, resolved versions, handoff path, image paths if complete, and any problems or user decisions needed.
  • Do not add a routine final verification pass, hashes, or per-file inventory to a clean production-light callback.
  • If callback cannot be sent, record the failure in Callback Status; the parent may then use the task's recorded polling fallback or user intervention path.

Slide Agent Packet

Use this only in test/audit, explicit review, repair, exception handling, or a deliberately isolated single-slide run. Production-light defaults to the child session writing the brief, prompt, image, slides.md update, and handoff directly.

# S-NN Slide Agent Packet V1

## Status

## Target Slide

## Allowed Actions

## Input Files

## Output Files

## Artifact Version / Write Policy

## Reference Roles

## Visual-System Requirements

## Gpt-Image-2 Advisor Rule

## Host Generation Evidence Rule

## Generation Rule

## Review Rule

## Completion Gate Rule

## Lifecycle Rule

## Return File

Slide Agent Return

Use this only when a slide agent was actually launched. Production-light direct-child packages do not write slide-agent returns.

Test/audit or exception form:

# S-NN Slide Agent Return V1

- Status:
- Slide/version:
- Prompt:
- Image:
- Review mode: none
- Completeness gate:
- Advisor / host-native:
- Reference roles loaded:
- Agent lifecycle: terminal
- Blockers:
- Parent summary:

Return field rules:

  • Completeness gate records only the required receipt facts: expected files exist, append-only version, no-overwrite status, reference loading status, and review absence/presence according to packet.
  • Agent lifecycle states that this worker is terminal / closed after this return.
  • Parent summary should be short and suitable for copying into the child-session handoff.
  • A return with blocked, failed, or warning must name the exact artifact or condition that the child/main session should inspect.
  • Do not add a narrative review, full file inventory, or long source audit to the return. Production-light direct-child packages should not write this return at all.

Slide Design

Use this for cover pages, PPT pages, science-video pages, title cards, explainers, and any slide that needs later human layout, typography, text placement, or post-production. Ordinary MV shot slides may skip this and start at Slide Brief. The default sNN-vN-design.md is written in Chinese. If an English companion is needed, add sNN-vN-design-en.md beside it.

# S-NN Slide Design V1

## Status

## Design Purpose

## Discussion Summary

## Visual Concept

## Image Base Requirements

## Text / Typography Plan

## Layout / Safe Areas

## Color Guidance

## Post-Production Notes

## Constraints / Avoid

## Confirmation Gate

Design field rules:

  • Write the default sNN-vN-design.md in Chinese unless the user explicitly asks otherwise.
  • Use sNN-vN-design-en.md only as an optional English companion or translation; it must not replace the Chinese default.
  • Design Purpose says who the design is for and why a separate design file is needed.
  • Discussion Summary captures the user-approved design direction and tradeoffs.
  • Image Base Requirements describes what the generated image should and should not contain; if text will be added later, explicitly say the generated image must contain no text.
  • Text / Typography Plan, Layout / Safe Areas, and Color Guidance are for human post-production, not for image generation unless the task explicitly asks to render text into the image.
  • Confirmation Gate states what must be confirmed before brief, prompt, or image generation starts.

Slide Brief

# S-NN Slide Brief V1

## Status

## Source Basis

## Slide Function

## First Read

## Risk Class

## Reference Plan

## Visual Requirements

## Character Handling

## Composition / Scale

## Light / Color / Texture

## Forbidden Drift

## Acceptance Checklist

## Prompt Handoff

Brief field rules:

  • Source Basis lists only key sources.
  • Risk Class uses values such as environment-only, object/body detail, distant human, medium human, close/face human, core motif, or repair.
  • Reference Plan must name the active style module and any active character references.
  • Visible character slides must select character reference images from visual-system/characters/character-reference-registry.md.
  • Prompt Handoff tells the child session, or the slide agent when one is used, what must be carried into the prompt.

For Video Workbench image generation, the brief should treat gpt-image-2 as prompt/spec Advisor only. It should not require or expect Garden/API execution unless the task plan explicitly changes the project policy.

Slide Prompt

# S-NN Slide Prompt V1

## Status

## Based On Brief

## Reference Inputs

## Operation Notes

## Advisor / Host-Native Record

## Final Prompt

## Negative / Avoid

## Output Intent

Prompt field rules:

  • Based On Brief links to sNN-vN-brief.md.
  • Reference Inputs lists actual image references and roles.
  • Operation Notes records only generation-relevant steps.
  • Advisor / Host-Native Record records the gpt-image-2 mode result, the Skill/template files used for prompt/spec construction, and that Garden/API execution is not expected by default.
  • Final Prompt should be copyable into another image-generation platform with minimal cleanup.
  • Do not put long project explanation, detailed source audit, review conclusions, or task orchestration history in normal prompt files.
  • For Video Workbench, final prompts may name local paths for traceability, but the prompt must also say that the actual reference image must be loaded into visible context before host image generation when identity/reference control matters.

Artifact version / write policy rules:

  • Use a new slide version for every new task execution. Do not reuse an existing vN just because an earlier version is incomplete.
  • Resolve the version by scanning existing slides/sNN/sNN-v*-* files and choosing the next unused integer.
  • The child session, and any slide-agent packet when one is used, must state Overwrite allowed: no by default.
  • Before writing any output path, check whether the target file exists. If it exists and overwrite is not explicitly authorized for that exact file, stop and return an artifact-collision blocker.
  • Do not backfill missing brief or prompt files for an old generated image as if they were original generation inputs. If backfill is needed for analysis, label it as reconstruction / audit, not as the original prompt.

Slide Review

Use this only in test/audit or explicit review tasks. Production-light default is no review file.

# S-NN Slide Review V1

## Status

## Generation Trace

## Host Generation Evidence

## Local File Check

## Local Visual Check

## Acceptance Checklist

## Issues

## Decision / Next Action

Review field rules:

  • Use local capabilities by default.
  • Do not call Minimax MCP unless the user explicitly authorizes it for the task.
  • For character-visible slides, record whether the required character reference image was loaded.
  • For style-sensitive slides, record whether the active style module was used.
  • Host Generation Evidence should record Garden/API expected: no unless the task explicitly changes policy, the visible-context image roles actually loaded, the host generated-image source path, the copied project image path, and any hash/file verification performed.