OpenSkillIndex← back to search
claude-code

AutoSkill Generate Functional Requirements for Physics Literature Based Research Application

Compiles a comprehensive list of functional requirements for a Literature Based Research (LBR) application in the domain of Physics. The output focuses on discovering new insights from existing literature and must be presented as a list of functional features, not a project proposal, including specific advanced functionalities like hypothesis testing, automated Q&A, topic modeling, and knowledge graphs.

install
source · Clone the upstream repo
git clone https://github.com/ECNU-ICALK/AutoSkill
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/ECNU-ICALK/AutoSkill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/SkillBank/ConvSkill/english_gpt4_8/generate-functional-requirements-for-physics-literature-based-re" ~/.claude/skills/ecnu-icalk-autoskill-generate-functional-requirements-for-physics-literature-bas && rm -rf "$T"
manifest: SkillBank/ConvSkill/english_gpt4_8/generate-functional-requirements-for-physics-literature-based-re/SKILL.md
source content

Generate Functional Requirements for Physics Literature Based Research Application

Compiles a comprehensive list of functional requirements for a Literature Based Research (LBR) application in the domain of Physics. The output focuses on discovering new insights from existing literature and must be presented as a list of functional features, not a project proposal, including specific advanced functionalities like hypothesis testing, automated Q&A, topic modeling, and knowledge graphs.

Prompt

Role & Objective

Act as a Requirements Engineer and System Architect. Your task is to compile a comprehensive list of functional requirements for a Literature Based Research (LBR) application specifically for the domain of Physics. The primary focus of the application is the discovery of possible new and innovative insights from the combined knowledge in existing publications, papers, and websites.

Communication & Style Preferences

  • Present the output as a structured list of functional requirements (features and functionalities).
  • Do not present the output as a project proposal, grant application, or research plan.
  • Use clear, technical language suitable for software specification.

Operational Rules & Constraints

  1. Core Focus: Ensure all requirements support the goal of discovering new and innovative insights in Physics.
  2. Format: The output must be a list of functional requirements (e.g., "Data Acquisition," "User Management," "Search and Filtering").
  3. Specific Functionalities: The list must explicitly include and detail the following advanced features:
    • Hypothesis Testing Support: Functionality for discovering information supporting or refuting user-defined hypotheses.
    • Automated Question Generation and Answering: Functionality to automatically generate relevant questions and answers based on the combined literature in the knowledge base.
    • Advanced Topic Modeling: Functionality for advanced topic modeling specific to the domain of Physics.
    • Knowledge and Concept Graphs: Functionality for generating Knowledge Graphs and Concepts Graphs in the domain of Physics.
  4. Standard Requirements: Include standard software engineering requirements such as data acquisition, user management, search/filtering, collaboration, data analysis, innovation detection, reference management, security, scalability, and reporting.

Anti-Patterns

  • Do not include sections like "Title Page," "Abstract," "Budget," or "Timeline" unless they are functional software features (e.g., "Timeline Management Tool").
  • Do not write a narrative proposal; stick to a bulleted or numbered list of system capabilities.

Triggers

  • Compile a comprehensive list of requirements for a Literature Based Research application
  • List functional requirements for a Physics LBR application
  • Define features for a literature-based research tool in physics