Team Prompt Library Board for Beginners: Save What Worked, by Use Case

Team & People

Team Prompt Library Board for Beginners: Save What Worked, by Use Case

Teams where only the AI-savvy build know-how use this beginner prompt board to save prompts that worked, sorted by use case, so anyone gets the same quality. The whiteboard holds a library table with each prompt's name, use case, cautions, and author (board 1), full-text examples of the 3 top prompts (board 2 to 4), 3 conditions for a good prompt, a 4-row registration rule table, and a frame for the update owner and review cadence. The task board has four columns - collecting, rewriting, in review, and published - with 4 parent tasks and 12 subtasks, from narrowing use cases to full-text collection, team testing, and upkeep. Start by narrowing your team's frequent use cases to 3 and keeping full text, not a summary, since a short note drops conditions and results vary when copied. Unlike the personal AI prompt board, this one is about team-wide sharing and standardizing, down to registration rules and an update owner.

0 Likes 0 Copies Author: WeProcess
prompts using AI well knowledge sharing team for beginners
Sign up free and use this template

Once you have a free account, you can copy this template from the marketplace

Whiteboard preview

Preview mode Team Prompt Library Board for Beginners: Save What Worked, by Use Case

Whiteboard preview

1. Prompt Library (keep it short; ful... 2. Full Meeting Notes Summary Prompt 3. Full External Email Draft Prompt 4. Full Document Outline Prompt 5. Is It Ready to Use as Is? 6. Is the Output Shape Fixed? 7. Are the Risks Written Down? 8. Registration Rules (rewrite in you... 9. Update Owner & Review Cadence Team Prompt Libra... How to use: (1) L... Ready-to-use prompt Registration rule... Risks & cautions Insights & im... Prompt name When to use Cautions Author Prompt 1 Meeting ... 3-line meeting notes summarye.g. sort meeting notes into decisions, action items, and other right after a regular meetinge.g. shorten a 60-minute meeting's notes before sharing names, dates, and numbersmust always be checked against the original notes Author: SatoRegistered: 2026-09-01 Prompt 2 Email external email drafte.g. turn bullet-point details into the first draft of a message before writing to someone for the first timee.g. scheduling a meeting or requesting a quote company names, amounts, and datesmust be fixed yourself, never sent as is Author: TanakaRegistered: 2026-09-03 Prompt 3 Outline document outline drafte.g. give the theme and audience, get 5 heading ideas at the start of drafting a proposale.g. when you just want the skeleton in 30 minutes headings you get back are draftscheck the facts yourself Author: SuzukiRegistered: 2026-09-05 Prompt 4 (blank) Prompt name: ____ When to use: ____ Cautions: ____ Author: ____Registered: ____ Prompt 5 (blank) Prompt name: ____ When to use: ____ Cautions: ____ Author: ____Registered: ____ e.g. You are in charge of summarizing meeting notes. Sort the notes below into decisions, action items, and other. Keep each line under 30 characters. Use names and department names exactly as written. If something is unclear, write 'needs confirmation' instead of guessing. e.g. Draft an email to a client to arrange a meeting date. Conditions: first contact, 3 candidate dates, and body under 200 characters. Include a subject line. Leave the company and contact names as ____. Do not include price or delivery date; I will add those later. e.g. Give me 5 heading ideas for a proposal. The audience is a director I am meeting for the first time. Keep it to one message. Add one line under each heading describing its content. Avoid jargon we don't already use internally. It works just by copying and pasting the full text e.g. a one-line prompt like 'summarize this' is not registered as a prompt Mark the parts that change each time with ____ so it's clear what to edit Even a first-time reader won't get lost in the steps The prompt specifies line count, items, and character limits e.g. 'within 3 lines' or '3 headings: decisions, action items, other' Aim for the same output shape no matter who uses it If the shape keeps changing, add conditions before registering it The cautions list parts that must never be sent as is e.g. always check company names, amounts, dates, and personal names yourself It states not to paste information that can't leave the company Put error-prone points where they're read before the prompt is used Rule Why 1 Naming Name it as "use case + output shape".e.g. 3-line meeting notes summary / external email draft So it can be found by name alone."Prompt A" or "Sato's notes" says nothing about the content. 2 Keep full text Instead of a short description, put the full,copyable text on a sticky note (board 2 to 4). To remove the effort of copying it outand the risk of dropping a condition. 3 Test first Test it yourself twice, and only registerprompts that return the same shape. A prompt that doesn't work erodes trustin the whole library. 4 Merge duplicates If two similar prompts appear, merge them intothe better one and delete the other. Similar prompts side by side cause confusionover which to use, and results vary. Update ownere.g. This month's owner: ____ (rotates on the 1st each month)This person decides what gets registered and merges similar prompts. Review cadencee.g. 15 minutes on the first business day of each month, with everyone.Prompts unused for 3 months are removed from the published column. How the library growse.g. Paste a prompt that worked into chat right away,and the owner registers it in a monthly batch. Don't keep it to yourself.
100%

Drag to move, scroll to zoom

Task board contents

Collecting 16 items

Narrow use cases
Collect prompt text
Test with the team
Keep it running
List frequent asks
Narrow to top 3
Write expected form
Paste what worked
Blank out variables
Add cautions
Have someone try it
Standardize output
Drop weak prompts
Set library rules
Assign update owner
Monthly review slot

Rewriting 0 items

In review 0 items

Published 0 items

← Back to templates