SuperAPI AI Directory
Partner with us中文AI newsFavorites
Skillsfund-technical-route-writer

fund-technical-route-writer

Writing & research

View repository

Updated 10-15 22:15

About this skill

NSFC "Research Methods—Technical Route—Innovation and Features" Writing Skill

Core Positioning

This skilldoes notcreate a new research plan, but rather, on the basis of the user's existing research concept, providesacademic expression, logical optimization, and standardized presentation。

Skill Scope

This skill is only responsible for the research methods, technical route, and innovation and features sections of an NSFC proposal.

Core Principles

  1. Do not create a research plan: provide academic expression on the basis of the user's existing research concept
  2. Logic first: prioritize ensuring the rigor of the research logic, rather than pursuing complex expression or ornate wording
  3. Closed-loop design: research content→key scientific questions→research methods→technical route→innovation and features must form a complete closed loop
  4. User first: prioritize retaining the materials, methods, and framework provided by the user
  5. No transfer: do not transfer the specific research content, research objects, data sources, and conclusions of historical proposals to a new project

Knowledge Base References

This skill relies on the following knowledge base files and must strictly follow them when writing:

Research Methods

  • knowledge_base/methodology_style_guide.md: Research methods writing style guide
  • knowledge_base/methodology_patterns.md: Research methods organizational logic paradigm

Technical Route

  • knowledge_base/technical_route_style_guide.md: Technical route writing style guide
  • knowledge_base/technical_route_patterns.md: Technical route organizational logic paradigm

Innovation and Features

  • knowledge_base/innovation_style_guide.md: Innovation and features writing style guide
  • knowledge_base/innovation_patterns.md: Innovation and features distillation logic paradigm

Reference Files

  • references/info_form.md: User input information form
  • references/output_skeletons.md: Output skeleton template
  • references/validation_menu.md: Validation checklist
  • references/anti_patterns.md: Anti-pattern list
  • references/terminology_sheet.md: Glossary

Workflow

Step 1: Read user input

Read the research objectives, research content, key scientific questions, and all additional materials provided by the user.

Required: research objectives, research content, key scientific questions Optional: specified research methods, existing drafts, reference code, algorithm frameworks, method design documents, flowchart drafts, etc.

Step 2: Analyze the research logic

Analyze the logical chain of research objectives→research content→key scientific questions, and identify:

  • The logical relationships among the research content (progressive/parallel/supporting)
  • Project type (data-driven/optimization decision-making/method research/empirical research/mechanism research)
  • What types of methods are needed

Step 3: Design or optimize the research methods

According to methodology_style_guide.md and methodology_patterns.md：

Case 1: the user provides only the research objectives, research content, and key scientific questions → design the research methods yourself, selecting the method combination according to the method selection decision tree and project type

Case 2: The user has already provided research methods → Prioritize understanding and inheriting the user's method design, and check whether the mapping between the methods and the research content is complete

Scenario 3: The user has already provided part of the research methods and part of the technical route → Focus on optimizing their logical connections, and prioritize retaining the user's existing design

Output: Research methods section (including method list, purpose description, and mapping to research content)

Step 4: Construct the technical route

Based on technical_route_style_guide.md and technical_route_patterns.md：

  1. Determine the level of expansion(default fine-grained):
    • Fine-grained (default): expand by sub-study → sub-sub-study, aligned with the three-level structure of the research content
    • Coarse-grained: used only when explicitly specified by the user
  2. Design the overall technical route (1 paragraph of overall research approach + 1 overall roadmap)
  3. Design the technical route for each content section:
    • Fine-grained: for each sub-study, write an introductory paragraph + roadmap + independent paragraphs for sub-sub-studies (6-step semantic order)
    • Coarse-grained: for each sub-study, write 1 combined plan paragraph + 1 figure
  4. Ensure methods are embedded in the route and form a closed loop

Output: Technical route text description + technical roadmap design plan

Step 5: Design the technical roadmap

Provide Mermaid code or design suggestions for the technical roadmap:

  • Overall roadmap: reflect the global logic
  • Content-specific roadmaps: reflect specific operations
  • Annotate research methods
  • Reflect closed-loop design

Step 6: Extract innovations and features

Based on innovation_style_guide.md and innovation_patterns.md：

  1. Identify breakthrough points from the research content
  2. Identify corresponding innovations from the key scientific questions
  3. Identify methodological innovations from the research methods
  4. Organize innovation points by innovation type (method/perspective/theory/application/framework/integration)
  5. Ensure the innovation points echo the research content and key scientific questions

Output: Innovations and features section

Step 7: Closed-loop verification

Based on validation_menu.md and anti_patterns.md：

  1. Check the closed loop of research content → research methods → technical route → innovation features
  2. Check the consistency between methods and content
  3. Check the consistency between the technical route and the main text
  4. Check the consistency between innovation points and content
  5. Check anti-patterns
  6. Check format specifications

Adaptation mechanism

The user provides only basic information

Design the research methods and technical route independently, and organize them according to the paradigms in the knowledge base.

The user has already provided research methods

Prioritize understanding and inheriting the user's method design. If there are omissions, supplement suggestions rather than replace them.

The user has already provided some materials

Focus on optimizing logical connections rather than overturning and rebuilding. Prioritize the methods and frameworks specified by the user.

Output format

The output includes the following parts:

  1. Research methods: the methods section written in the style of the knowledge base
  2. Technical route text description: overall approach + detailed plan for each content section
  3. Technical roadmap design plan: Mermaid code or design suggestions
  4. Innovations and features: the innovations and features section written in the style of the knowledge base

Language constraints

  • The output language is consistent with the user's input language
  • Use academic expression, avoid colloquialism
  • Prioritize logical rigor rather than pursuing complex expression
  • Use Chinese-English bilingual method names (when first appearing)