> For the complete documentation index, see [llms.txt](/llms.txt).
> Markdown versions of each page are available by appending .md to any URL.

# 5 agent workflows for product managers

Use five agent workflows to automate status updates, document drafting, Slack search, and meeting preparation for product managers.

Most PM work involves gathering information, synthesizing it, and communicating the result. These five workflows use agents in Warp and MCP servers to gather context and speed up synthesis. You’ll spend less time switching between tools and more time making decisions. Each workflow takes 5–10 minutes to set up.

## Prerequisites

-   **Warp** - Install Warp and sign in. See [Installation and setup](/getting-started/quickstart/installation-and-setup/).
-   **MCP servers** (optional but recommended) - Connect agents to tools and data sources such as Slack, Linear, and Notion. See [MCP](https://docs.warp.dev/agents/capabilities/mcp/) for setup instructions. Each workflow identifies the servers it uses and includes a fallback.

Note

These workflows work with the Warp Agent or third-party CLI agents running in Warp, including Claude Code, Codex, OpenCode, and Gemini CLI. See [Third-party CLI agents](https://docs.warp.dev/agents/cli-agents/overview/) for the full list.

## 1\. Pull cross-project status updates

Compiling a status update across multiple projects usually means opening Slack, Linear, Notion, and email in separate tabs, reading through each one, and manually synthesizing a summary. With MCP-connected agents, you can pull context from all of these tools in a single prompt.

1.  Tell the agent which projects, tools, and time range to cover. Be specific about the audience and format you need.
2.  Submit a prompt that queries your connected tools. For example:

```
Pull updates from the last week across #project-atlas and #project-beaconin Slack, any Linear tickets that moved to Done or In Review, and thelatest entries in our Notion launch tracker. Summarize into a statusupdate for my skip-level, organized by project. Use bullet points. Flaganything blocked or at risk.
```

3.  Review the output and iterate. Ask the agent to adjust the tone (more concise, more formal), reorder sections, or add context for a specific stakeholder.

You’ll have a formatted status update ready to paste into Slack or email.

This workflow uses Slack, Linear, and Notion MCP servers.

Note

**Without MCP:** Copy relevant updates from each tool and paste them into your prompt. Ask the agent to synthesize and format the summary. The workflow remains the same, but MCP automates the gathering step.

## 2\. Draft documents from the terminal

Writing a rollout doc, product brief, or strategy doc usually starts with a blank page in Google Docs or Notion. Instead, describe what you need to the agent and iterate on a draft without leaving Warp.

1.  Describe the document type, audience, and structure. For example:

```
Draft a product brief for a new onboarding flow redesign. The audienceis engineering and design leads. Include sections for problem statement,proposed solution, success metrics, and open questions. The problem isthat 40% of new users drop off before completing setup.
```

2.  Review the draft and iterate. Ask the agent to expand a section, tighten the language, add a competitor comparison, or restructure the outline.
3.  If you have the Notion MCP server connected, ask the agent to push the finished draft to Notion.

You’ll have a structured first draft, grounded in your specific context and ready for review.

Note

**Without MCP:** Copy the finished draft and paste it into your documentation tool.

## 3\. Search Slack for meeting prep

Before a meeting or project check-in, you might need to catch up on activity across multiple Slack channels. If you have the Slack MCP server connected, you can search and summarize in one prompt rather than manually reading through each channel.

1.  Tell the agent which channels and time range to search. For example:

```
Search #eng-backend, #design-reviews, #project-atlas, and#incidents for the last 3 days. Summarize the key decisions,open questions, and anything that was escalated. I have aproject sync in 30 minutes and need to be caught up.
```

2.  Review the structured summary the agent returns, grouped by topic or channel.
3.  Ask follow-up questions to drill into specific threads. For example, ask, “What was the resolution on the API rate limiting discussion in #eng-backend?”

You’ll have a briefing document that summarizes recent activity across channels.

This workflow uses the Slack MCP server.

Note

**Without MCP:** Copy key messages or thread summaries from Slack and paste them into your prompt. Ask the agent to organize and summarize them. This works well for a smaller number of channels.

## 4\. Run parallel workstreams in tabs

PM work often involves several threads at once, such as researching a competitor, drafting a brief, and reviewing a teammate’s document. Warp’s vertical tabs let you run separate agent sessions side-by-side, with each focused on a different task. To enable vertical tabs:

1.  In the Warp app, go to **Settings** > **Appearance** > **Tabs**, then toggle on **Use vertical tab layout**.
2.  Open a separate tab for each workstream, and give each tab a clear deliverable:
    -   **Competitor research (Tab 1)** - Ask the agent to compare competitor pricing, packaging, and positioning, then return a five-bullet summary with source links.
    -   **Product brief (Tab 2)** - Ask the agent to draft a product brief with a problem statement, target users, success metrics, and open questions.
    -   **Stakeholder update (Tab 3)** - Ask the agent to summarize relevant Slack threads into decisions, risks, and next steps.
3.  Use each tab’s agent status badges and activity indicators to see which workstream needs attention without repeatedly switching tabs.

When the research is ready, use its summary to refine the brief or stakeholder update. This pattern keeps workstreams isolated and lets you switch context without losing progress. For a detailed walkthrough of multi-agent tab setups, including tab configs and Git worktrees, see [Run multiple AI coding agents](/guides/agent-workflows/how-to-run-multiple-ai-coding-agents/).

## 5\. Use voice to draft strategy docs

When thinking through a brief, strategy doc, or stakeholder update, talking can be faster than typing. Warp’s voice input lets you dictate a rough draft. Then use the agent to organize and refine the transcription.

1.  Click the **microphone icon** in the input area or press the voice input key to start recording. By default, the voice input key is `fn`.
2.  Talk through your document naturally. Describe the problem, your proposed approach, open questions, and next steps. Don’t worry about structure or polish.
3.  After the transcription appears, submit this follow-up prompt:

```
Clean up that transcription into a structured strategy doc. Add anexecutive summary at the top, organize the body into Problem, Approach,Risks, and Next Steps sections, and tighten the language for aleadership audience.
```

You’ll have a structured first draft from an unstructured recording. For setup details and additional use cases, see [Use voice and images to prompt agents](/guides/agent-workflows/how-to-use-voice-and-images-to-prompt-coding-agents/).

## Productivity tips

-   **Save Rules for recurring formats** - Save a Rule with your team’s status update format, document templates, or project list so agents start with the right context. See [Rules](https://docs.warp.dev/agents/capabilities/rules/).
-   **Reuse recurring workflows** - Save your weekly status update or meeting-prep instructions as a [Saved Prompt](/guides/configuration/trigger-reusable-actions-with-saved-prompts/) that you can run again.
-   **Use `Ctrl+G` for complex prompts** - Open the rich input editor for click-to-edit prompt composition instead of navigating with arrow keys. This works with any CLI agent running in Warp. See [Rich Input Editor](https://docs.warp.dev/agents/cli-agents/rich-input/).
-   **Save Tab Configs for recurring setups** - If you regularly use a research, drafting, and review layout, save it as a Tab Config for one-click workspace setup. See [Tab Configs](https://docs.warp.dev/terminal/windows/tab-configs/).

## Next steps

You now have five workflows for common PM tasks. They cover cross-project status updates, document drafting, Slack search for meeting prep, parallel workstreams in tabs, and voice-to-text for rough drafts.

To go deeper on any of the tools used in these workflows, explore the related guides below. You can also customize how agents behave across your team with Rules, Saved Prompts, and MCP integrations.

-   [Connect agents to MCP servers](/guides/external-tools/using-mcp-servers-with-warp/) to set up Slack, Linear, Notion, and other integrations.
-   [Use voice and images to prompt agents](/guides/agent-workflows/how-to-use-voice-and-images-to-prompt-coding-agents/) for full setup and use cases for multimodal input.
-   [Run multiple AI coding agents](/guides/agent-workflows/how-to-run-multiple-ai-coding-agents/) for multi-tab workflows, tab configs, and Git worktrees.
-   [MCP](https://docs.warp.dev/agents/capabilities/mcp/) for the full configuration reference.
-   [Rules](https://docs.warp.dev/agents/capabilities/rules/) to save persistent context so agents follow your team’s conventions.
-   [Voice input](/agents/local-agents/interacting-with-agents/voice/) for the full reference to voice transcription features.