# Content handoff

Report structure and production are separate responsibilities. The optional `report-structure` Skill maintains report logic, chapter relationships, page order, page content allocation and learning from user examples. This Skill owns template selection, visual composition, native objects, shared layout recipes, source projects and production evidence. Neither requires the other to be installed.

## Receive a plan

Accept a readable outline or page plan; no special file schema or compiler integration is required. Reuse stable page IDs and the user's agreed review sequence. For the current page, identify its purpose, what the audience should understand, content, evidence, necessary qualifications, progression within the page, relationship to adjacent pages, and allocation between visible content and speaker notes or appendix. A summary that introduces groups should match the actual groups and their organizing basis.

For the extended structure workflow, receive the current lightweight page-explanation PDF and its editable page source together, along with the confirmed content scope, audience/professional starting point and execution choices. A slide's explanation may span several physical PDF pages; use stable slide IDs rather than assuming PDF page numbers equal slide numbers. Take actual slide text, formulas, required visual descriptions, dependencies and transitions from the editable source. Preserve its separation of screen content, required visuals and speaker/review analysis; analysis does not automatically become slide text. No reverse PDF parsing or installed structure Skill is required. Ordinary user plans remain supported without this specific PDF delivery format.

The source identifies the contribution or judgment supported by the report, section and current page, including whether a portion presents a result or an objective analysis. Make each text/visual group serve those goals. Preserve required visual objects, relationships, directions, labels, data/sources and presentation order; optional decoration or equivalent visual expression follows production authorization. An addition that changes a fact, cause, conclusion strength or necessary premise first returns to the content plan. Do not default to adding limitations or self-undermining endings.

Reuse the [confirmed execution choices](execution-and-review.md): specialist reviews and assignments, review after revision, page/block mode, ImageGen scope/budget and any selected alternatives. Ask once for consequential unresolved production choices, not for choices already supplied. A refusal alone does not identify a replacement Agent or tool.

For reasoning or mathematical derivation, retain the necessary premises, definitions, key steps and conditions that make the next step valid. Show the exact premises again where the audience needs them. A task that explicitly needs only results may omit the derivation; keep the result's meaning, conditions and sources. Identify which evidence supports each conclusion and how the page should make that association visible. These details can live in the existing brief rather than additional required fields. A time constraint concerns the overall report or relevant sections; a time budget for every page is not required.

Select layout and composition from those information relationships under the chosen template. Check the actual page's reading order, information burden and conclusion-to-evidence associations. Keep essential explanations and qualifications in the related main information; small text may retain sources, ranges, references and supplementary definitions. Fix ambiguous or overstrong body text directly, and remove preventive disclaimers that add no useful understanding or action. Preserve facts, numbers, source meaning and content boundaries even when the plan came from another Skill. A supplied plan is input, not proof of truth or authorization to generate all pages.

Without a plan, establish enough content context to complete the authorized page or deck request. Do not stop ordinary production merely because `report-structure` is unavailable. Use that Skill when the task calls for substantive report planning, restructuring or learning from examples; avoid duplicating its evolving rules here.

## Return a content issue

When the declared typography, spacing and supported layouts cannot accommodate the content, report the affected page IDs, missing relationship or capacity issue and a concrete content option. Options may include removing a true duplicate, using a supported layout, moving optional detail, or splitting a complete argument with a clear transition. Preserve the user's locked content and existing authorization; do not shrink fonts, alter fixed gaps or conceal key conditions to make a page fit.

The content owner resolves chapter/order/selection changes. For one Agent handling both responsibilities, revise the content plan first and then produce the affected authorized pages; no extra peer or approval round is required for settled, reversible work. When order or page allocation changes, synchronize stable IDs and their destinations, page numbers, references and speaker notes. Keep necessary premises and key steps connected across a split.

When source content or speaker explanation changes, return the affected IDs and source revision so the content owner can synchronize the current PDF and related analysis. Distinguish the received version from a later draft; an older PDF or approval does not validate changed content. Apply the agreed independent-review assignment to affected production revisions through [review after revision](execution-and-review.md#review-after-revision).

User feedback about report logic goes to the structure Skill's maintained example/rule source when authorized. Feedback about fonts, spacing, layout recipes or template geometry stays with the production/template maintainer. A content-plan review does not establish visual, native-editing or projection acceptance.