ppt-planner

# PPT Planner

Read only after `ppt-router` chooses `CREATE` or `OUTLINE`. Planning is the source of truth for construction, not optional prose around the deck.

## 1. Presentation brief

Lock these fields from the request and inspected materials:

- audience and decision, learning, sales, or communication job;
- desired audience action or takeaway;
- language, slide-count range, tone, and content density;
- source boundary: supplied-only, supplied-plus-current-research, or clearly labeled draft assumptions;
- must-include, must-avoid, confidentiality, brand, and template/reference constraints;
- delivery format and aspect ratio; default to editable `.pptx` and 16:9 when unspecified.

When the user explicitly supplies slide titles, labels, or an ordered page
list, record those visible strings and their order as a verbatim content
contract. Do not improve, synonymize, shorten, or replace them with autonomous
assertion titles. Assertion-title guidance applies only where the user did not
fix the visible wording.

Ask only when a missing answer would change the deck's purpose, evidence boundary, or deliverable. Otherwise choose a sensible default and record it.

## 2. Visual source and references

Resolve one visual source before choosing an art direction:

- `autonomous`: no visual reference exists. This is a normal, complete path. Do not ask the user to find a reference and do not reduce the deck to a generic title-and-bullets template. Derive a suitable visual character from the audience, communication job, subject matter, tone, and available evidence.
- `text-direction`: translate the user's words into a usable visual system without inventing a named brand or claiming an exact external style match.
- `reference-image`: inspect every supplied reference image and extract only the relevant visual signals: palette hierarchy, canvas/background treatment, typography character, grid and alignment, whitespace, dominant-object scale, image crop/focal point, surface treatment, and recurring motifs. Record uncertain inferences as low confidence. A reference image is not a reusable slide asset unless the user supplied or authorized it for reuse.
- `reference-deck`: decide whether the PPTX is `inspiration` or an authorized `template-source`. Inspect all source slides structurally. For strict template following, also render and inspect every source slide before mapping output roles to reusable source patterns; for inspiration, render enough slides to cover every recurring layout family and the opening/section/data/close roles. Extract theme colors, font evidence, margins, alignment lines, background language, image treatment, chart/table treatment, recurring furniture, and slide-role patterns.
- `existing-deck`: preserve its current visual system unless the user authorizes a bounded redesign.

Reference material is production input, not a routine clarification trigger.
When its role is explicit, inspect it before requesting optional business copy.
If the deck topic, customer facts, product proof, or quarterly values are still
missing, complete the structure with neutral titles and visibly labeled
placeholders or assumptions. Do not end with “send these details and I will
start”; the reference interpretation, story skeleton, visual system, and
production route can all be completed safely first.

If tools are unavailable, distinguish observed evidence from planned evidence:
never claim that a reference was inspected, but still return a self-contained
unexecuted specification naming what will be inspected, which visual-DNA fields
will be extracted, how each output page will adapt them, how the source remains
unchanged, and what structural and rendered evidence will be reviewed. Use
plain presentation language rather than private tool names.

Do not fill an uninspected reference-image record with a plausible palette or
named art direction based on the deck topic. Mark palette, typography,
background, geometry, crop/focal behavior, and motifs as pending reference
inspection. If a construction-ready fallback is useful, label it explicitly as
a provisional autonomous fallback, not as evidence extracted from the image.

Record this compact interpretation:

```yaml
visual_source: autonomous|text-direction|reference-image|reference-deck|existing-deck
reference_mode: none|inspiration|brand-source|template-source|editable-source
reference_strength: loose|balanced|strict
reference_asset_reuse: allowed|reference-only|unknown
visual_dna:
  character: "visual personality appropriate to the communication job"
  palette_behavior: "dominant, support, accent, and semantic-color behavior"
  canvas: "background composition and whitespace behavior"
  typography: "hierarchy and typographic character; exact family only when evidenced"
  geometry: "grid, alignment, scale, and spacing tendencies"
  imagery: "subject, crop, focal point, ratio, and treatment"
  motifs: []
  avoid: []
confidence: high|medium|low
```

References control only their declared role. Record `keep`, `adapt`, and `do_not_copy`. Do not copy third-party logos, unique illustrations, proprietary claims, or exact layouts without authorization. User instructions and authorized brand/reference material override autonomous defaults; narrative clarity and source fidelity still take precedence over irrelevant reference structure.

A known authoring limitation does not require pretending that source inspection
already occurred. When the user requires an unsupported feature with exact
fidelity, state the limitation and preserve the source immediately. Inspect or
render the source only when that evidence can identify a supported preservation
path or user-selectable alternative; do not perform ceremonial inspection merely
to restate a capability boundary that is already known.

## 3. Content boundary

Inspect supplied material before outlining and separate user-provided content,
explicit draft assumptions, and missing copy. Preserve the visible meaning of
supplied wor