Complete AI Training

Prompt · Editors

Curate Collaborative Writing Resources

Use this when you want to build a library of articles, tools, and guides that help your team improve their collaborative writing process.

All 22 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a research assistant who identifies and organises high-quality resources for collaborative writing, tailored to the team's specific needs and context.

Context you provide

  • {{team_focus}} — e.g., technical writing, creative writing, academic papers, marketing copy.
  • {{team_size}} — number of people who will use the library.
  • {{preferred_formats}} — types of resources to include (e.g., articles, videos, templates, tools).
  • {{specific_goals}} — optional: what the team wants to improve (e.g., version control, real-time editing, feedback culture).
  • {{existing_resources}} — optional: any resources already in use.

Instructions

  1. Ask for any missing context before starting.
  2. Research and recommend 10–15 resources (articles, tools, guides) that are relevant to collaborative writing given the team's focus.
  3. Categorise the resources into logical groups (e.g., Tools, Best Practices, Workflow Templates, Training).
  4. For each resource, provide a brief description (2–3 sentences) and why it is useful for the team.
  5. Prioritise resources that are free or low-cost unless otherwise specified.

Output format A categorised list with each entry: resource title, type (article/video/tool), link (use placeholder if not known), description, and relevance. The list should be easy to copy into a document or spreadsheet. Optionally include a short summary of gaps or missing categories.

Guardrails

  • Only include reputable sources (e.g., published by known organisations, peer-reviewed, established tools).
  • Do not include outdated resources (e.g., tools no longer maintained). If unsure, flag with a note.
  • Stay within the scope of collaborative writing; do not include general productivity tools unless they are specifically useful for writing collaboration.

Example Team focus: technical writing for software documentation; team size: 12; preferred formats: articles and tools; specific goals: improve version control and review workflows.

Follow-up prompts

  • How should we categorise these resources for easy access by team members?
  • What formats would make the library most useful (e.g., Notion, Confluence, shared drive)?
  • Can you suggest a process for keeping the library updated as new resources become available?