Agent workflow library

A workflow is a step-by-step runbook for one product task. An agent follows it with Deck MCP tools. Humans can read it to see what the agent does and what it changes.

Every workflow is MCP-first. Each page starts with a "Probe Deck MCP" step that calls get_user_context. If Deck MCP is not installed, the agent follows the AI PM protocol and then comes back to the workflow.

To pick a workflow, find the group that matches the task. Then open the workflow with the closest goal. Each page is also served as Markdown: add .md to the page URL, or use the markdown link next to each workflow.

For setup protocols, see the agent prompt library.

How to choose

If you are not sure where to start, use Workspace audit. It shows what Deck knows today: sources, integrations, credits and gaps. Then pick the workflow that fills the largest gap.

Let the agent pick a workflow

An agent with Deck MCP can call get_workflow_ideas to pick a workflow. The agent sends the goal or the problem in the words of the user. It can also send the role of the user and other facts from memory and the conversation, for example the tools that the team uses. Deck reads the workspace state and returns the workflows that fit best. For each workflow, the result gives why it fits, what stops it now, the first tool call and the Markdown URL of the page. The agent tells the user about the options and asks which one to start. Then it fetches that Markdown page and follows its steps.

Set up

Connect sources, import feedback and roadmap items, and make sure that Deck has enough data.

• Workspace audit — also as markdown. Use this first. It audits what Deck knows: sources, integrations, credits and gaps.
• Connect the feedback stack — also as markdown. Use this to connect the team's feedback tools as native integrations.
• Migrate surveys — also as markdown. Use this to move survey exports into Deck as CSV uploads.
• Import interviews — also as markdown. Use this to bring interview transcripts into Deck.
• Import the Linear roadmap — also as markdown. Use this to import Linear initiatives and projects.
• Import Jira epics — also as markdown. Use this to import Jira epics as Projects.
• Roadmap evidence check — also as markdown. Use this to find roadmap items with little customer evidence.
• Cross-tool signal sweep — also as markdown. Use this to compare other connected tools with Deck and find the signal that Deck does not have.
• Install a feedback widget — also as markdown. Use this to create a feedback widget and install it in the product.
• Credits readiness check — also as markdown. Use this before a big import or research run. It checks the plan and the credits.

Taxonomy

Organize themes, subthemes and segments so that the signal is easy to read.

• Design the theme taxonomy — also as markdown. Use this to design the theme taxonomy from feedback and product context, then apply it.
• Taxonomy review — also as markdown. Use this to find duplicate, vague and oversized themes, then fix them.
• Sort uncategorized insights — also as markdown. Use this to place insights that no subtheme holds yet.
• Define segments — also as markdown. Use this to create customer segments and their rules.

Decide

Read the signal and pick what to build next.

• Weekly signal brief — also as markdown. Use this to write a weekly brief of new and growing signal.
• Prioritize the backlog — also as markdown. Use this to pick the top opportunities and give the reasons.
• Segment comparison — also as markdown. Use this to compare what two customer segments ask for.
• NPS breakdown — also as markdown. Use this to explain the NPS score and what drives detractors.
• Competitor gaps — also as markdown. Use this to find competitor gaps that customers also ask about.
• Competitor finding to backlog — also as markdown. Use this to turn a competitor finding into a backlog opportunity.

Act

Turn a decision into work, ship it and close the loop with customers.

• Opportunity to delivery — also as markdown. Use this to turn an opportunity into a Project and link it to Linear or Jira.
• Plan an initiative — also as markdown. Use this to group opportunities into an initiative with a goal.
• Build from evidence — also as markdown. Use this to implement a Project in the codebase from its evidence.
• Release impact check — also as markdown. Use this to compare theme signal before and after a release.
• Customer follow-up — also as markdown. Use this to tell the customers who asked for a fix that it shipped.