How to keep prompts for feature specs for product engineers in 2026

Product engineers can save feature-spec prompts as reusable snippets and compare tools that store them well.

By SupaKeeper · 2026-10-29

SupaKeeper is published by LunarWerx, which makes some of the tools compared here.

To keep prompts for feature specs, write each prompt once as a reusable snippet, file it where the team can find it, and check that it inserts correctly in the editor used for Copilot conversations.

Option	What it can do	What to check
Copilot AI Productivity Suite	A VS Code extension that saves prompts as snippets and inserts the saved template into a Copilot conversation with a short command. ^[1]	Check that its folders, groups and pricing match how often the team reuses prompts.
Existing Copilot workflow	Use the prompt-saving methods already available in the Copilot workflow.	Check whether the current approach keeps feature-spec prompts findable and reusable.
Separate prompt manager tool	A separate tool may provide a way to organize prompt text and share it.	Check the editor support and sharing it offers before choosing it.

What you need before you start

Before setting up prompt storage, gather the feature-spec prompts that repeat across your work. Write each one clearly, because the saved text is the version that gets reused. Keep the editor in mind, since a prompt is only useful where it can be inserted into a conversation.

Feature-spec prompts often share a structure. Placeholders for the feature name, scope, and acceptance criteria let one prompt cover many features instead of a separate prompt for each request.

Pick names that a teammate can guess. A prompt called acceptance-criteria is easier to reuse than one with an unclear label.

Decide whether prompts stay on one machine or move between machines and people. Have a small set of starter prompts ready before a feature starts, and group related prompts so a whole set can be referenced together. Check that the chosen option works in the editor used for Copilot conversations, and that it keeps prompts findable when a new feature begins.

Step by step

Collect the feature-spec prompts that need to be kept. Start with the ones used at the beginning of most feature work, such as a prompt that asks for a spec draft and a prompt that asks for acceptance criteria.

Choose where the prompts are stored. The option can be the snippet feature of the editor, a separate tool, or a shared set the team keeps updated.

Write each prompt as a reusable template with a short, clear name. The name should say what the prompt produces, so it is easy to pick later.

Add placeholders for the values that change per feature. A placeholder that asks for the feature name at insertion time means the same prompt works across many features.

Group related prompts together. Bundling the prompts for one kind of request means the whole set can be referenced at once rather than pasted one by one.

Test that inserting a prompt into a Copilot conversation gives the expected text. Adjust the wording, the placeholders, and the names until the result is what the team wants to reuse.

Review the storage when the team or the editor changes. A workflow that keeps prompts easy to reach should stay in place, and prompts that no longer fit should be updated or removed.

Keep a routine for naming and grouping prompts. Consistent labels make future searches faster and stop the team from re-typing prompts that already exist.

Tools that can do it

Copilot AI Productivity Suite is made by the team that publishes this site.

It is a VS Code extension that saves prompts as snippets, and typing #copilotsuite with a snippet id inserts the exact saved template into the conversation. ^[1] Snippets can sit in nested folders, and several can be bundled into a group that is referenced all at once. ^[1] Placeholders such as ${name} or ${name:default} ask for a value when the snippet is inserted. ^[1] You can pin up to five favorite prompts to the VS Code status bar. ^[1]

The extension is installed from the VS Code Marketplace as LunarWerx.copilot-suite. ^[1] It needs VS Code 1.116.0 or newer, and it is also on Open VSX for Cursor, Windsurf and VSCodium. ^[1] You can select several snippets and move them, delete them, or insert all their references at once. ^[1] You can create and edit Copilot toolsets, custom agents, instruction files and prompt files from the sidebar. ^[1]

For reuse outside Copilot, a bundled local MCP server lets you use snippets and groups in Claude Code, Codex CLI and other MCP clients. ^[1] If one option is turned on, each snippet is written out as a slash command file for Claude Code and Codex CLI, and the files stay in sync as you edit. ^[1] You can export snippets as JSON or make a share link, and teammates can import it. ^[1]

Signing in with an account that uses an emailed one-time code syncs snippets, groups and settings across your machines. ^[1] There is a Free plan at $0 that allows 20 Copilot insertions a week. ^[1] Premium costs $6.99 a month and has unlimited Copilot insertions. ^[1] The software uses a proprietary licence and is proprietary and confidential to LunarWerx. ^[1] While VS Code telemetry is on, it sends anonymous usage statistics, but never snippet content. ^[1]

Other approaches include using the prompt-saving methods already available in a Copilot workflow, or choosing a separate prompt manager tool after checking what it stores and how it works in the editor used. Compare each option against the exact job of keeping feature-spec prompts findable and reusable.

Common mistakes to avoid

Avoid saving prompts as plain text without placeholders. A prompt that has to be rewritten for every feature name wastes the time saved by storing it.

Avoid choosing storage without checking that it works in the editor used for Copilot conversations. A stored prompt that cannot be inserted is not useful.

Avoid unclear prompt names. A label that does not say what the prompt produces makes the stored set hard to search later.

Avoid keeping different versions of the same prompt in different places. When prompts are shared, check that everyone uses the same saved copy so inserts do not drift apart.

Avoid ignoring the cost structure of the option. Fee and per-insertion limits should be checked before the storage becomes part of daily work.

Frequently asked questions

Can Copilot AI Productivity Suite keep feature-spec prompts as snippets?

Copilot AI Productivity Suite stores prompts as snippets in VS Code, and typing #copilotsuite with a snippet id inserts the exact saved template into the conversation. ^[1] Snippets can sit in nested folders and be grouped so several are referenced at once. ^[1] Placeholders named ${name} ask for a value when the snippet is inserted. ^[1]

How much does Copilot AI Productivity Suite cost for product engineers?

Copilot AI Productivity Suite has a Free plan at $0 that allows 20 Copilot insertions a week. ^[1] Premium costs $6.99 a month and has unlimited Copilot insertions. ^[1] For regular feature-spec work, compare the weekly insertions on the free option against how many prompts are inserted each week ^[1].

Can Copilot AI Productivity Suite sync prompts across machines?

Signing in with an account that uses an emailed one-time code syncs snippets, groups and settings across machines. ^[1] The extension needs VS Code 1.116.0 or newer, and it is also on Open VSX for Cursor, Windsurf and VSCodium. ^[1] Before relying on sync, confirm each machine runs a compatible editor. ^[1]

Can feature-spec prompts be shared with teammates?

Prompts can be exported as JSON or given a share link that teammates can import. ^[1] Exporting a prompt and importing it into a teammate's own copy puts the same saved text in both places. ^[1] Check how teammates receive prompt files before choosing a sharing routine. ^[1]

Can Copilot AI Productivity Suite reuse prompts outside Copilot?

A bundled local MCP server lets you use snippets and groups in Claude Code, Codex CLI and other MCP clients. ^[1] If one option is turned on, each snippet is written out as a slash command file for Claude Code and Codex CLI, and the files stay in sync as edits are made. ^[1] This suits teams that reuse prompts in other tools. ^[1]

There is a Free plan at $0 that allows 20 Copilot insertions a week. ^[1]

Try Copilot AI Productivity Suite

Sources

Copilot AI Productivity Suite's own description of itself (the product of this site's publisher)