Skip to main content

Command Palette

Search for a command to run...

Cursor for Product Managers

PMs use Cursor to prototype features, validate concepts with working code, and ship small changes directly. When you can build a working version of what you are describing, conversations with stakeholders and engineers become more concrete.

Beyond prototyping, Cursor lets you answer technical questions by querying the codebase directly, generate specs grounded in what is possible, automate recurring tasks like keeping FAQ docs up to date, and connect to the tools you already use (Jira, Notion, Figma) so everything flows into one workspace.

Building prototypes

Describe what you want to build. The agent builds it, you see it in the integrated browser, and you refine with follow-up prompts. Each iteration takes seconds.

Agent example: Prototype a settings page
Create a settings page for notification preferences. Users should be able to toggle email, push, and in-app notifications separately for different event types.
Agent example: Prototype an onboarding flow
Build a prototype of a new onboarding flow with three steps: account setup, team invitation, and first project creation. Make it interactive and use our existing component library.

This works well for features that have been discussed but never prioritized, concepts you want to test with users before committing resources, and demos for stakeholder buy-in. A working prototype clarifies requirements in ways that specs and mocks cannot.

Plan Mode helps structure the path from idea to working code. Press Cmd+Shift+P (or Ctrl+Shift+P) to start planning, or Cursor will suggest it automatically for complex tasks.

A workflow that works well:

  1. Start in Plan Mode with your requirements
  2. Answer clarifying questions as Cursor researches your codebase
  3. Review and edit the structured plan
  4. Build from the plan, iterating as you see results
  5. Hand off the plan plus prototype to engineering
Plan mode example: Plan and prototype
I want to add a notification preferences page where users can toggle email, push, and in-app notifications for different event types. Plan the implementation, then build a prototype.

When you start a plan, Cursor researches your codebase to find relevant files, reviews existing patterns, and asks clarifying questions. The output is a markdown file with file paths, code references, and a structured list of tasks. You can edit the plan directly, save it to your repository, or build from it immediately.

Plans surface technical considerations early and make scope conversations concrete. The prototype shows exactly what you mean. Together, they give engineers a clear starting point.

For more on Plan Mode, see the Plan Mode documentation or the introductory blog post.

Answering technical questions

You can query the codebase directly and get answers grounded in actual code.

Ask mode example: Understand a feature
How does user authentication work? Walk me through the flow from login to session creation.
Ask mode example: Trace a user flow
What happens when a user hits the usage limit? What do they see and what gets logged?

Use Ask mode when exploring. It prevents changes while you learn. Press Shift+Tab and select Ask.

The codebase is the source of truth for how things actually work. See Understanding Unfamiliar Code for more exploration techniques.

Data analysis and reporting

PMs often need quick answers from data: usage patterns, conversion metrics, customer segments. Describe what you want to see.

Agent example: Query usage data
Query our analytics database to show me the top 10 features by usage this month, broken down by user plan type.
Agent example: Build a report
Build a simple report showing weekly active users over the last quarter. Include a chart.

Cursor can connect to databases, write queries, and generate visualizations. For PMs comfortable with data but not SQL syntax, this removes friction from self-service analytics.

Connecting your existing tools

Plugins and MCP integrations connect Cursor to tools you already use. Requirements from Jira, context from Confluence, designs from Figma; all flow into the same workspace.

Agent example: Build from Jira ticket
Pull in the requirements from jira.company.com/browse/P... and build a prototype that addresses the acceptance criteria.
Agent example: Build from Figma
Reference figma.com/file/xyz789/set... and generate a React component that matches the design.

Browse the Marketplace for available integrations: Linear, Jira, Notion, Confluence, Figma, Slack, and more.

Automating recurring work

Automations run cloud agents on a schedule or in response to events. PMs can use them to keep documentation current, triage incoming requests, and maintain consistency across repositories.

A common example: set up an automation that runs on a schedule to review your FAQ docs against the latest codebase changes and open a PR when answers need updating.

Other use cases for PMs:

  • Triage Slack bugs. An automation listens for bug reports in a Slack channel, investigates the codebase, and files an issue or opens a fix. Start from the Fix Slack Bugs template.
  • Clean up feature flags. Schedule an automation to find and remove stale feature flags after a rollout. Start from the Clean Up Feature Flags template.
  • Review PRs for security. Trigger an automation on every pull request to scan for vulnerabilities. Start from the Find Vulnerabilities template.

Create a new automation at cursor.com/automations, or browse templates in the Marketplace.

Getting started

You do not need a local development environment to start. Cloud Agents connect to your repositories and run in the background. Combined with the Slack integration, you can ask questions and kick off tasks from Slack without opening the editor.

For PMs who want to go deeper, the full Cursor app provides more control: the integrated browser for seeing changes in real-time, direct file editing, and richer context from having the codebase open.

  1. Start with Cloud Agents. Ask questions about your codebase from Slack. No setup required, connect your repositories and go.

  2. Build a prototype. Pick an idea sitting in your backlog and build a working version. Start small.

  3. Use Plan Mode for specs. Press Shift+Tab to start planning. Let Cursor research your codebase and generate a structured plan.

  4. Use Ask mode to explore. Understand how features work before writing specs. See Understanding Unfamiliar Code for techniques.

  5. Connect your tools. Browse the Marketplace to connect Jira, Notion, Figma, and other tools.

  6. Set up an automation. Pick a recurring task, like keeping FAQ docs current, and create an automation to handle it on a schedule.