| name | sci-issue-intake |
| description | Use when a SCI paper task begins from a vague request, reviewer comment, advisor feedback, suspected flaw, manuscript confusion, or multi-step repair need |
SCI Issue Intake
Overview
Convert a messy paper problem into a bounded revision brief before touching manuscript text.
Core principle: no manuscript edit until the issue type, evidence need, and success criteria are explicit.
Intake Fields
Use the fields below directly. If the project has an issue-intake template, update that template too.
Minimum fields:
- project and paper version
- user concern or reviewer comment
- affected section/file
- issue type: citation, claim, method, result, figure/table, LaTeX, submission, marketing
- evidence needed
- what must not change
- success criteria
Classification
| Issue type | Next branch |
|---|
| Citation or related work | sci-literature-vetting |
| Prose quality or section logic | sci-paper-revision |
| Results interpretation | sci-evidence-discussion |
| Prior-work comparison | sci-comparative-positioning |
| Submission readiness | sci-reviewer-preflight |
| TeX/package/reference breakage | sci-latex-editing |
Output
Produce a short brief:
- issue summary
- target files/sections
- evidence bundle to collect
- branch skill to use next
- open questions, only if blocking
Common Mistakes
- Treating reviewer tone as truth without mapping it to evidence.
- Jumping to a rewrite before identifying the claim being repaired.
- Letting one issue expand into a whole-paper rewrite.
