An autonomous Synthetic Product Brain Trust that lives inside your IDE (Cursor/Claude).
The Last PM is not a generic "PRD generator." It is a deterministic, anti-hallucination Operating System that commands 62+ specialized AI agents across two strategic altitudes—from McKinsey-level venture strategy down to initiative-level product craft. Gain the leverage to escape the feature factory, elevate your product sense, and focus on building the right thing with exceptional taste.
For the last decade, Product Management lost its way. PMs were meant to be product builders, deeply connected to user pain and product craft. Instead, the industry turned them into backlog administrators, alignment-bureaucrats, and meeting-facilitators.
The Last PM outsources the bureaucracy to the OS.
| The Feature Factory PM | The High-Craft Builder (Using Last PM) |
|---|---|
| Spends days wordsmithing alignment docs. | Synthesizes complex strategy into sharp, Amazon-style 6-pagers in seconds. |
| Ships features to appease stakeholders. | Uses the OS to mathematically stress-test roadmaps against actual business leverage. |
| Drowns in unstructured customer feedback. | Auto-extracts core user friction and monetization opportunities from raw transcripts. |
| Manages the Jira board. | Lives in the trenches, iterating prototypes, and obsessing over product quality. |
Great product leaders don't start from a blank page. They rely on mental models.
You simply talk to The Last PM right inside your IDE. You state your strategic blocker, and the Orchestrator diagnoses the problem and silently summons the perfect mental model in the background. It commands a directory of 62+ expert agents operating at two altitudes, modeled after the methodologies of the industry's top product titans:
Built for McKinsey / Bain / Deloitte-level bets. These agents fire when you are making company-wide strategic decisions, not feature-level ones.
- Capabilities: Executive strategy synthesis, TAM/SAM/SOM market sizing, competitive landscape analysis, financial modeling, enterprise risk & scenario planning, GTM playbooks, and industry trend intelligence.
The full product craft toolkit.
- Strategic Leverage: The system runs the LNO framework (Leverage, Neutral, Overhead) to ruthlessly cut the roadmap down to what actually moves the needle.
- Continuous Discovery: Feed the OS raw user interviews, and it maps the precise psychological friction preventing users from activating.
- Monetization & Packaging: Design your pricing model and SaaS tiers before engineering writes a single line of code.
- Positioning: Reframes your narrative so your unique value proposition becomes undeniably obvious.
- Launch Pre-Mortems: Hunts down fatal execution risks (the Tigers and Elephants) before they break your launch.
You supply the product sense. The OS provides the leverage.
- "AI hallucinates and lies to me." Generic chatbots lie. The Last PM does not use open-ended chat. It is a deterministic state machine. It uses strict KERNEL frameworks to map your data against mathematical scoring matrices. It doesn't guess; it calculates based on your hard inputs.
- "I need to run an AI 1,000 times to get anything good." That is because you are starting from a blank prompt. The Last PM uses 62+ highly constrained playbooks. You aren't teaching the AI how to think; the OS is forcing you to run your ideas through the same mental models used by Amazon and Stripe.
- "I won't let an AI write my strategy." Neither would we. The Last PM is designed with Mandatory Human Checkpoints. If you pitch an idea with a fatal flaw (e.g., terrible monetization), the OS hits the brakes. It flags the risk and forces you to pivot the strategy first. It is an exoskeleton for your product sense, not a replacement for your brain.
The Last PM is not a traditional software app you install. It is a strictly structured file system and a set of architectural prompts that live directly where you work.
Prerequisites: You need either Cursor IDE (Highly Recommended for autonomous file writing) or Claude (via Claude Projects).
Cursor allows The Last PM to physically read your context, fetch agents, navigate folders, and write Markdown files directly to your local drive.
- Get the OS: Clone this repository or download it as a ZIP file.
- Open your Vault: Open the downloaded repository folder directly in Cursor.
- Set the Rules: Copy the contents of
LastPM.mdand paste them into your.cursorrulesfile. This makes the OS always active in the background. - Initiate the Orchestrator: Open the Cursor Chat (Cmd + L), explicitly tag the Orchestrator, and state your problem.
- Example:
@LastPM.md I just dropped 3 user interviews into the Backlog folder. Tell me what the biggest friction point is.
- Example:
If you don't use an IDE, you can run the OS using Claude's "Projects" feature, which acts as the system's memory.
- Create the Environment: Open Claude and create a new Project (e.g., "Product Vault").
- Upload the Brain: Upload the files from
00_OS_System_Files, the01_Global_Context/folder, and the entire/03_Agents/folder into the Project Knowledge base. - Set the Identity: Open
LastPM.md, copy all the text, and paste it into the "Custom Instructions" box for your Claude Project. - Start Building: Open a new chat inside the project and talk to your Synthetic Brain Trust. (Note: Claude Web cannot write local files, so it will output Markdown for you to copy/paste).
You do not need to burn expensive premium tokens to run this OS.
Because The Last PM relies on a highly constrained, step-by-step architectural algorithm rather than open-ended reasoning, it is exceptionally token-efficient. The system runs flawlessly on lightning-fast, lightweight models like Anthropic's Claude 3.5 Sonnet or Claude 3.5 Haiku.
The Benefit: You get near-instant agent execution, zero hallucination loops, and you save your premium IDE requests for complex coding tasks. The architecture does the heavy lifting, not the model.
The OS is designed to separate logic, static business context, and isolated project workspaces to prevent "Context Pollution."
📦 The-Last-PM
┣ 📜 LastPM.md # The Orchestrator (Paste into .cursorrules)
┣ 📂 00_OS_System_Files # The Operating System Core
┃ ┣ 📜 agent_registry.md # Directory of all 62+ specialized agents
┃ ┣ 📜 intent_dictionary.md # Deterministic Semantic Routing Map
┃ ┣ 📜 scoring_matrix.md # The 0-10 Evaluation Rubric
┃ ┗ 📜 DECISION_template.md # Template for Product Decision Records (PDRs)
┣ 📂 01_Global_Context # The Static Brain
┃ ┣ 📂 01_Company_Context # company.md (Business model, burn rate, constraints)
┃ ┣ 📂 02_Product_Context # product.md (Current capabilities, OKRs, value props)
┃ ┗ 📂 03_Venture_Strategy # 🏛️ Altitude 1: Company-level strategic artifacts
┣ 📂 02_Product_Workspace # The Localized Workspace
┃ ┗ 📂 [Your_Product_Name] # (e.g., DVA_Platform)
┃ ┣ 📂 00_Intake_and_Backlog # 📥 THE DROP ZONE: Raw transcripts, Zendesk tickets
┃ ┣ 📂 01_Global_Domains # Global Strategy & Docs
┃ ┗ 📂 02_Initiatives # 🚀 THE BUILD ZONE: Feature-specific folders
┗ 📂 03_Agents # The Council of Titans
┣ 📂 Altitude 1 — Venture Strategy # 12 McKinsey/Bain/Deloitte-level agents
┗ 📂 Altitude 2 — Initiative Craft # 50 initiative-level product agents
The Orchestrator operates as a strict, deterministic state machine. It actively manages the lifecycle of your ideas, promoting them from raw feedback to validated initiatives:
- The Intake (Drop Zone): You drop a raw transcript, feature request, or angry support email into the 00_Intake_and_Backlog folder.
- The Triage: You ask the OS to evaluate it. The OS selects a Discovery agent (like the Opportunity Score Calculator) to quantify the actual user pain.
- The Gatekeeper (Scoring): If the pain is real, you pitch building a feature. The OS reads the scoring_matrix.md and mathematically scores your pitch from 0-10 on Delight, Defensibility, Distribution, Monetization, and Feasibility.
- The Intervention: If your idea has a fatal flaw (e.g., 4/10 Monetization), the OS blocks you from writing a PRD. It automatically routes you to a strategy framework (like the Tiering Strategy Architect) to fix the flaw.
- The Checkpoint: After you provide inputs, the OS presents a brief, bulleted summary of its assumptions. You stay in control and must approve the direction before it writes any documents.
- The Promotion (Auto-Folder Creation): Once approved, the OS physically generates the Markdown document. If it's a new feature, it automatically creates a new 02_Initiatives/[Feature_Name] folder and moves the idea out of the Backlog into the Build Zone.
- The Memory: It prompts you to log a Product Decision Record (PDR) directly into that initiative's folder so the Vault never loses the "why" behind your pivot.
The OS is only as smart as the context you give it. To stop the AI from giving you generic, boilerplate advice, you must wire it into your specific product reality.
🧠 The Static Brain (Initialize your Vault)
Before you run your first agent, you need to define your playing field.
- Navigate to
01_Global_Context/. - Open and fill out the core templates:
company.mdandproduct.md. - Why this matters: Every time The Last PM runs a framework, it silently reads these files first. This ensures the pricing agent knows you are a B2B Enterprise SaaS (not a consumer app), and the strategy agent knows your current OKRs.
⚡ The Live Brain (MCP Integrations)
To unlock the absolute highest tier of autonomous product management, you need to connect the OS to your live tools using MCP (Model Context Protocol).
Because you are running this in Cursor, you can natively attach MCP servers to let The Last PM pull live data directly into the frameworks:
- Jira / Linear MCP: Connect your issue tracker. When you ask the OS to run a prioritization framework (like LNO or RICE), it can dynamically pull your current backlog, read the tickets, and re-rank them based on your current strategy.
- Notion / Google Drive MCP: Connect your knowledge base. Instead of copy-pasting customer interviews into the Intake folder, you can tell the Orchestrator: "Fetch the last 5 Gong transcripts from Notion and run the Jobs-to-be-Done (JTBD) agent."
- GitHub MCP: Connect your codebase. The OS can read PR velocity to understand true engineering constraints before proposing an aggressive roadmap.
Note: You don't need MCP to use The Last PM — you can always just paste your PRDs or transcripts directly into the 00_Intake_and_Backlog folder. But wiring up MCP turns the system from a consultant into a fully integrated Chief of Staff.