Practical guide

Manage your team’s prompts, step by step.

Setting up AI prompt management means choosing recurring tasks, naming and organizing prompts, identifying their variable information, reviewing them, sharing them and revisiting them. The goal is to build a reliable base before automating everything.

Choose recurring tasks

Start with a short inventory. Select prompts used every week, prompts that affect deliverable quality and prompts that teammates copy repeatedly.

Checklist

  • List the tasks prepared with AI every week.
  • Identify 10 to 20 priority prompts.
  • Remove obvious duplicates.

Name and organize

Give each prompt a name that describes its real use, then store it where the team will look for it: by client, by department or by type of task.

Checklist

  • Name each prompt after its real use.
  • Choose an organization: folders by client, department or task.
  • Add tags to prompts used across teams.

Identify variable information

Each prompt should include a goal, context, variable information, an output format and known limitations. This is usually enough for another teammate to understand it.

  • Goal: what the prompt should produce.
  • Variables: what changes at each use.
  • Criteria: what makes the output acceptable.

Checklist

  • Spot the passages that change at each use.
  • Turn them into fields with clear labels.
  • Move durable information into the workspace context.

Review

Before sharing a prompt widely, test it on a real case, then have it reviewed by someone who knows the topic. The reviewed version becomes the team’s reference version.

Checklist

  • Clear name and identified owner.
  • Goal, variables and output format described.
  • Input example and known limitations noted.
  • Tested on a real case, then reviewed by a lead.

Share

Publish the reviewed version in the relevant workspace. People with access find it in the library, and close to their AI tool with the browser extension.

Checklist

  • Publish the reviewed version in the right workspace.
  • Check that the right people have access.
  • Introduce the prompt to the team with an example of use.

Revisit

Quality depends on readable versions and feedback. When the same correction happens repeatedly, improve the reference prompt instead of only editing today’s output.

Checklist

  • Review important prompts monthly.
  • Add examples of successful outputs.
  • Archive prompts that are no longer used.

Frequently asked questions

How many prompts should we review first?

A small batch is enough. Build a reliable method first, then expand it to more workflows.

Should every prompt have performance metrics?

Metrics are useful for frequent prompts, but structure and a reference version come first.

Who should own team prompts?

Business owners or team leads should own prompts that directly affect production or customer-facing work.

Your turn: pick a prompt you use often.

Spot the information you change every time: those are your first variables.

Try for free

Free during beta