# 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

```text
# <Task Title>

## Status

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

## User Instruction

## Slide Scope

## Child Session Split

## Shared Context

## Visual-System Usage

## Rules

## Expected Outputs

## User Review / Sampling Plan

## Stop Conditions
```

## Task Log

```text
# Task Log

## Status

## Timeline

## Child Session Results

## Slide Status Summary

## Open Decisions
```

## Child Session Plan

```text
# Child Session NN Plan

## Status

## Parent Task

## Assigned Slides

## Shared Context To Read

## Visual-System Files To Read

## Per-Slide Work Order

## Agent Packet Paths

## Stop Conditions
```

## Child Session Handoff

```text
# Child Session NN Handoff

## Status

## Completed Slides

## Files Written

## Problems / Repairs Needed

## User Decisions Needed

## Next Session Input
```

## Slide Agent Packet

```text
# S-NN Slide Agent Packet V1

## Status

## Target Slide

## Allowed Actions

## Input Files

## Output Files

## Reference Roles

## Visual-System Requirements

## Gpt-Image-2 Advisor Rule

## Generation Rule

## Review Rule

## Return File
```

## Slide Agent Return

```text
# S-NN Slide Agent Return V1

## Status

## Files Written

## Generation Result

## Review Result

## Blockers

## Next Action
```

## Slide Brief

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

## Slide Prompt

```text
# S-NN Slide Prompt V1

## Status

## Based On Brief

## Reference Inputs

## Operation Notes

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

## Slide Review

```text
# S-NN Slide Review V1

## Status

## Generation Trace

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