Workflow gallery

These examples show a reliable pattern for document work: identify the source of truth, create a separate output, inspect the real file, and recover cleanly when the result is wrong.

Before you run a workflow#

1. Put the source files in one project.
2. Open the main source document.
3. Save the source and create a copy when it cannot be replaced.
4. Add supporting files with @ or as attachments.
5. Ask for output under exports/ or another explicit destination.

For consequential work, ask for a plan before allowing edits.

Refine a Word report#

Start with the DOCX open in the paginated editor. Ask for an audit that does not edit:

Audit @customer-research-report.docx for repeated findings, inconsistent headings, weak evidence links, and tables that are difficult to scan. Report issues by section and page. Do not edit the document.

Then request one bounded pass:

Revise only the Executive Summary using the approved findings already in the report. Preserve its styles, header, footer, tables, quotes, and every number. Show the document changes for review.

Open Word documents for the full editor and compatibility checklist.

Verify the updated pages, not only the agent response. Check page count, text wrap, heading styles, and whether the summary still matches the detailed findings.

Turn a workbook into an executive brief#

Open the workbook and identify its authoritative sheet before asking for prose.

Inspect @portfolio-review.xlsx. Identify the source sheets for actual spend, forecast, delivery status, and risk. Flag structural or formula warnings and wait for my approval.

After confirming the definitions:

Create exports/portfolio-decision-brief.docx from the approved Summary and Risk Register sheets. Include the three largest variances, the owner and due date for every high risk, and a source-cell reference for each number. Do not edit the workbook.

Compare the DOCX with the workbook. A polished paragraph is still wrong if a filter, unit, sign, or date boundary changed.

See Spreadsheets for formula review and CSV limits.

Turn a LaTeX paper into a research talk#

Compile the paper first so the source and rendered PDF are known-good.

Read @paper.tex, @references.bib, and the compiled paper. Plan a six-slide research talk for an applied-ML audience: question, prior limitation, method, strongest result, limitations, and next step. Use claims from the paper only and wait for approval before creating a deck.

Then create a separate output:

Create exports/research-talk.pptx from the approved plan. Add concise speaker notes with source section and citation keys. Do not change the LaTeX project.

Inspect the deck at slide size. Verify claims, equations, figure labels, citations, and text fit. The presentation editor does not replace a final PowerPoint compatibility check.

Use LaTeX & research for compilation and shell-escape safety.

Turn a PowerPoint review into a decision brief#

A working deck often contains the approved narrative, evidence, operating plan, and speaker notes. Start with the PPTX as the source rather than creating another presentation.

Read slides 1–8 and speaker notes in @guided-setup-launch-review.pptx. List the recommendation, pilot size, success thresholds, owners, dates, open risks, and stop rule. Cite the source slide or note for each item. Do not edit the deck.

Create a durable memo for the next audience:

Create exports/guided-setup-decision-brief.docx for Product Council. Preserve every threshold, comparison operator, unit, owner, and date. Include decision required, evidence, rollout plan, risks, and stop rule. Cite the supporting slide for each decision and keep the PPTX unchanged.

Review the memo against the deck and its notes. Pay special attention to words such as at least, below, and within; removing one can reverse a threshold.

See Presentations for slide editing and deck audits.

Review every generated deliverable#

Use the same handoff check across formats:

• The source files were not overwritten.
• Every number and claim maps to an authoritative source.
• The output path and file type are correct.
• Page, slide, sheet, and chart layout were inspected.
• Pending changes were accepted or discarded deliberately.
• The saved file was reopened before delivery.

If the result is too broad, discard the pending review or recover the last good state. Then ask for one section, sheet, or slide range at a time. See Review changes & recover.