1.6 KiB
1.6 KiB
description, args, section, topLevelCli
| description | args | section | topLevelCli |
|---|---|---|---|
| Turn research findings into a polished paper-style draft with equations, sections, and explicit claims. | <topic> | Research Workflows | true |
Write a paper-style draft for: $@
Derive a short slug from the topic (lowercase, hyphens, no filler words, ≤5 words). Use this slug for all files in this run.
Requirements:
- Before writing, outline the draft structure: proposed title, sections, key claims to make, source material to draw from, and a verification log for the critical claims, figures, and calculations. Write the outline to
outputs/.plans/<slug>.md. Present the outline to the user, then continue automatically. Do not block the workflow waiting for confirmation. - Use the
writersubagent when the draft should be produced from already-collected notes, then use theverifiersubagent to add inline citations and verify sources. - Include at minimum: title, abstract, problem statement, related work, method or synthesis, evidence or experiments, limitations, conclusion.
- Use clean Markdown with LaTeX where equations materially help.
- Generate charts with
pi-chartsfor quantitative data, benchmarks, and comparisons. Use Mermaid for architectures and pipelines. Every figure needs a caption. - Before delivery, sweep the draft for any claim that sounds stronger than its support. Mark tentative results as tentative and remove unsupported numerics instead of letting the verifier discover them later.
- Save exactly one draft to
papers/<slug>.md. - End with a
Sourcesappendix with direct URLs for all primary references.