What problem does it solve? Deleting a technical note, presentation deck, or presenter's companion from a study repository by hand risks breaking manifests, catalogs, and inbound links. This Skill performs scoped companion deletion that removes only the selected companion and its owned outputs while keeping the parent study intact. ## Core Features & Use Cases - Scoped companion deletion: Removes a technical/research note, deck, or presenter's companion together with its owned HTML, PDF, DOCX, and notes JSON outputs. - Manifest and metadata preservation: Updates deck/companion manifests by exact source identity while preserving the parent study's canonical files, Edited-on/Status fields, catalog, and proposal metadata. - Validated execution: Supports dry-run preview, rejects canonical study files and out-of-scope paths, validates the full plan before writing, and can recover manifest entries from a base ref. - Use Case: A study has an outdated deck and presenter companion. Run the removal script with both filenames in dry-run mode, review the owned-file list, then execute and finalize so the parent study and its catalog remain consistent. ## Quick Start Ask the assistant to remove the companion files Technical-Note-Example.md and Deck.pptx from the study with slug <Slug> using a dry run first, then confirm the deletion and run the shared finalizer.
