Write a research paper
Bring source discovery, notes, figures, and manuscript revisions into one project.
Build the paper around the evidence. Keep the manuscript, source notes, and figures close enough that a revision does not mean reconstructing how you reached the result.
Start the manuscript
Section titled “Start the manuscript”Choose an Article research starter in research project setup, or open a venue template. Pick LaTeX, Typst, or Markdown to match the document and submission you need.
For an existing draft, import the project and continue with its own source files.
Gather sources
Section titled “Gather sources”Search by topic in Citation Search. Add the references you need to the bibliography, then keep short notes on what each paper establishes.
For a broader sweep, use /oleafly-literature-sweep. Give it the research question, date range, and inclusion criteria. Ask for identifiers and a source table you can check. With a CLI agent, the Literature sweep and Related work starting points attach the same skills, even for agents that can’t load Oleafly’s skills on their own.
Draft with the evidence nearby
Section titled “Draft with the evidence nearby”Write beside the PDF and use citation completion as you go. Link a reference folder if your PDFs live outside the project.
When a section needs revision, use an inline edit or ask the assistant to work from the relevant files:
Revise related-work.tex using the notes in research/. Group the papers by method, preserve the citation keys, and mark claims that still need evidence.
Add figures and results
Section titled “Add figures and results”Use the diagram composer for a manual diagram: it draws TikZ for LaTeX, fletcher for Typst, and Mermaid for Markdown. Or ask the assistant for an editable AI figure, written as TikZ in a LaTeX project or CeTZ in a Typst project. For numerical results, keep the analysis script with the generated tables and plots.
Review and submit
Section titled “Review and submit”Run a claim check with /oleafly-verify-claims, read the evidence, and use Preflight to catch mechanical issues. Save a named Git commit for the submitted source, then export the PDF and required source files.