RW Journal Submission

Initiation

1. Read

   references/standalone.md

   ,

   references/method.md

   and

   references/standards.md

   .
2. Read the materials provided by the user in this round; if no materials are provided, only complete the parts allowed by the current evidence.
3. Retrieve

   references/atoms.jsonl

   when rule judgment is required; read

   references/cases.md

   when encountering similar tasks.
4. Read

   references/domain-guide.md

   when selecting methods or tools, and use

   assets/worksheet.md

   to organize deliverables.
5. Read

   references/acceptance.md

   .

   references/behavior-tests.json

   is only used for testing and not as factual information for user tasks.
6. When current literature, APIs, report specifications and journal requirements may change, open the official links in

   references/source-map.md

   for verification and record the date.

Work Stages

1. Confirm the paper type, research scope, methodology, target audience, authors and submission restrictions.
2. Verify the scope, article types, fees, formatting, data and AI policies from the official pages of candidate journals.
3. Compare journals using the same criteria, and record the page URLs and verification dates.
4. Establish the main manuscript, title page, figures and tables, supplementary materials, checklists, disclosures and author contribution lists.
5. Prepare a Cover Letter that only states verifiable facts, without promising acceptance probabilities.
6. Split editor and reviewer comments into stable numbered items, retaining the original text, proposer, round, requirements and dependencies.
7. Record processing actions, revision locations, evidence, reasons for disagreement and items to be confirmed by authors item by item, then cross-check the response letter with the revised manuscript.

Operating Rules

• Journal requirements may change; current official pages must be verified before submission.
• Journal scope, article type and methodology adaptation take priority over impact metrics.
• Open access fees, page charges and other fees must be verified separately.
• Author eligibility, contribution roles and author order must be confirmed by the author team.
• CRediT records contribution roles but does not independently determine author eligibility.
• The Cover Letter does not repeat the abstract nor fabricate editor interests.
• Status of duplicate submissions, related manuscripts and preprints must be disclosed in accordance with journal and ICMJE requirements.
• Conflict of interest, funding, ethics, data and AI usage statements must be checked separately.
• Each reviewer response must point to the revision location or explain why no changes are made.
• When a single comment contains multiple requirements, split it into sub-items; retain cross-references when the same revision addresses multiple comments.
• Each response uses statuses: pending, processed, pending author confirmation, disagree, and blocked; do not directly mark model-generated responses as completed.
• Revision locations use page numbers and line numbers, sections and paragraphs, or stable block IDs; mark old locations as invalid after version changes.
• When disagreeing with reviewer comments, respond with methodology and evidence, do not evaluate the reviewer.
• The revised manuscript, final manuscript, response letter and supplementary documents must use the same version tracking system.
• Do not claim current acceptance probabilities or processing times based on historical experience.

Outputs

• Journal comparisons with official sources and dates.
• List of submission documents, disclosures and versions.
• Response tracking sheet with stable comment numbers, statuses, revision locations and evidence.

Stop Conditions

• Do not mark submission preparation as complete when unable to access the current official requirements of the journal.
• Do not fabricate editor names, preferences, fees, time limits or acceptance probabilities.
• Stop the final submission checklist when there are disputes over authors or disclosures.
• Do not perform unauthorized actual submissions or external sending.

Standalone Operation

• By default, do not read private workspaces, personal corpus directories or preset research-lab.
• Files, text, links and data provided by the user are inputs for the current task, not installation dependencies.
• When the network is unavailable, continue using stable methods within the Skill; mark parts requiring current facts as pending verification.
• Can connect with other research Skills in this package when available; when installed separately, directly return instructions for the next step without stopping the current task.

Source Discipline

• Separate user materials, public sources, current inferences and unknown items.
• Report specifications only check reporting transparency, do not automatically prove design quality.
• Public source summaries are stored within the Skill; return to official pages when needing versions, fees, policies, APIs or current journal statuses.
• Do not generate non-existent papers, data, DOIs, tool operation results or journal requirements.