GovSpend Prompt Library

6
pinned tiles on the search page, dragged into order: 3
tabs in the manager: all, yours, your team's: 2
ways into the library: the platform and MCP: 1
checkbox between private and shared with the account

How it started

AI Search answers one question at a time, and the questions that work are long ones: the competitors you track, the states you sell into, the window of time that matters. People were keeping them in a notes file and pasting them back in. The Prompt Library makes that notes file part of the product. I was the lead developer on it and stayed with it from the first sketch to the October 2026 release, carrying the parts that had no owner as well as the ones that did.

The problem

A saved prompt is easy to describe and awkward to get right. It has to behave like a template, so editing it in the search box cannot touch what is stored. It has to be private by default and shared on purpose, which means an edit and delete rule that holds across a whole account. And once a team shares prompts, finding one matters more than writing it, so tags and search carry as much weight as the editor does.

The approach

Every user starts with prompts the AI wrote from their SLED and Federal Profiles, already pinned, so the page is useful before anyone types anything. From there the Prompt Manager opens on All, My Prompts or Team, each tab showing how many it holds. A prompt is a title, the text, tags and one checkbox. If you do not know how to word it, Generate takes a plain sentence and writes the prompt, filling in the competitors and agencies your Profile already lists. Six tiles on the AI Search page hold what you use most, and the same library is readable from an assistant over MCP.

One stored prompt, six paths through it

On the surface it is a list of saved text. Underneath, the same object arrives from AI generation, from the person writing it, or from a teammate sharing it, and then has to show up in the Prompts popup, on a pinned tile, and inside an assistant's MCP session. Most of the work is keeping one prompt consistent across all of those without each surface growing its own idea of what a prompt is.

Three ways a prompt gets into the library and three places the same library shows up, the platform, the pinned tiles and an assistant over MCP. Sources: the Help Center article on the Prompt Library and the October 2026 release notes.

A template, not a draft

Selecting a prompt fills the search box and nothing else. Whatever you change there belongs to that one search, and the stored version does not move. It sounds obvious until you watch someone adjust a prompt for a single question and then ask why their library changed. Editing the saved prompt happens in one place, the Prompt Manager, and only for whoever created it.

Private by default, shared on purpose

Prompts start private. One checkbox moves a prompt to the Team tab, where everyone on the account can find it and run it, and nobody but its creator can change it. On a prompt somebody else shared, the pencil and the trash icon are not there at all, so the rule shows up as an absence rather than as an error message after the click.

On screen · tap to enlarge

The AI Search page with pinned prompts: up to six tiles, dragged into the order you want, one click to load one into the search box.

The Prompt Manager: All, My Prompts and Team, each with its count, over a library you search by keyword or by tag.

Creating one: a title, the text, tags, and a single checkbox between private and shared with the whole account.

What's next

The Prompt Library went out with the October 2026 release notes, live in AI Search and in GovSpend's MCP server at the same time. The Help Center files it under The Lab, in the AI Search beta, which is where GovSpend puts what is still being shaped by the people using it.

Stack

MCP Protocol
AI Search

Public sources

All projects