Karen had been asked to find tables that had been pasted into terms and conditions pages as images.
Karen is a pseudonym, and this workflow is based on a real user experience.
The tables needed to be rebuilt as proper Exstream Design objects. That meant recreating the table structure, formatting it to match the original and entering the content as text. Before Karen could start that work, she needed a list of the affected pages.
There were around 250 pages to check.
The manual option
The normal approach was to open each page in Designer and inspect it visually.
Even at 20 seconds per page, checking 250 pages would take more than 80 minutes. That estimate covers only the initial search. It does not include reviewing the tables or rebuilding them.
Asking the repository
Karen did not use the command line herself. She described what she needed to an AI agent.
The agent used the Design CLI from CCMForge Inspect to search the repository for pages containing embedded images. Around one minute later, Karen had the output she wanted: a list of pages to review.
The workflow was read-only. Inspect did not edit the pages, decide which images should be replaced or attempt to rebuild the tables.
Karen made those decisions herself. She used the returned list to open the relevant pages and replace the screenshots manually with proper Design objects.
The result
From 250 page opens to one reviewable list.
Inspect shortened the search. It did not take over the document work.
Manual first pass
~80 min
Open and inspect around 250 pages in Designer.
Inspect with an AI agent
~1 min
Search the repository and return the pages to review.
This is a useful boundary for AI-assisted inspection. The agent can search hundreds of objects and return a result that a person can check. The document developer still decides what the result means and what should change.
See how CCMForge Inspect reads an Exstream Design repository.