79 lines
3.8 KiB
Markdown
79 lines
3.8 KiB
Markdown
---
|
|
name: qqwrite
|
|
description: Adjust manuscript Word documents to match journal or group writing templates. Use when the user asks QQwrite to format, restructure, clean, or align a .docx manuscript according to a Word template from the local template library, especially for scientific manuscripts, AFM-style templates, section order, title page metadata, abstract/keywords placement, headings, captions, references, SI pointers, and submission-ready Word formatting.
|
|
---
|
|
|
|
# QQwrite
|
|
|
|
QQwrite is the Word-template execution skill for manuscript writing workflows. Its current scope is intentionally narrow: use a template from the local template library to adjust a user's manuscript Word file while preserving scientific meaning. When available, consume a QQsci-checked `qqwrite_brief.json` to guide section order, claim placement, DOI placeholders, and missing-input reporting.
|
|
|
|
## Core Rule
|
|
|
|
Do not overwrite the source manuscript. Always create a revised copy and a short Markdown report.
|
|
|
|
Default outputs:
|
|
|
|
- `*_qqwrite_adjusted.docx`
|
|
- `*_qqwrite_report.md`
|
|
|
|
## Template Library
|
|
|
|
Use bundled templates first:
|
|
|
|
- `assets/templates/afm/article-template.docx` for Advanced Functional Materials-style manuscript formatting.
|
|
|
|
If the user provides another template path, use the user-provided template instead.
|
|
|
|
For template handling details, read `references/template-adjustment.md`.
|
|
|
|
## Workflow
|
|
|
|
1. Identify inputs:
|
|
- source manuscript `.docx`
|
|
- template `.docx`
|
|
- optional QQsci-checked `qqwrite_brief.json`
|
|
- target journal or template name if provided
|
|
- output directory
|
|
|
|
2. Preflight both documents:
|
|
- inspect section order and heading hierarchy
|
|
- compare title page fields, abstract, keywords, main text, methods, references, captions, acknowledgements, and supporting information pointers
|
|
- inspect paragraph styles, table count, figure-caption patterns, references section, and obvious empty or duplicated sections
|
|
- run `scripts/docx_template_audit.py` when a quick structural report is useful
|
|
- if a `qqwrite_brief.json` is provided, read `references/brief-consumption.md`
|
|
|
|
3. Adjust only formatting and template structure unless the user explicitly asks for rewriting:
|
|
- move or relabel sections to match the template
|
|
- normalize heading levels
|
|
- normalize title, author, affiliation, abstract, keywords, captions, references, and acknowledgements placement
|
|
- preserve scientific claims, numbers, units, equations, citations, and figure/table labels
|
|
- flag unclear template conflicts in the report instead of guessing silently
|
|
|
|
4. Produce the revised Word file:
|
|
- copy the original manuscript first
|
|
- apply template-compatible styles and section order
|
|
- keep original content recoverable
|
|
- avoid converting citations to plain text unless unavoidable and reported
|
|
|
|
5. Produce the report:
|
|
- list template used
|
|
- list changed sections and formatting changes
|
|
- list unresolved issues requiring author decision
|
|
- list any content that appears missing relative to the template
|
|
|
|
## Boundaries
|
|
|
|
- QQwrite does not decide manuscript novelty, literature strength, or reviewer risk. Route those tasks to QQsci.
|
|
- QQwrite does not generate or repair `qqwrite_brief.json`; DeepSeek drafts it and QQsci checks it.
|
|
- QQwrite does not generate Zotero/DeepSeek literature notes. Route those tasks to QQnote.
|
|
- QQwrite may lightly fix obvious Word-format inconsistencies, but substantial scientific rewriting belongs in QQsci or a future writing module expansion.
|
|
- For citation suggestions inside Word, follow QQsci's DOI-only comment convention if the task explicitly involves citation comments.
|
|
|
|
## Current Capability
|
|
|
|
Only one capability is active now:
|
|
|
|
`template-adjust-docx`: adjust a manuscript `.docx` according to a `.docx` template from the local library.
|
|
|
|
Future capabilities can be added later, but keep this skill focused on Word-template execution.
|