Choose a research task
Describe the result you need in your Host. You can use $qiongli in Codex or a visible workflow shortcut, but you do not need to memorise task IDs. The IDs below help you find the shared guidance and keep records consistent across stages. They are not native CLI subcommands.
Start from your current material
| Goal | Ask the Host | Useful guidance and outputs |
|---|---|---|
| Turn a broad topic into a question | “Help me narrow this topic using the sources I supplied. Show unresolved assumptions.” | A1/A4: research questions, scope and gap memo; add theory or hypothesis work when relevant |
| Build a literature review | “Plan the search for this review, then extract the supplied papers with source locations and limitations.” | B1/B1_5/B2/B3 and relevant synthesis/reporting tasks: search, screening, extraction and literature map |
| Design a study | “Check this design against our question, available data and agreed protocol.” | Stage C: design, variable/data feasibility, rival explanations and justified robustness checks |
| Write from results | “Draft this results section from the approved analysis. Preserve estimates, uncertainty and source references.” | F1/F2/F3 as needed: outline, section or manuscript; use figure and reporting guidance where relevant |
| Build research code | “Implement this method from the supplied specification, then check statistical validity and reproducibility.” | I5/I6/I7/I8/I4: specification, plan, implementation, review and reproducibility record |
| Prepare for submission or revision | “Map these reviewer comments to the manuscript and propose a response for each.” | H1/H2/H3/H4: submission materials, response matrix or source-based critique, according to the request |
| Fix one finding | “Resolve finding I8:P1-01 in this candidate and check only the affected result.” | Keep the finding ID, candidate and relevant checks; no full workflow restart is required |
A code plan should resolve important assumptions before implementation. It does not need to prescribe every routine coding choice. Likewise, a request for one section does not require new files for every research stage.
Journal decisions
If you already chose a journal, ask for an A5 requirement check against the specific article type and submission stage. If you want recommendations from an existing manuscript, H5 starts with its contribution, methods and evidence. Both routes need current sources for decision-relevant journal rules. See journal fit and review.
Save and continue
For a formal project, retain the applicable artifacts under RESEARCH/[topic]/ and use the existing preview and approval process. Carry claim IDs, citekeys, source locations and methodological limits forward. Ask for a stage summary when work is ready to hand over; the summary preserves links to original material and does not delete files. Any file deletion remains your own selection and action.
Use reply only when you want a conversational answer without tools, files or a project workflow. See Skills for the full map, paper-type examples for research routes and the CLI guide for installation and project commands.