Introduction

The folder-first workflow, generated deliverables, and local PDF/LaTeX workspace.

DOCUMENTEDUPDATED AUG 2026

Anything-to-Journal is a folder-first agent skill. Give it the complete context of a research project and it produces a journal manuscript that remains easy to inspect, compile, and edit.

The core loop#

01Collect

Create a dedicated folder and add every useful source.

02Confirm

You choose draft mode or a specific journal template.

03Inspect

Only then does the agent read and classify every material.

04Generate

The agent writes, compiles, checks, and packages the journal.

The confirmation step is part of the contract and happens before source-content access. The agent may locate the folder by filename, but it must not infer a target journal from scattered hints or inspect evidence before your answer.

What goes in#

The workspace can contain notes, drafts, PDFs, spreadsheets, structured data, figures, code outputs, transcripts, citations, and submission instructions. Formats can be mixed; usefulness matters more than tidiness.

TEXTNotes & drafts

Markdown, plain text, Word, and prior manuscripts.

DATATables & results

CSV, TSV, spreadsheets, and exported summaries.

MEDIAFigures & diagrams

Publication-ready images and working graphics.

CITEReferences

BibTeX libraries, source PDFs, and citation notes.

What comes out#

The primary handoff is a plain, editable LaTeX project plus a compiled preview and a short generation report. When supported, the agent also starts the local Manuscript Workspace: one localhost page with a scrollable PDF Preview and a LaTeX editor connected to the actual generated source. The Overleaf copy remains bundled separately so the entire project can be uploaded in one step.

OUTPUT TREE

journal-output/
├── manuscript/
│   ├── manuscript.tex
│   ├── references.bib
│   ├── traceability.csv
│   └── evidence-map.csv
├── reports/
│   ├── source-review.json
│   └── quality-report.md
└── submission/
    ├── overleaf-upload.zip     ← upload this
    ├── overleaf-upload/
    │   ├── main.tex            ← ZIP root
    │   ├── references.bib
    │   └── README_OVERLEAF.md
    ├── manuscript.pdf
    └── submission-package.zip

Design principles#

Evidence before prose. Claims should trace back to the source folder.
Explicit uncertainty. Missing evidence becomes a visible gap, not invented content.
Human-editable output. Sections, figures, and references stay in ordinary files.
Synchronized local editing. Codex and the browser workspace share the same LaTeX source.
Portable handoff. The output works in the local workspace and can still be uploaded to Overleaf.
Template fidelity. Journal-specific formatting is used only when supplied and confirmed.

NEXT GUIDE / 01Run your first journal workflow↗