Content
New
$10.00Release Notes
Turn approved software changes into accurate release notes with source traceability, audience variants, migration actions, known issues, and a publication handoff.
release noteschangelog
T
talvio
Updated Jul 25, 2026
Turn controlled source material into an editable, source-traceable presentation with a clear argument, accessible slides, exact-output QA, and an approved handoff.
A presentation can look finished while the numbers came from the wrong spreadsheet, the notes contradict the slide, the charts are flattened, or the PDF hides a broken editable file. Those failures tend to appear late, when someone is already waiting for the deck.
Presentation Production treats the deck as a controlled professional deliverable. It starts with source identity, claim state, audience, authority, and acceptance criteria. It then builds the argument, maps each slide to one takeaway and its supporting evidence, chooses an appropriate visual form, and keeps speaker context, citations, accessibility, and editability attached to the work.
The workflow covers new decks, template-based revisions, pitch presentations, research updates, decision briefs, training material, reports, and proposals. It separates factual, content, brand, accessibility, and release approval. It also defines structural, claim, render, visual, editability, and PDF checks against the exact candidate hash. If a save or export times out, it preserves the ambiguous output and last-known-good copy before any retry.
This package does not invent evidence, approve claims, guarantee persuasion, or claim that an openable or clean-looking file is verified. It produces the strongest lifecycle state the supplied evidence and authority support, then names the next check or decision needed.
Version 1.0.0 was reviewed on 2026-07-23 for Codex using gpt-5.6-sol in fresh read-only contexts. Across three supplied planning and recovery cases, the exact package scored 98.33, compared with 66.25 for the baseline agent and 65.42 for the exact free upstream revision. All three candidate cases passed. Those results are bound to the reviewed package; they do not prove compatibility with every PowerPoint version, template, font, chart type, accessibility checker, projector, or customer workflow. Maintenance and install support are handled by the platform-operated publisher for this listing.
Input
Build a 12-slide pitch plan from a board-approved metrics file and newer founder notes with higher, unsupported numbers. I can edit but cannot approve, overwrite, or distribute.
Output
A source and claim register that preserves the conflict, a bounded argument and slide manifest, rejected unsupported claims, editable chart and citation requirements, exact-output QA plan, blocked authorities, and one owner decision needed next.
Input
Plan an eight-slide clinical research update from a locked CSV and a PI interpretation. Confidence intervals, adverse events, and the clinical threshold are missing. Use the hospital template without changing masters.
Provide the objective, audience, setting, runtime, owner, approver, delivery formats, source paths or stable IDs, revisions and hashes when available, template constraints, required claims, accessibility target, and your read, edit, approval, replacement, and distribution authority. Ask to plan, produce, revise, review, recover, or hand off the presentation. Missing evidence stays visible instead of becoming polished fiction.
Objective, audience, setting, duration, owner, approver, deadline, language, aspect ratio, delivery variants, and acceptance criteria.
Source files or stable identifiers with revisions, hashes when available, owners, reporting periods, claim states, conflicts, and required attribution.
Template and brand rules, fonts and asset rights, accessibility target, available presentation and rendering tools, and explicit edit, replace, approve, distribute, and publish authority.
SKILL.md; evidence-controlled presentation lifecycle; argument and slide-manifest framework; template, visual, accessibility, review, exact-output QA, delivery, and recovery controls; canonical handoff contract
No reviews yet.
Output
A claim-safe eight-slide architecture, visible uncertainty and missing-data disclosures, editable visual specifications, notes and citations, projection and accessibility controls, template-fidelity checks, separate PI and accessibility approvals, and a planned verdict.
Input
A save timed out after writing a staging PPTX. The path exists but its contents are unknown. Rerun to the same path and replace the previous version.
Output
An evidence hold, read-only reconciliation plan, exact-hash structural and visual checks, five outcome branches, a new path for any later retry, last-known-good protection, blocked replacement, and one safe next action.
Creator
Ssivaro