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

7.2 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 them into full audit reports.

Task Plan

# <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

# Task Log

## Status

## Timeline

## Child Session Results

## Slide Status Summary

## Open Decisions

Child Session Plan

# Child Session NN Plan

## Status

## Parent Task

## Parent Callback Contract

## Assigned Slides

## Shared Context To Read

## Visual-System Files To Read

## Artifact Version / Write Policy

## Per-Slide Work Order

## Agent Packet Paths

## Stop Conditions

Child Session Handoff

# Child Session NN Handoff

## Status

## Callback Status

## Completed Slides

## Completion Gate

## Review Mode / Result

## Agent Lifecycle

## Files Written

## Problems / Repairs Needed

## User Decisions Needed

## Parent Summary

## Next Session Input

Handoff field rules:

  • Callback Status records whether callback is required, the parent thread id, the callback mechanism, whether the callback has been sent, and confirms that child-session-handoff.md existed before callback.
  • Completion Gate states pass, blocked, failed, or warning, then lists only the concise evidence needed by the parent.
  • Review Mode / Result states whether review was required, suppressed, completed, or skipped by task rule.
  • Agent Lifecycle lists each slide Agent and confirms terminal / closed status after return.
  • Parent Summary is the main-session consumption surface. It should be short enough that the parent can continue without opening prompt, return, ledger, or image files unless the status is not clean.

Callback payload rules:

  • Send the callback only after child-session-handoff.md exists.
  • The callback should include status, completion gate, resolved versions, handoff path, image paths if complete, and any problems or user decisions needed.
  • 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

# 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

# S-NN Slide Agent Return V1

## Status

## Files Written

## Completeness Gate

## Advisor Result

## Generation Result

## Host Generation Evidence

## Review Result

## Agent Lifecycle

## Blockers

## Parent Summary

## Next Action

Return field rules:

  • Completeness Gate records file existence, append-only version, no-overwrite status, reference loading status, and review presence/absence 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.

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 slide agent 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.
  • A slide-agent packet 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

# 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.