Show HN: PM Workflow Copilot AI Product-Management Workflow in Cursor/Cline IDEs

3 days ago 1

GitHub last commit GitHub license PRs welcome

AI Product‑Management copilot for Cursor & Cline IDEs ‑ guiding you from idea ➜ MVP docs with chat‑first workflows.


Product teams at fast‑moving startups rarely have time to open Confluence. Yet skipping structured discovery & scoping leads to feature creep and re‑work. pm‑workflow‑copilot‑ide embeds a lightweight, opinionated product‑management workflow inside the editor chat you already use, keeping momentum while safeguarding first‑principles rigor.


  1. Rules file is loaded by Cursor/Cline so the assistant understands the workflow and file‑naming conventions.
  2. On first mention of a project (e.g. “weather app”) the copilot creates pm_project_docs/<project_name>/.
  3. For every workflow step it suggests the next best action and offers to auto‑generate artefacts (Opportunity Brief, MVP Scope, Usability Findings…).
  4. All artefacts are Markdown stored alongside code, enabling docs‑as‑code review flows.
  5. Progress is logged to pm-progress.json for instant context recall.

💬 What Using the Copilot Feels Like (Sample Dialogs)

Below are a handful of concise interactions that illustrate typical usage. Real wording varies by IDE, but the flow stays the same.

1. Kick‑off from a Rough Idea

You: I want to build an app that helps freelancers track billable hours. Copilot: Excellent! Let’s begin with Strategic Alignment. Who's the primary user and what pain are we solving?

2. Checking Project Progress

You: How far along is my "weather_app" project and what's next? Copilot: Progress → Product Charter ✓ • User Flow ✓ • MVP Scope ✓ Next → Prototype & usability testing → `usability_findings.md` → business viability check.

3. Clarifying Workflow Stage

You: Which phase are we in now? Copilot: You're in Feasibility & Viability. Technical feasibility completed; business viability still pending. Shall I draft `business_viability.md`?

4. Requesting a New Artefact

You: Generate the MVP scope for the budgeting tool, please. Copilot: Drafting `pm_project_docs/budgeting_tool/mvp_scope.md` with user stories, success metrics, and out‑of‑scope items…

(Conversation styles differ across IDEs; snippets are simplified for readability.)


# 1 – clone the repo (or copy rules file into an existing project) $ git clone https://github.com/your‑org/pm‑workflow‑copilot‑ide.git # 2 – point your IDE to the rules file # Cursor: no further works to do # Cline : no further works to do # Roo Code, Github Copilot, Windsurf, etc: copy .clinerules/.pm_workflow_assistant to specified paths for project/workspace custom rules in these IDEs # 3 – open a project folder and start chatting

Tip: keep your product‑management artefacts in git. They get versioned automatically, and reviewers can PR suggestions like any code change.


pm‑workflow‑copilot‑ide/ ├── .clinerules/ # Core prompt rules loaded by IDE └── .pm_workflow_assistant ├── docs/ │ └── product_management_workflow_startup.md # Detailed framework (read‑only) ├── examples/ # End‑to‑end transcripts & sample artefacts └── pm_project_docs/ └── weather‑app/ # ← generated per project ├── opportunity_brief.md ├── mvp_scope.md ├── usability_findings.md ├── technical_feasibility.md ├── business_viability.md └── pm-progress.json

Phase Key Output Trigger Command / Prompt
Strategic Alignment product_charter.md "Who is this for?"
Problem Discovery opportunity_brief.md "Draft 5 survey Qs"
Solution Definition mvp_scope.md "Prioritize MVP features"
Feasibility & Viability technical_feasibility.md
business_viability.md
"Assess tech risks"
Requirements prd.md "Generate PRD"

Heads‑up: pm‑workflow‑copilot‑ide began as a proving ground for bringing lightweight product‑management support into the broader Rulebook‑AI ecosystem — a cross‑IDE "rules + memory bank" toolkit for AI coding assistants. The long‑term plan is to merge this functionality upstream and deprecate this standalone repo once parity is reached. Follow the Rulebook‑AI repo for consolidated updates.


  • Context‑aware commands for VS Code extension
  • Slack bot companion for cross‑functional reviews
  • Automatic link‑back between PRs and related PM artefacts

Check the issues list for more.


  1. Fork and create a feature branch.
  2. Follow Conventional Commits for commit messages.
  3. Run pre‑commit install to auto‑format Markdown.
  4. Open a PR – the README’s badges will update once CI passes.

We love fresh perspectives from PMs, designers & engineers alike.


Distributed under the MIT License. See LICENSE for details.


  • Inspired by Tom Preston‑Werner’s "README first" philosophy.
  • Workflow adapted from the open‑source [Product Management Workflow for Startups].
  • Badges by shields.io.# pm-workflow-copilot-ide

GitHub last commit GitHub license PRs welcome

Read Entire Article