final-delivery-clean

name	final-delivery-clean
description	Strip workflow notes, engineering meta text, status remarks, workspace references, and other process-facing language from any final deliverable such as a PPT, DOCX, PDF, report, manuscript, or submission package. Use when preparing a final export, submission-ready artifact, or client-facing handoff.

Final Delivery Clean

Apply this skill whenever the user is asking for a final deliverable, export, submission package, or presentation/report/manuscript that will be handed in, presented, or sent to others.

Goal

Final artifacts must read like finished deliverables, not like working files. Remove process-facing language before delivery.

Always Remove

Delete any wording that sounds like:

• workflow status
• working notes
• engineering meta text
• export/build remarks
• workspace or file-management comments
• comments about matching, syncing, rebuilding, or where files are saved

Common examples that must not appear in final outputs:

• current script matched
• latest PPT
• submission folder
• workspace
• build script
• for editing and rehearsal
• speaker notes were removed
• current PPT build

Required Checks

Before delivering any final artifact:

1. Scan visible text for process/meta wording.
2. Remove or rewrite anything that reads like an internal note.
3. If the artifact is generated by script, hardcode a denylist or validation step so banned wording cannot pass through silently.
4. Re-export the final artifact.
5. Verify the exported file itself, not just the source text.

Output Standard

The final file should contain only user-facing content:

• real slide/report/document text
• citations or references if needed
• labels that belong to the deliverable itself

It must not contain internal production notes, project-management remarks, or build/export commentary.