nsfc-research-content-writer
Original:🇨🇳 Chinese
Translated
5 scripts
Write/refactor the NSFC main text section (II) Research Content, and synchronously organize the Characteristics and Innovations and Three-Year Annual Research Plan, outputting three extraTex files that can be directly applied to LaTeX templates. Suitable for scenarios where users need to write/revise research content, research objectives, key scientific issues, technical routes, innovation points, three-year plans/milestones, etc.
12installs
Added on
NPX Install
npx skill4agent add huangwb8/chineseresearchlatex nsfc-research-content-writerTags
Translated version includes tags in frontmatterSKILL.md Content (Chinese)
View Translation Comparison →NSFC (II) Research Content Organization & Writing Tool
Target Output (Contract)
- Write Destinations (3 Files):
extraTex/2.1.Research Content.texextraTex/2.2.Characteristics and Innovations.texextraTex/2.3.Annual Research Plan.tex
- Prohibited Modifications: ,
main.tex, anyextraTex/@config.texfiles.cls/.sty - Organization Principle: First write Section 2.1 as a "verifiable closed loop", then extract innovation points from Section 2.1 to generate Section 2.2, and finally split the tasks in Section 2.1 into three-year milestones to generate Section 2.3.
Parameters and Output Modes (Recommended to Provide Explicitly)
- : Root directory of the grant proposal project (e.g.,
project_root)projects/NSFC_Young - (default
output_mode):apply- : Do not write directly to files; output three draft LaTeX main text sections that can be copied and pasted, and mark the target file paths they should be written to
preview - : Only write to the three target files (see "Target Output"), do not touch other files
apply
Required Inputs (Minimum Information Form)
- If not provided by the user, collect/supplement first: references/info_form.md
Writing Security Constraints (Must Comply)
- Only edit the three files; do not modify
extraTex/2.*.tex,main.tex, or anyextraTex/@config.texfiles.cls/.sty - If the target file already contains title commands (e.g., /
\\subsection{...}), only replace the main text content, do not modify the title or structural hierarchy\\subsubsection{...} - If information is incomplete, ask for supplements first; do not force-write details that "look real"
Workflow (Execute in Order)
- Locate Project and Target Files: Confirm , read and only edit the three
project_rootfiles; if the target files do not exist, prompt the user to initialize/copy the template project first.extraTex/2.*.tex - Fix the "Sub-Goal Triplet": Split the target into 3–4 sub-goals (recommended to number them S1–S4 for subsequent traceability), and for each sub-goal, clearly write:
- Metrics (verifiable/acceptance-able)
- Comparison/Baseline (compare with whom, how to compare)
- Data Source/Verification Scheme (samples/experimental system/evaluation method)
- Generate Section 2.1 Research Content (following the main line of Problem → Objective → Content → Route → Verification):
- Research Problems and Overall Objectives (no more than 2 paragraphs)
- List of Sub-Goals (3–4 items, each with the triplet)
- Research Content and Task Decomposition (align with sub-goals, avoid "writing a bunch of methods without showing what problems they solve")
- Technical Route and Verification Criteria (comparison/ablation/external verification/leakage prevention/statistical methods)
- Extract Section 2.2 Characteristics and Innovations from Section 2.1:
- 1–3 items are sufficient; each item should be expressed using a "relative coordinate system": Compared with mainstream routes A/B, this project differs in X, is expected to bring Y, and can be verified with Z.
- Avoid absolute wording (e.g., "first time", "leading"); if it is necessary to use such wording, provide verifiable evidence or rewrite it into a reviewable relative statement.
- Derive Section 2.3 Annual Research Plan from Section 2.1 (three years, no cross-year arrangements):
- For each year: Annual Objective → Key Tasks → Milestones (verifiable) → Deliverables (papers/data/prototypes/specifications/software, etc.)
- Milestones must be linked to sub-goals (otherwise reviewers will think "the plan is disconnected from the research content")
- Consistency Check:
- Check whether the innovation points in Section 2.2 can be traced back to specific tasks and verification in Section 2.1;
- Check whether the milestones in Section 2.3 cover all sub-goals, and there are deliverables every year.
- Terminology Alignment: Try to keep the research objects/abbreviations/metric names consistent with Section (I) Project Justification and Section (III) Research Basis (if they already exist in the proposal)
Acceptance Criteria (Definition of Done)
- See: references/dod_checklist.md
Writing Cheat Sheet (Optional)
- Examples of Sub-Goal Triplet: references/subgoal_triplet_examples.md
- Examples of Innovation Point "Relative Coordinate System": references/relative_coordinate_examples.md
- Annual Plan Template (Ensure Milestones are Verifiable): references/yearly_plan_template.md
- Minimum Structure Skeleton for Three Output Files (Copy-Pasteable): references/output_skeletons.md
- Common Writing Anti-Patterns and Rewrites: references/anti_patterns.md
- Verification Criteria Menu (Comparison/Ablation/External Verification/Statistics/Leakage Prevention): references/validation_menu.md
- Terminology Alignment Table (Consistent Across Chapters): references/terminology_sheet.md
Change Log
- This tool does not maintain change history in this document; all changes are uniformly recorded in the root-level .
CHANGELOG.md