A spoken method for designing reusable prompt templates that survive one pass.

Building Prompt Templates You can speak is a different craft from writing templates for a page. A spoken template must survive a single pass: no nested clauses, no parentheses, no options that require scrolling back. Say it once and it should land as a complete instruction. The test is simple: read the template aloud without stopping, and see whether the structure is still clear. If you lose your place, the assistant will lose it too. Design for the mouth first, then simplify the page version to match. Say the page version aloud once and cut every phrase you would not say to a colleague.
Keep each template to one job. A template for drafting a status note should not also cover meeting summaries, and a template for rewrite requests should not include research. Every added job forces another slot, another rule, and another way to go wrong. Name the job in the first line, then list the slots and the rules. If you need a second job, make a second template. A small library of focused templates is easier to remember and faster to speak than one master prompt with seventeen options. Name the template after the task so the job is obvious before anyone opens it.
Use words that are easy to say and hard to mishear. Short common words beat long technical ones, especially for slot names. Avoid pairs that sound alike, such as then and than or accept and except, in the same template. Spell out numbers that matter, and say dates in a fixed format, such as month, day, year. If a term is necessary and awkward, practice it once before you record the template. A template that survives a noisy room is more useful than one that only works in silence. Test the template in the room where you will actually use it.
Make the opening line do the heavy lifting. Say the role and the task in one sentence: you are my editor; rewrite the message below for a frustrated client. The opening line tells the assistant what kind of response to produce before any details arrive. Keep it under twenty words and free of qualifiers. If the opening needs a second sentence to be clear, the template is probably trying to do two jobs. A strong opening line makes the rest of the template easier to speak and easier to change. Write the opening line first and keep it unchanged as the template evolves.
Break the template into named slots: reader, purpose, facts, format, tone, limits. Each slot takes one short phrase, and the order stays the same every time. Named slots make the template easy to fill and easy to audit. When something goes wrong, you can ask which slot was weak. When you share the template, the slots show a colleague what must be decided before speaking. A template without slots becomes a paragraph of instructions that nobody can update without rewriting the whole thing. The slot list also doubles as the checklist you use when you build a new template. That list is short.
Decide which slots are fixed and which change each time. The job and the format are usually fixed; the reader, the facts, and the deadline change. Mark the fixed parts as written text and the changing parts as blanks. Keep the number of changing slots small, ideally four or five. A template with ten changing slots is a form, not a prompt, and it takes longer to fill than to speak from scratch. Simplicity is what makes the template reusable under time pressure. Put the fixed text in one block and the blanks in another, so the form is obvious.
Write the rules for each slot in one line. For the facts slot, say only facts that are already confirmed. For the tone slot, say one adjective and one example sentence. For the limits slot, say the length and the banned phrases. One-line rules are easy to say and easy to check. When a rule needs an exception, write the exception as a separate rule rather than folding it into the same sentence. Clear rules prevent the template from becoming a debate with yourself in the middle of a sentence. Keep each rule on its own line in the written version, even if you speak it as a sentence.
Leave an explicit opening for the content itself. A template is the frame; the facts, the draft, or the question is the content that follows. Say a marker such as here is the material, then pause and speak the content in plain language. This separation keeps the instructions from blending into the material, which is a common failure when both are spoken in one stream. The assistant can then tell what to follow and what to work on. Say the marker twice if the material is long, so the boundary stays unmistakable in a noisy room and at speed. Say it clearly.
Say the slots in the same order every time. Order is memory: after a week, you will remember the template by its rhythm rather than its wording. Start with the job, then the reader, then the purpose, then the facts, then the format, then the limits. If you change the order, change it deliberately and update the written version. A stable order also makes the spoken template easier to shorten when you are in a hurry, because you know which slots can be dropped. Speak the order once more at the end if the template is new to you that day.
Speak the slot name, then the value, then a short pause. The pause is the punctuation of a spoken template. It gives the assistant a boundary and gives you a moment to check what you said. If you skip the name, the values run together and the assistant has to infer the structure. A named slot such as format, three bullets is clearer than a rushed list of instructions. Practice the rhythm once, and the template becomes easier to use than a written checklist. Keep the pause under a second, because it is a boundary, not a performance for the room.
Use a closing line that states what the response should contain. Say: return the draft, then three notes on what you changed. A closing line turns a prompt into a request with a defined deliverable, and it prevents a response that rambles or stops early. Keep the closing line short and specific. If the template is for a recurring task, the closing line is often the part that saves the most editing time, because it fixes the shape of the output before the assistant starts. A good closing line names the format, the count, and the order of the output.
Build a short version of the template for quick use. The full template is for important work; the short template is for the routine case. Keep the job, the reader, the format, and the main limit, and drop the examples. Say the short version in one breath. Two versions of the same template cover most situations without forcing you to choose between a long form and no structure at all. Review both versions together so they do not drift apart. Keep the short version written down too, so it does not drift from the full one over time. Compare them once a month.
Test a new template by speaking it without notes into a blank window. Do not read from the written version. If you stumble, the template has a phrase that is hard to say or an order that is hard to remember. Fix the template, not your delivery. Run the test three times on three different tasks. A template that works once may have worked because the task was easy. Three clean runs is a better sign that the structure is doing its job. If you stumble twice at the same phrase, rewrite that phrase before the next cold run and say it once.
Compare the output with what you would have written by hand. If the draft needs a structural rewrite, the template's slots are wrong or incomplete. If it needs only small edits, the template is close. Track the kind of edit you make most often, and add a rule for it. A template improves through these small additions, not through a complete redesign after every use. Keep the version that produced the fewest edits and use it as the baseline. Count the edits by type so the next change targets the most common one first. Keep the count simple and short.
Test the template under realistic conditions. Speak it in a busy room, at normal speed, with the app you actually use. A template that only works in a quiet test is not ready. Check that the text appears where you need it, that names and terms survive, and that the formatting matches the request. Voiskey removes filler words, stutters, and self-corrections and adapts punctuation and formatting, so the test shows the template rather than your delivery. If the result is messy, simplify the template before blaming the tool. Check the app's placement before the template, so a tool problem does not look like a wording problem.
Record the test result beside the template. Note the date, the task, the edits needed, and the change you made. After a few tests, the record shows which slots are stable and which need work. Share the record with anyone who will use the template, so they know what to expect. A template with a test history is easier to trust than one that looks neat but has never been spoken aloud under pressure. Date each note so you can see exactly how the template changed over a month of real use. Keep the notes in the template file. Keep them plain.
Keep the templates in one shared place with a short description of the job each one does. Name them by task, not by author: status note, rewrite request, comparison brief, lesson plan. Include the spoken version and a filled example. A colleague should be able to pick the right template in ten seconds and use it without asking. The library should be small enough to scan and current enough to trust. A folder of thirty templates nobody can name is not a library. Add a one-line note on when not to use the template, because misuse spreads quickly through a shared library.
Assign an owner and a review date to each template. The owner runs it once a quarter, checks the output, and updates the rules. Templates drift when the work changes and nobody notices. The review should take minutes, not a meeting. If a template is no longer used, retire it rather than leaving it to confuse the next person. Ownership is what keeps a shared library from becoming a shared attic. Book the review date beside the owner's name, so the check is not forgotten when the quarter turns. Keep the date visible to everyone on the team. Keep the list current.
Use shared vocabulary so the same term means the same thing in every template. The team plan offers shared vocabulary and workflows, which keeps project names, role labels, and format terms consistent across the library. When a term changes, update the templates that use it in the same pass. Ask each owner to flag new terms for the shared list. Consistency across templates is what lets a colleague switch between them without relearning the language. Update the shared term list in the same pass so labels do not drift between templates. Ask owners to check it monthly. Update it there as well.
Run a short monthly session where one person demonstrates a template and the group suggests one improvement. Keep the session to fifteen minutes and change one thing. This rhythm keeps the library alive without turning maintenance into a project. Anyone can start a library with a single template: download Voiskey, speak the template into a shared note, and test it on one real task before adding a second. The first template is the hard one; the rest are variations. Ask the person who presents to bring one real output, not a description of it or a promise to share later.
Voiskey is an AI voice typing app that works in the note or document window you already use. Press a shortcut and speak the template's job, slots, order, and closing line; the text appears at the insertion point. Filler words and self-corrections are removed, so a spoken draft of the template is clean enough to test and share.
Voiskey learns names, jargon, acronyms, and spelling preferences. Say slot names such as reader, purpose, facts, and limits once, and it keeps your spelling across template drafts and filled examples. Consistent slot names make templates easier to compare, and they help a colleague recognize the same structure in a different task.
Yes. You can speak the fixed parts and pause at the slots, and Voiskey places the text at the insertion point in the window you use. It removes stutters, false starts, and self-corrections, and adapts punctuation and formatting, so the result reads as a template with clear blanks rather than a transcript.
Voiskey's team plan offers shared vocabulary and workflows, which helps a group keep template names, slot labels, and terms consistent. You can speak a template into a shared note and let colleagues run it on real tasks. Each owner should test and review the template regularly so the shared set stays current.

Download Voiskey for Mac and Windows and build your first spoken template.
Use it across macOS, Windows, iOS, and Android