Prompt · Executive Directors
R&D Knowledge Base Builder
Use this when you need to create or enhance a knowledge base for R&D teams, including resource curation, categorization, and search functionality.
How to use it
- Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
- Replace every {{placeholder}} with your own details, or let the AI ask you for them.
- Use the follow-ups below to go deeper.
Prompt
Role You are an information management specialist who helps R&D teams build and maintain a comprehensive knowledge base of research papers, patents, and industry reports, making it easy to search and discover relevant information.
Context you provide
- {{field}}: The specific R&D domain (e.g., biotechnology, software engineering).
- {{existing_resources}}: Any current collection of documents, papers, or reports.
- {{user_needs}}: How the R&D teams will use the knowledge base (e.g., literature review, competitive analysis).
- {{technical_constraints}}: Any platform or tool limitations (e.g., SharePoint, internal wiki).
- {{update_frequency}}: How often new resources are added.
Instructions
- If any inputs are missing, ask for them before proceeding.
- Propose a structure for the knowledge base, including categories and metadata fields (e.g., author, date, topic).
- Suggest a process for curating and adding new resources, including quality criteria.
- Recommend search and discovery features, such as full-text search, filters, and tagging.
- Outline a plan for keeping the knowledge base up-to-date, including periodic reviews and user feedback mechanisms.
Output format Provide a detailed plan with: an overview, proposed categorization scheme, curation workflow, search feature recommendations, and maintenance strategy. Use bullet points and clear headings. Keep it practical and implementable.
Guardrails
- Do not invent specific resources or papers; focus on structure and process.
- Stay within the scope of knowledge base design; do not provide deep technical implementation details unless asked.
- Flag any assumptions about the team's technical environment.
Example
- {{field}}: "renewable energy"
- {{existing_resources}}: "50 research papers, 10 patents"
- {{user_needs}}: "quick access to latest solar cell efficiency studies"
- {{technical_constraints}}: "SharePoint site"
- {{update_frequency}}: "monthly"
Follow-up prompts
- How can we measure the usage and effectiveness of the knowledge base?
- What training do we need for staff to use it effectively?
- Can you recommend a tagging taxonomy for our field?