Added a full set of rules for Product Managers #139
Conversation
WalkthroughAdds a new “documentation-product-manager-multiuse-toolkit” containing multiple Markdown-based PM templates, a canonical product-context, a context generator rule, helper docs and data, alternate templates, an output placeholder, README, and LICENSE. Templates cover PRDs, epics, user stories, journeys, roadmaps, RICE, personas, lean canvas, positioning, KPI→revenue mapping, and risk analyses. Changes
Sequence Diagram(s)sequenceDiagram
autonumber
actor PM as Product Manager
participant Rules as Project Rules Engine
participant Ctx as product-context.mdc
participant Tmpl as Template Rule (e.g., PRD/Epic/RICE)
participant FS as /product-documents/
PM->>Rules: Natural-language request (e.g., "Create PRD")
Rules->>Ctx: Load context (alwaysApply)
Rules->>Tmpl: Apply selected template instructions
Tmpl-->>Rules: Generated markdown content
Rules->>FS: Save file with naming convention
Rules-->>PM: Return/open generated document
sequenceDiagram
autonumber
actor PM as Product Manager
participant CGen as context-generator.mdc
participant Ctx as product-context.mdc
PM->>CGen: Provide 1-line Product Concept (if prompted)
CGen->>Ctx: Search/replace only specified sections (preserve rest)
CGen-->>PM: Updated context ready for templates
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Suggested reviewers
Poem
Tip 🔌 Remote MCP (Model Context Protocol) integration is now available!Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats. ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 11
🧹 Nitpick comments (62)
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-context.mdc (3)
6-6: Grammar: “experience” → “experienced”.Minor polish for professionalism.
-You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experience Product Manager. +You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experienced Product Manager.
38-38: Grammar: prefer “Try to keep it …” and expand numerals in prose.-[LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY AND KEEP IT TO 1 OR 2 SENTENCES] +[LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY TO KEEP IT TO ONE OR TWO SENTENCES]
57-58: Improve imperative phrasing of file actions.-- **Write file**: Save the generated content to the file -- **Open the file** for editing +- **Write the file**: Save the generated content. +- **Open the file** for editing.rules/documentation-product-manager-multiuse-toolkit/helper-docs/extra-copy-context.txt (4)
6-6: Grammar: “experience” → “experienced”.-You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experience Product Manager. +You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experienced Product Manager.
38-38: Grammar: expand numerals in prose and use “Try to …”.-[LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY AND KEEP IT TO 1 OR 2 SENTENCES] +[LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY TO KEEP IT TO ONE OR TWO SENTENCES]
57-58: Phrasing and punctuation for file actions.-- **Write file**: Save the generated content to the file -- **Open the file** for editing +- **Write the file**: Save the generated content. +- **Open the file** for editing.
1-60: Avoid duplication with product-context.mdc to prevent drift.This file duplicates the template in
.cursor/rules/product-context.mdc. Prefer a single source of truth (link or reference) to reduce maintenance risk.Would you like a PR follow-up that replaces this file with a short pointer to the canonical template?
rules/documentation-product-manager-multiuse-toolkit/alternate-templates/epic-alternate (4)
12-12: Grammar: “Try to define …”-You are to generate the Epics for the product to match the time frame and scope. Try and define no more than *3* epics in total. +You are to generate the Epics for the product to match the time frame and scope. Try to define no more than *3* epics in total.
18-18: Punctuation: use “e.g.,”-4. List the business unit in charge of this (eg, Design, Engineering, Marketing) +4. List the business unit in charge of this (e.g., Design, Engineering, Marketing)
21-31: Wrap example in a code block for readability.### Example Epic Output: +"``` "Epic": "User Authentication System", "Description": "Implement secure login and registration flows for all user types. This includes password management, session handling, and integration with existing SSO providers.", "Dependencies": [], "Business Unit": "Engineering" "Epic": "Product Catalog Management", "Description": "Create a comprehensive system for managing product listings, categories, and inventory. Enable administrators to easily add, edit, and organize products.", "Dependencies": ["Epic: User Authentication System"], "Business Unit": "Engineering" +"```"
35-35: Tighten wording (“per epic”).-Stop and think about the Epics you just wrote, and then come up with *5* User Stories each for each of the Epics. +Stop and think about the Epics you just wrote, then create *5* user stories per epic.rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/risk-analysis-template.mdc (3)
5-9: Fix context mismatch and typos (“User Stories”, “for for”, “the this”).Align the preamble with this file’s purpose and clean up wording.
-Before writing the User Stories, ask a short Clarifying Question to the user about what the Specific Feature is (do not provide ideas). +Before writing the Risk Analysis, ask a short Clarifying Question to the user about what the Specific Feature is (do not provide ideas). ONLY THEN, continue with the rest of this document. -Be sure to use the @product-context.mdc data for for initial context. +Be sure to use the @product-context.mdc data for initial context. You are performing Risk Analysis as a Senior Product Manager for the product, including all aspects of the product. -Then, write a Risk Analysis for the Feature to be developed, using the this format: +Then, write a Risk Analysis for the feature to be developed, using this format:
11-16: Grammar, capitalization, and clarity in category instructions.Polish examples, capitalization of “Product Market Fit,” and a small grammar nit.
## Risk Factor Categories Given the Product Context and Feature/Product to be developed, what are the three main risk categories involved in such a product? -Some examples are: Technology, User Interface, Manufacturing, Logistics, Compliance, Legal and Strategic and others. -Do not list 'Product market fit' as one of them! -List the three main risks categories first. +Examples include: Technology, User Interface, Manufacturing, Logistics, Compliance, Legal, Strategic, etc. +Do not list 'Product Market Fit' as one of them. +List the three main risk categories first.
18-26: “Table” vs list, newline wording, and stray apostrophe.The example is a list, not a table; clarify newline wording and remove the trailing quote.
-## Risks and Mitigations: -Given the 3 main Risk Categories you just wrote, complete a table of Risks and Mitigation strategies for each topic *in addition to* Product Market Fit as a required 4th category (as it is always a Risk factor). +## Risks and Mitigations: +Given the 3 main Risk Categories you just wrote, compile a list of Risks and Mitigation strategies for each category, *in addition to* Product Market Fit as a required 4th category (as it is always a risk factor). Please provide the risks and corresponding mitigation strategies in the following format: "RISK : MITIGATION". For each Risk, write a single Mitigation Strategy. Write only 3 entries of risks and mitigations for each category. -Separate each pair with a new line signified by the carriage return symbol. Example response: +Separate each pair with a newline. Example: Category 1 RISK 1 : MITIGATION 1 RISK 2 : MITIGATION 2 -RISK 3 : MITIGATION 3' +RISK 3 : MITIGATION 3rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-positioning.mdc (1)
8-10: Minor clarity edits (“for for”; “Try and” → “Try to”).-Be sure to use the @product-context.mdc data for for initial context. +Be sure to use the @product-context.mdc data for initial context. Then, you will write 2 Elevator Pitches using the templates below. -Write only the pitch, no other text before or after the pitch. Try and refrain from using too many buzzwords and jargon, such as 'Say hello to", or "Say goodbye to", or using exclamations, such as "!" or "?!" +Write only the pitch, no other text before or after the pitch. Try to refrain from using too many buzzwords and jargon, such as "Say hello to", "Say goodbye to", or exclamations like "!" or "?!"rules/documentation-product-manager-multiuse-toolkit/product-documents/Contents.txt (1)
1-1: Consider making this a README.md for visibility.GitHub renders Markdown by default; a README.md in this directory would be more discoverable.
Want me to draft a minimal README.md explaining output conventions and example filenames?
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/persona-template.mdc (3)
2-3: Align description with body (“Ideal” vs “Regular”).-description: Defining 2 User Personas for the product: Regular and Skeptical Personas +description: Defining 2 User Personas for the product: Ideal and Skeptical Personas
22-23: Numbered list formatting is compressed into one line.Split into separate lines for consistency and readability.
-1. Their name 2. Overview, 3. Goals, 4. Behaviors, 5. Pains and 6. Needs +1. Their name +2. Overview +3. Goals +4. Behaviors +5. Pains +6. Needs
27-27: Simplify the final instruction.Avoid the awkward “'''markdown'''” phrasing.
-Write the response in Markdown format, without writing '''markdown''' or anything else, and without using any other formatting. +Write the response in Markdown format only.rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.md (5)
6-6: Grammar: “experience” → “experienced”.-You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experience Product Manager. +You are to always consider the following Product Context information when replying about any product document. All generated documents should reference the information provided here, and you will respond as an experienced Product Manager.
12-12: Make the 1‑line description concise and specific.-An extension for your coding IDE that allows you to use it instead for generating Documents for Product Managers using its built-in AI generators +An IDE extension that generates Product Management documents with built‑in AI
20-23: Capitalize consistently.-- Product management software +- Product Management Software
38-38: Differentiator is marketing-heavy; tighten to a crisp value statement.-Seamlessly streamline your document generation process within your coding IDE using cutting-edge AI technology, empowering your product management workflow like never before. +AI‑native document generation inside the IDE to reduce context switching and accelerate PM workflows.
41-41: Reduce repetition; make the summary sharper.-Our innovative product addresses the time-consuming manual document creation processes that Product Managers face, providing an efficient solution by integrating AI-powered document generation within coding IDEs. This streamlines workflow for tech-savvy PMs, Agile Software Development Teams, and IT Project Management Professionals, offering seamless collaboration and customization options. The key differentiator lies in our ability to revolutionize document generation within the coding environment, empowering PMs to enhance productivity and efficiency through cutting-edge AI technology. Ultimately, our mission is to empower Product Managers with a unified toolset that optimizes workflow and enhances collaboration across teams for improved project outcomes. +AgileGen eliminates manual PM documentation by embedding AI-driven generators directly in coding IDEs. It streamlines collaboration among PMs, developers, and stakeholders, and supports customization across methodologies. By working where teams already build software, AgileGen improves productivity and reduces tool fragmentation, leading to faster, more consistent product documentation.rules/documentation-product-manager-multiuse-toolkit/helper-docs/list_of_product_metrics_text_only.txt (2)
9-11: Fix duplicate phrase and typo; normalize bullet formatting on flagged lines.Removes repeated clause, corrects “Annial,” and standardizes asterisk spacing where inconsistent.
@@ @@ @@Also applies to: 116-116, 21-23, 135-137
1-160: Consistency pass recommended (bullets, headings, math notation).There’s mixed use of “Metric” vs “ Metric,” and math like “DAU / MAU” vs “1/Churn Rate.” Consider a quick sweep to standardize bullet spacing and formula spacing for readability.
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-story-template.mdc (1)
8-8: Typo: duplicate word “for for”.rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/RICE-analysis-template.mdc (2)
11-11: Typo: duplicate word “for for”.
20-24: Clarify the “JSON-only” step to avoid conflict with later narrative sections.Make it explicit that only the RICE estimation step should be JSON-only; later sections may include prose.
Also applies to: 56-61
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/roadmap-template.mdc (2)
6-6: Typo: duplicate word “for for”.
13-33: Optional: add timeline context and capacity guardrails.Consider adding “Assumptions/Dependencies,” “Resource/Capacity notes,” and “Now/Next/Later” alt view to improve planning flexibility.
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/lean-canvas-template.mdc (2)
7-9: Tone/grammar nits.Minor clarity and style improvements.
12-29: Optional: soften “Rethink” to “Refine” and ensure consistent capitalization.@@Also applies to: 35-42
rules/documentation-product-manager-multiuse-toolkit/README.md (4)
9-9: Fix bare URL and tighten wording.Replace the bare link with a proper Markdown link and clarify the phrasing.
-**Note that the Cursor Rules now follow a newer paradigm (no longer .cursorrules), as defined here**: https://docs.cursor.com/en/context/rules +**Note:** Cursor Rules now follow a newer paradigm (not .cursorrules). See the official docs: [docs.cursor.com/en/context/rules](https://docs.cursor.com/en/context/rules).
74-98: Add fence language and align the folder name + typos in tree.
- Specify a language for the fenced block (markdownlint MD040).
- The root dir shown (“pm-cursor-generator/”) doesn’t match the actual path in this repo. Align or state “example layout.”
- Fix “alternate_read.me” → “README.md”.
-``` -pm-cursor-generator/ +```text +documentation-product-manager-multiuse-toolkit/ ├── .cursor/rules/ # Cursor Project Rules @@ -├── alternate-templates/ # alternate versions of templates -| ├── alternate_read.me -| └── etc.... +├── alternate-templates/ # Alternate versions of templates +│ ├── README.md +│ └── ... @@ -├── helper-docs/ # helper documentation and examples -| ├── example-product-context.md # an example of what this should look like -| └── etc.... # *.txt files that can add extra information for templates +├── helper-docs/ # Helper documentation and examples +│ ├── example-product-context.md # Example structure +│ └── ... # *.txt files with extra info for templates └── README.mdWould you prefer to present this as a generic example layout instead? --- `68-71`: **Confirm auto-creation claim for /product-documents/.** Cursor Rules alone may not auto-create folders/files. If this depends on a separate workflow, clarify or soften the claim. ```diff -- Creates `/product-documents/` folder automatically -– Maintains unique document IDs with timestamps -– Documents are ready for immediate use +- Use `/product-documents/` for outputs (create if missing). +- Keep unique document IDs with timestamps. +- Documents are ready for immediate use after generation.
16-19: Minor copy edits for concision and consistency.-### 1. **Download & Setup** (2 minutes) -- Download this repo to a new folder for your project -- No installation required - just need Cursor itself +### 1. **Download & Setup** (~2 minutes) +- Clone or download this repo into your project +- No installation required—only Cursorrules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-journey-template.mdc (7)
6-11: Fix typos and tighten intro.
- Double “for”.
- “speciality” → “specialty” (or “specialization”).
- “using the this format” wording.
-Be sure to use the @product-context.mdc data for for initial context. -You are writing the User Journey for the feature to be developed as a Product Manager with a speciality in UI and UX. -Then, write a User Journey for the Feature to be developed, using the this format: +Be sure to use @product-context.mdc for initial context. +Write the User Journey as a PM with a specialty in UI/UX. +Then write a User Journey for the feature using this format:
12-17: Clarify phase limits and sentence casing.-This can be from 3 to 5 phases, depending upon the complexity of the task. -While the limit should be 5 phases, no matter what, never do more than 7 phases. -The Phases should be described by no more than 8 words +Use 3–5 phases based on task complexity (never exceed 7). +Describe each phase in ≤8 words.
19-22: Grammar and brevity in Actions.-Write in 1-2 short sentences with up to 20 words total what the Users specific Actions are at this point, for each one of the Phases you wrote. +Write 1–2 short sentences (≤20 words total) describing the user's specific actions for each phase.
24-28: Possessives and clarity in Needs & Pains.-Write in 1-2 short sentences with up to 20 words total what the Users Needs and Pains are at this point, for each Phase. +Write 1–2 short sentences (≤20 words total) for each phase describing the user's needs and pains.
30-34: Reduce redundancy and standardize casing.-Think about how the user interacts with the Product at each Phase. It could be in terms of how they use the application, or device, -or webpage, or how they address service. This is the Touchpoint that the user has with the product. -Write the potential Touchpoints that the User has at each Phase. -For the TOUCHPOINTS, make each no more than 1 sentence of up to 12 words. +Describe how the user interacts with the product at each phase (app, device, web, support). +Write each touchpoint in ≤1 sentence and ≤12 words.
36-38: Lowercase “What” and tighten constraints.-For each of the Phases, What are the main Opportunities for improvement or development at this point/Phase? -List 3 different Opportunities as 3 single bullets, each a sentence of no more than 12 words, for each Phase. +For each phase, list three opportunities for improvement or development. +Use single-sentence bullets (≤12 words each).
39-41: Clarify summary format.-Write out the results sequentially *for each Phase* - List the Phase, then after that the Actions, Needs & Pains, Touchpoints and Opportunities for each Phase. They should be written in Markdown format, for easy viewing. +For each phase, output in Markdown: Phase, Actions, Needs & Pains, Touchpoints, Opportunities.rules/documentation-product-manager-multiuse-toolkit/helper-docs/kpi_revenues.txt (6)
8-11: Clarify non-revenue alternatives and style.-For companies that are not for-profit, or have non-revenue related business objectives (such as Tech development), here are some potential metrics/indicators that can be used instead of Growth, Retention and Margins: -Social Impact, Technology Adoption/Breakthrough, Open-source Contributions, Patents Filed, Sustainability Goals, Workplace Safety, Supply chain resilience, Energy Consumption. -These should only be used if it is clear that the company is not one interested in Revenues directly. +For non-profits or orgs with non-revenue objectives (e.g., tech advancement), consider: +Social Impact, Technology Adoption/Breakthrough, Open-source Contributions, Patents Filed, Sustainability Goals, Workplace Safety, Supply-chain Resilience, Energy Consumption. +Use these only when revenue is not a primary objective.
12-14: Tighten wording; remove redundancy.-Given the Revenue Goal, there are typically KPIs that directly relate to this goal. Here is a partial list of Revenue Goals, and the types of KPIs that are associated with them. -Note that each Goal has 2 sub-categories of metrics that reach that goal: +Each Revenue Goal typically aligns to two sub-categories of KPIs:
23-27: Standardize terminology.
- “Net Retention Revenue (NRR)” is commonly “Net Revenue Retention (NRR).”
- “Multi Stock Keeping Unit (SKU)” → “Multiple SKUs.”
-b. Net Retention Revenue (NRR) -c. Multi Stock Keeping Unit (SKU) +b. Net Revenue Retention (NRR) +c. Multiple SKUs
36-39: Use commonly accepted retention terms consistently.Consider GRR/NRR or GDR/NDR, but don’t mix. You already use NRR above.
-c. Gross and Net Dollar Retention (GDR, NDR) +c. Gross Revenue Retention (GRR) and Net Revenue Retention (NRR)
41-47: Clarify pricing terms.-1. Product pricing: -a. $ gating -b. Up/down/cross-sell -c. Monetizable account +1. Product pricing: +a. Paywall/price gating +b. Up-sell / Down-sell / Cross-sell +c. Monetizable accounts
48-50: Group cost metrics more precisely.CAC isn’t a service cost; consider “Acquisition and Service Costs,” or leave as-is but note the nuance.
-2. Service Costs: +2. Acquisition and Service Costs:rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/epic-generator-template.mdc (2)
8-18: Add language to fenced header block.-``` +```markdown # Epic Plan: [Feature Set/Initiative Name] @@ **Version:** 1.0--- `53-63`: **Add language to fenced Sub-Epic block.** ```diff -``` +```markdown #### **Epic X.Y: [Feature Component Name]** @@ - **Priority:** P0 (Critical) / P1 (High) / P2 (Medium)</blockquote></details> <details> <summary>rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/kpi-revenues-template.mdc (4)</summary><blockquote> `8-9`: **Keep model guidance tool-agnostic.** Refer generically to larger-context models in Cursor rather than a specific vendor/version. ```diff -**Also, advise the user that it may be better to manually switch to Gemini 2.5, which has a larger context window for this** +If you hit context limits, consider switching to a larger-context model within Cursor.
10-12: Fix double word and tighten sentence.-Be sure to use the @product-context.mdc data for for initial context. -Then, sequentially answer the following sections to help create Metrics for a Product Manager to help explain the "Why" for a product: +Be sure to use @product-context.mdc for initial context. +Then, sequentially answer the following to define PM metrics that explain the product “why”:
23-24: Decision gate: ensure the flow actually waits.Add an explicit “pause” instruction so LLMs don’t continue without a selection.
-**Ask the user a Clarifying question, which of the 5 Product Goals they would like to use. Only continue once you have a single Product Goal defined by the user!** +**Ask which of the 5 Product Goals to use and pause. Do not proceed until the user selects exactly one.**
60-67: Close the quote and simplify output instruction.-Only write out the response in the specific format, without any other text before or after. +Output only the following—no extra text: @@ -Follow this by listing the ONE Metric that best captures the core value our product delivers to customers. Write it as: -"One Metric That Matters Most: [Metric] +Then add: +One Metric That Matters Most: [Metric]rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/context-generator.mdc (2)
35-41: Clarify which file’s YAML is being preserved (and avoid hard-coding alwaysApply).“preserve the YAML frontmatter (--- alwaysApply: true ---)” can be misread as an instruction to change values. Make it explicit that this refers to the YAML in @product-context.mdc and that values must not change.
-**IMPORTANT**: You must preserve the following elements exactly as they are: -- The YAML frontmatter (--- alwaysApply: true ---) +**IMPORTANT**: In @product-context.mdc, preserve the following exactly as they are (do not change values): +- The YAML frontmatter (keep existing keys/values unchanged)
7-10: Scope the “single question first” gate to missing Product Concept only.You mention this parenthetically; make it explicit to avoid unnecessary prompts when the 1-liner is already present.
-You are to ask the user a single question first: +If the Product Concept is not already provided, ask the user a single question first:rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/prd-template.mdc (4)
6-6: Replace “User Stories” with “PRD”.This looks like a copy artifact.
-Before writing the User Stories, ask a short Clarifying Question +Before writing the PRD, ask a short Clarifying Question
100-108: Clean up press-release boilerplate (date/placeholders).Tighten the dateline and product-name placeholder to reduce ambiguity.
-Given a placeholder product name: <use the product name listed above> , and the customers, problem and solution listed above, you will describe the benefits to the user as a Press Release for this new goal. The format of the press release is: +Using the product name from @product-context.mdc, and the customers/problem/solution above, write a press release. Format: @@ -'New York, NY - in another: XX mo/wk/yr +'New York, NY — <Month DD, YYYY>
74-78: Disambiguate “Provide 4 L1 and L2 OKRs”.State exact counts and hierarchy to avoid inconsistent outputs.
-Provide 4 L1 and L2 OKRs to develop the feature or product. Each OKR should be a single sentence, no more than 25 words each. +Provide OKRs as follows: 2 L1 Objectives. For each L1, provide 2 L2 Key Results (4 KRs total). Each line ≤ 25 words.
11-16: Optionally split Market Opportunity into its own subheading for clarity.Improves skimmability and downstream parsing.
-## 1. Market Problem +## 1. Market Problem @@ -Then, describe the Market Opportunity for this problem. What is the market size for this problem and field, as found in existing market reports or similar report? +### Market Opportunity +Describe the market size for this problem and field, as found in existing market reports or similar reports.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (22)
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/RICE-analysis-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/context-generator.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/epic-generator-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/kpi-revenues-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/lean-canvas-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/persona-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/prd-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-context.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-positioning.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/risk-analysis-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/roadmap-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-journey-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-story-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/LICENSE(1 hunks)rules/documentation-product-manager-multiuse-toolkit/README.md(1 hunks)rules/documentation-product-manager-multiuse-toolkit/alternate-templates/alternate_read.me(1 hunks)rules/documentation-product-manager-multiuse-toolkit/alternate-templates/epic-alternate(1 hunks)rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.md(1 hunks)rules/documentation-product-manager-multiuse-toolkit/helper-docs/extra-copy-context.txt(1 hunks)rules/documentation-product-manager-multiuse-toolkit/helper-docs/kpi_revenues.txt(1 hunks)rules/documentation-product-manager-multiuse-toolkit/helper-docs/list_of_product_metrics_text_only.txt(1 hunks)rules/documentation-product-manager-multiuse-toolkit/product-documents/Contents.txt(1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
**/*.md
📄 CodeRabbit inference engine (.cursorrules)
Always use Markdown for documentation and README files
Files:
rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.mdrules/documentation-product-manager-multiuse-toolkit/README.md
**/*.{md,cursorrules}
📄 CodeRabbit inference engine (.cursorrules)
**/*.{md,cursorrules}: Use clear and concise language in all documentation and .cursorrules files
When adding examples or explanations, focus on practical use cases for Cursor AI users
Files:
rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.mdrules/documentation-product-manager-multiuse-toolkit/README.md
rules/*/README.md
📄 CodeRabbit inference engine (.cursorrules)
rules/*/README.md: Refer to the README in each folder for guidance on naming conventions and descriptions
Each .cursorrules file may have an accompanying README.md file in its folder; use this README to provide credit to the original author and a brief description of the .cursorrules file's purpose
Files:
rules/documentation-product-manager-multiuse-toolkit/README.md
🪛 LanguageTool
rules/documentation-product-manager-multiuse-toolkit/helper-docs/kpi_revenues.txt
[grammar] ~12-~12: There might be a mistake here.
Context: ...goal. Here is a partial list of Revenue Goals, and the types of KPIs that are associat...
(QB_NEW_EN)
[grammar] ~12-~12: There might be a mistake here.
Context: ...s of KPIs that are associated with them. Note that each Goal has 2 sub-categories...
(QB_NEW_EN)
[grammar] ~13-~13: There might be a mistake here.
Context: ...egories of metrics that reach that goal: **Growth (making revenue): 1. User growt...
(QB_NEW_EN)
[grammar] ~15-~15: There might be a mistake here.
Context: ...enue): 1. User growth and distribution: a. Active Users (AU, DAU, MAU) b. Net Pr...
(QB_NEW_EN)
[grammar] ~21-~21: There might be a mistake here.
Context: ...App Installs f. Click Through Rate (CTR) 2. Revenue Growth: a. Recurring Revenue (An...
(QB_NEW_EN)
[grammar] ~22-~22: There might be a mistake here.
Context: ...ck Through Rate (CTR) 2. Revenue Growth: a. Recurring Revenue (Annual, Monthly; A...
(QB_NEW_EN)
rules/documentation-product-manager-multiuse-toolkit/helper-docs/list_of_product_metrics_text_only.txt
[grammar] ~12-~12: There might be a mistake here.
Context: ... *Cost of Customer Acquisition (CAC) The cost of acquiring a new customer thr...
(QB_NEW_EN)
[grammar] ~21-~21: There might be a mistake here.
Context: ...s, or paid ads. * Cost Per Click (CPC) * Click-Through Rate (CTR) **Activation M...
(QB_NEW_EN)
[grammar] ~31-~31: There might be a mistake here.
Context: ...ete the onboarding process successfully. *Onboarding Drop-off Rate *User Activat...
(QB_NEW_EN)
[grammar] ~43-~43: There might be a mistake here.
Context: ...cess. *Product Qualified Accounts (PQA) *Product Qualified Leads (PQL) **Engage...
(QB_NEW_EN)
[grammar] ~122-~122: There might be a mistake here.
Context: ...-renewals within a specific time period. *Net Revenue Retention *Average Contrac...
(QB_NEW_EN)
[grammar] ~135-~135: There might be a mistake here.
Context: ...d as a ratio. *Customer Referral Rate The percentage of customers who refer ot...
(QB_NEW_EN)
rules/documentation-product-manager-multiuse-toolkit/helper-docs/extra-copy-context.txt
[grammar] ~5-~5: There might be a mistake here.
Context: ...ger Document Generator - Product Context You are to always consider the following...
(QB_NEW_EN)
[grammar] ~8-~8: There might be a mistake here.
Context: ...Product Manager. ## Product Information Product Name: [GIVE IT A SHORT NAME] ...
(QB_NEW_EN)
[grammar] ~11-~11: There might be a mistake here.
Context: ...ORT NAME] ## 1-line Product Description [A 1-LINER DESCRIPTION OF THE PRODUCT TH...
(QB_NEW_EN)
[grammar] ~12-~12: Ensure spelling is correct
Context: ...ME] ## 1-line Product Description [A 1-LINER DESCRIPTION OF THE PRODUCT THAT GENERAL...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~14-~14: There might be a mistake here.
Context: ...IZES THE SOLUTION] ## Problem Statement - [LIST AROUND 3 PROBLEMS THAT NEED TO BE ...
(QB_NEW_EN)
[grammar] ~15-~15: There might be a mistake here.
Context: ...ROUND 3 PROBLEMS THAT NEED TO BE SOLVED] - [PROBLEM 2] - [PROBLEM 3] ## Business F...
(QB_NEW_EN)
[grammar] ~16-~16: There might be a mistake here.
Context: ...MS THAT NEED TO BE SOLVED] - [PROBLEM 2] - [PROBLEM 3] ## Business Field - [PROVID...
(QB_NEW_EN)
[grammar] ~19-~19: There might be a mistake here.
Context: ...BLEM 2] - [PROBLEM 3] ## Business Field - [PROVIDE A 1-4 WORD DESCRIPTION OF THE F...
(QB_NEW_EN)
[grammar] ~20-~20: There might be a mistake here.
Context: ...IDE A 1-4 WORD DESCRIPTION OF THE FIELD] - [FIELD 2] - [FIELD 3] ## Type of Busine...
(QB_NEW_EN)
[grammar] ~21-~21: There might be a mistake here.
Context: ...RD DESCRIPTION OF THE FIELD] - [FIELD 2] - [FIELD 3] ## Type of Business [LIST ONE...
(QB_NEW_EN)
[grammar] ~24-~24: There might be a mistake here.
Context: ...IELD 2] - [FIELD 3] ## Type of Business [LIST ONE OF THESE: B2B, B2C, B2B2C, B2G...
(QB_NEW_EN)
[grammar] ~27-~27: There might be a mistake here.
Context: ..., B2B2C, B2G, ETC.] ## Target Customers - [LIST AROUND 3 CUSTOMERS OF THE PRODUCT]...
(QB_NEW_EN)
[grammar] ~28-~28: There might be a mistake here.
Context: ...[LIST AROUND 3 CUSTOMERS OF THE PRODUCT] - [CUSTOMER 2] - [CUSTOMER 3] ## Specific...
(QB_NEW_EN)
[grammar] ~29-~29: There might be a mistake here.
Context: ...CUSTOMERS OF THE PRODUCT] - [CUSTOMER 2] - [CUSTOMER 3] ## Specific Solution - [LI...
(QB_NEW_EN)
[grammar] ~33-~33: There might be a mistake here.
Context: ...N COMPONENTS OF YOUR SOLUTION. BE BRIEF] - [SOLUTION PART 2] - [SOLUTION PART 3] #...
(QB_NEW_EN)
[grammar] ~34-~34: There might be a mistake here.
Context: ... SOLUTION. BE BRIEF] - [SOLUTION PART 2] - [SOLUTION PART 3] ## Differentiator [LI...
(QB_NEW_EN)
[grammar] ~40-~40: There might be a mistake here.
Context: ...TO 1 OR 2 SENTENCES] ## Product Summary [SUMMARIZE YOUR PRODUCT IN A SINGLE PARA...
(QB_NEW_EN)
[grammar] ~47-~47: There might be a mistake here.
Context: ...tion ## Writing Style and File Format - Use clear, concise language - Avoid tech...
(QB_NEW_EN)
[grammar] ~55-~55: There might be a mistake here.
Context: ...ectory - Use the naming convention: [TYPE]-[description]-[version].md - Write file: Save the generated content...
(QB_NEW_EN)
rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.md
[grammar] ~5-~5: There might be a mistake here.
Context: ...ger Document Generator - Product Context You are to always consider the following...
(QB_NEW_EN)
[grammar] ~8-~8: There might be a mistake here.
Context: ...Product Manager. ## Product Information Product Name: AgileGen ## 1-line Prod...
(QB_NEW_EN)
[grammar] ~14-~14: There might be a mistake here.
Context: ...t-in AI generators ## Problem Statement - Product Managers face time-consuming man...
(QB_NEW_EN)
[grammar] ~15-~15: There might be a mistake here.
Context: ... creation processes for project details. - Inefficient integration between coding I...
(QB_NEW_EN)
[grammar] ~19-~19: There might be a mistake here.
Context: ... documentation tasks. ## Business Field - Productivity Tools - SaaS Technology - P...
(QB_NEW_EN)
[grammar] ~20-~20: There might be a mistake here.
Context: ... ## Business Field - Productivity Tools - SaaS Technology - Product management sof...
(QB_NEW_EN)
[grammar] ~21-~21: There might be a mistake here.
Context: ...d - Productivity Tools - SaaS Technology - Product management software ## Type of ...
(QB_NEW_EN)
[grammar] ~24-~24: There might be a mistake here.
Context: ...management software ## Type of Business B2B ## Target Customers - Tech-savvy Pr...
(QB_NEW_EN)
[grammar] ~27-~27: There might be a mistake here.
Context: ...ype of Business B2B ## Target Customers - Tech-savvy Product Managers - Agile Soft...
(QB_NEW_EN)
[grammar] ~28-~28: There might be a mistake here.
Context: ... Customers - Tech-savvy Product Managers - Agile Software Development Teams - IT Pr...
(QB_NEW_EN)
[grammar] ~29-~29: There might be a mistake here.
Context: ...agers - Agile Software Development Teams - IT Project Management Professionals ## ...
(QB_NEW_EN)
[grammar] ~34-~34: There might be a mistake here.
Context: ...n for PMs, developers, and stakeholders through unified toolset. - Customization option...
(QB_NEW_EN)
[grammar] ~34-~34: There might be a mistake here.
Context: ...nd stakeholders through unified toolset. - Customization options tailored for vario...
(QB_NEW_EN)
[grammar] ~37-~37: There might be a mistake here.
Context: ...odologies and styles. ## Differentiator Seamlessly streamline your document gene...
(QB_NEW_EN)
[grammar] ~40-~40: There might be a mistake here.
Context: ...w like never before. ## Product Summary Our innovative product addresses the tim...
(QB_NEW_EN)
[grammar] ~47-~47: There might be a mistake here.
Context: ...tion ## Writing Style and File Format - Use clear, concise language - Avoid tech...
(QB_NEW_EN)
[grammar] ~55-~55: There might be a mistake here.
Context: ...ectory - Use the naming convention: [TYPE]-[description]-[version].md - Write file: Save the generated content...
(QB_NEW_EN)
rules/documentation-product-manager-multiuse-toolkit/README.md
[grammar] ~5-~5: There might be a mistake here.
Context: ...ursor's AI capabilities. ## 🎯 Overview This project provides a modern approach ...
(QB_NEW_EN)
[grammar] ~11-~11: There might be a mistake here.
Context: ....com/en/context/rules ## 🚀 Quick Start ### 📹 Video Tutorial (Recommended First...
(QB_NEW_EN)
[grammar] ~13-~13: There might be a mistake here.
Context: ...ideo Tutorial** (Recommended First Step) 🎥 **[Watch the Setup Tutorial](https://...
(QB_NEW_EN)
[grammar] ~14-~14: There might be a mistake here.
Context: ...ow to get started in just a few minutes! ### 1. Download & Setup (2 minutes) - Do...
(QB_NEW_EN)
[grammar] ~16-~16: There might be a mistake here.
Context: ... ### 1. Download & Setup (2 minutes) - Download this repo to a new folder for y...
(QB_NEW_EN)
[grammar] ~20-~20: There might be a mistake here.
Context: ...Configure Your Product* (2-10 minutes) 2 options: 1. Manually edit `.cursor/ru...
(QB_NEW_EN)
[grammar] ~21-~21: There might be a mistake here.
Context: ...Your Product** (2-10 minutes) 2 options: 1. Manually edit `.cursor/rules/product-con...
(QB_NEW_EN)
[grammar] ~22-~22: There might be a mistake here.
Context: ...in the helper-docs directory as a guide. 2. Use the AI helper to automatically gener...
(QB_NEW_EN)
[grammar] ~23-~23: There might be a mistake here.
Context: ...AI helper to automatically generate one: - Type @context-generator.mdc in Cursor ...
(QB_NEW_EN)
[grammar] ~30-~30: There might be a mistake here.
Context: ...nts** (Immediate!) Simply ask Cursor AI: - "Create a PRD for user authentication" -...
(QB_NEW_EN)
[grammar] ~32-~32: There might be a mistake here.
Context: ...uthentication" - "Generate user stories for checkout process" - "Make a persona for...
(QB_NEW_EN)
[grammar] ~36-~36: There might be a mistake here.
Context: ... Q1 features" ## 📋 What You Can Create - PRD (Product Requirements Document) - ...
(QB_NEW_EN)
[grammar] ~38-~38: There might be a mistake here.
Context: ... - PRD (Product Requirements Document) - User Stories & Acceptance Criteria - *...
(QB_NEW_EN)
[grammar] ~39-~39: There might be a mistake here.
Context: ...* - User Stories & Acceptance Criteria - User Personas (Regular & Skeptical) - ...
(QB_NEW_EN)
[grammar] ~40-~40: There might be a mistake here.
Context: ... User Personas (Regular & Skeptical) - Product Roadmaps - Epics Generator...
(QB_NEW_EN)
[grammar] ~41-~41: There might be a mistake here.
Context: ...egular & Skeptical) - Product Roadmaps - Epics Generator - **RICE Prioritizatio...
(QB_NEW_EN)
[grammar] ~42-~42: There might be a mistake here.
Context: ...Product Roadmaps - Epics Generator - RICE Prioritization Analysis - **User ...
(QB_NEW_EN)
[grammar] ~43-~43: There might be a mistake here.
Context: ...rator** - RICE Prioritization Analysis - User Journey Maps - **Lean Canvas (Pro...
(QB_NEW_EN)
[grammar] ~44-~44: There might be a mistake here.
Context: ...ization Analysis** - User Journey Maps - Lean Canvas (Product Strategy) - **Pro...
(QB_NEW_EN)
[grammar] ~45-~45: There might be a mistake here.
Context: ...aps** - Lean Canvas (Product Strategy) - Product Positioning (Elevator Pitch) -...
(QB_NEW_EN)
[grammar] ~46-~46: There might be a mistake here.
Context: ...- Product Positioning (Elevator Pitch) - KPI to Revenue Connector - **Risk Anal...
(QB_NEW_EN)
[grammar] ~47-~47: There might be a mistake here.
Context: ...or Pitch)** - KPI to Revenue Connector - Risk Analysis ## 🎯 How It Works #...
(QB_NEW_EN)
[grammar] ~52-~52: There might be a mistake here.
Context: ... Risk Analysis ## 🎯 How It Works ### 1. Project Rules Integration The `.cur...
(QB_NEW_EN)
[grammar] ~54-~54: There might be a mistake here.
Context: ...orks ### 1. Project Rules Integration The .cursor/rules/ files provide: - **...
(QB_NEW_EN)
[grammar] ~55-~55: There might be a mistake here.
Context: ...on** The .cursor/rules/ files provide: - Product Context: Always included in AI...
(QB_NEW_EN)
[grammar] ~56-~56: There might be a mistake here.
Context: ...t**: Always included in AI conversations - Template Instructions: Guide AI on doc...
(QB_NEW_EN)
[grammar] ~57-~57: There might be a mistake here.
Context: ...ctions**: Guide AI on document structure - Writing Guidelines: Ensure consistent ...
(QB_NEW_EN)
[grammar] ~60-~60: There might be a mistake here.
Context: ...nt quality ### 2. AI-Powered Creation When you ask Cursor AI to create a docum...
(QB_NEW_EN)
[grammar] ~61-~61: There might be a mistake here.
Context: ... you ask Cursor AI to create a document: 1. AI reads the Product-Context from Projec...
(QB_NEW_EN)
[grammar] ~67-~67: There might be a mistake here.
Context: ...r naming ### 3. Smart File Management - Creates /product-documents/ folder aut...
(QB_NEW_EN)
[grammar] ~72-~72: There might be a mistake here.
Context: ...r immediate use ## 📁 Project Structure pm-cursor-generator/ ├── .cursor/rules/ # Cursor Project Rules │ ├── product-context.mdc # Product context (*always* applied) │ ├── context-generator.mdc # helps generate your product context │ ├── prd-template.mdc # PRD creation instructions │ ├── user-story-template.mdc │ ├── persona-template.mdc │ ├── roadmap-template.mdc │ ├── epic-generator-template.mdc │ ├── rice-analysis-template.mdc │ ├── user-journey-template.mdc │ ├── lean-canvas-template.mdc │ ├── product-positioning.mdc │ ├── kpi-revenues-template.mdc │ └── risk-analysis-template.mdc ├── product-documents/ # Generated documents (output) ├── alternate-templates/ # alternate versions of templates | ├── alternate_read.me | └── etc.... ├── helper-docs/ # helper documentation and examples | ├── example-product-context.md # an example of what this should look like | └── etc.... # *.txt files that can add extra information for templates └── README.md ## 🤝 Contributing 1. Fork the repository ...
(QB_NEW_EN)
[grammar] ~100-~100: There might be a mistake here.
Context: ...es └── README.md ``` ## 🤝 Contributing 1. Fork the repository 2. Create a feature ...
(QB_NEW_EN)
[grammar] ~108-~108: There might be a mistake here.
Context: ... 5. Submit a pull request ## 📄 License MIT License - see LICENSE file for detai...
(QB_NEW_EN)
🪛 markdownlint-cli2 (0.17.2)
rules/documentation-product-manager-multiuse-toolkit/README.md
9-9: Bare URL used
(MD034, no-bare-urls)
74-74: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🔇 Additional comments (4)
rules/documentation-product-manager-multiuse-toolkit/LICENSE (1)
1-21: LGTM on MIT license text.Standard MIT terms look intact with correct year and holder. Consider verifying alignment with any repo-root LICENSE to avoid mixed licensing.
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-context.mdc (1)
59-60: Confirm whether trailing---is required at EOF.A closing
---at the end can confuse some front-matter parsers. If not required by Cursor rules, remove it.rules/documentation-product-manager-multiuse-toolkit/helper-docs/extra-copy-context.txt (1)
59-60: Confirm whether trailing---at EOF is intended.rules/documentation-product-manager-multiuse-toolkit/alternate-templates/epic-alternate (1)
8-8: Verify reference syntax to product context file.Ensure
@product-context.mdcis the correct handle for Cursor’s include/reference mechanism given the file lives at.cursor/rules/product-context.mdc.
| After answering the question, you are to update the existing @product-context.mdc file by modifying ONLY the following sections while preserving all other content, metadata, and structure: | ||
| ## Problem Statement | ||
| - [LIST AROUND 3 PROBLEMS THAT NEED TO BE SOLVED] | ||
| - [PROBLEM 2] | ||
| - [PROBLEM 3] | ||
| ## Business Field | ||
| - [PROVIDE A 1-4 WORD DESCRIPTION OF THE FIELD] | ||
| - [FIELD 2] | ||
| - [FIELD 3] | ||
| ## Type of Business | ||
| [LIST ONE OF THESE: B2B, B2C, B2B2C, B2G, ETC.] | ||
| ## Target Customers | ||
| - [LIST AROUND 3 CUSTOMERS OF THE PRODUCT] | ||
| - [CUSTOMER 2] | ||
| - [CUSTOMER 3] | ||
| ## Specific Solution | ||
| - [LIST THE MAIN COMPONENTS OF YOUR SOLUTION. BE BRIEF] | ||
| - [SOLUTION PART 2] | ||
| - [SOLUTION PART 3] | ||
| ## Differentiator | ||
| [LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY AND KEEP IT TO 1 OR 2 SENTENCES] | ||
| ## Product Summary | ||
| [SUMMARIZE YOUR PRODUCT IN A SINGLE PARAGRAPH OF AROUND 100-200 WORDS. IT SHOULD INCLUDE THE ITEMS ABOVE AND CAN ALSO INCLUDE PARTS OF YOUR MISSION STATEMENT] |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Guard against overbroad search_replace by defining section anchors.
Without explicit start/end anchors, search_replace risks corrupting unrelated content if section headings repeat. Add concrete boundaries.
After answering the question, you are to update the existing @product-context.mdc file by modifying ONLY the following sections while preserving all other content, metadata, and structure:
+Implementation note for search_replace:
+- Match from the exact H2 heading (e.g., '^## Problem Statement$') up to (but not including) the next line that starts with '## ' or end-of-file.
+- If a section is missing, append it at the end with the exact heading and formatting shown below.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| After answering the question, you are to update the existing @product-context.mdc file by modifying ONLY the following sections while preserving all other content, metadata, and structure: | |
| ## Problem Statement | |
| - [LIST AROUND 3 PROBLEMS THAT NEED TO BE SOLVED] | |
| - [PROBLEM 2] | |
| - [PROBLEM 3] | |
| ## Business Field | |
| - [PROVIDE A 1-4 WORD DESCRIPTION OF THE FIELD] | |
| - [FIELD 2] | |
| - [FIELD 3] | |
| ## Type of Business | |
| [LIST ONE OF THESE: B2B, B2C, B2B2C, B2G, ETC.] | |
| ## Target Customers | |
| - [LIST AROUND 3 CUSTOMERS OF THE PRODUCT] | |
| - [CUSTOMER 2] | |
| - [CUSTOMER 3] | |
| ## Specific Solution | |
| - [LIST THE MAIN COMPONENTS OF YOUR SOLUTION. BE BRIEF] | |
| - [SOLUTION PART 2] | |
| - [SOLUTION PART 3] | |
| ## Differentiator | |
| [LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY AND KEEP IT TO 1 OR 2 SENTENCES] | |
| ## Product Summary | |
| [SUMMARIZE YOUR PRODUCT IN A SINGLE PARAGRAPH OF AROUND 100-200 WORDS. IT SHOULD INCLUDE THE ITEMS ABOVE AND CAN ALSO INCLUDE PARTS OF YOUR MISSION STATEMENT] | |
| After answering the question, you are to update the existing @product-context.mdc file by modifying ONLY the following sections while preserving all other content, metadata, and structure: | |
| Implementation note for search_replace: | |
| - Match from the exact H2 heading (e.g., '^## Problem Statement$') up to (but not including) the next line that starts with '## ' or end-of-file. | |
| - If a section is missing, append it at the end with the exact heading and formatting shown below. | |
| ## Problem Statement | |
| - [LIST AROUND 3 PROBLEMS THAT NEED TO BE SOLVED] | |
| - [PROBLEM 2] | |
| - [PROBLEM 3] | |
| ## Business Field | |
| - [PROVIDE A 1-4 WORD DESCRIPTION OF THE FIELD] | |
| - [FIELD 2] | |
| - [FIELD 3] | |
| ## Type of Business | |
| [LIST ONE OF THESE: B2B, B2C, B2B2C, B2G, ETC.] | |
| ## Target Customers | |
| - [LIST AROUND 3 CUSTOMERS OF THE PRODUCT] | |
| - [CUSTOMER 2] | |
| - [CUSTOMER 3] | |
| ## Specific Solution | |
| - [LIST THE MAIN COMPONENTS OF YOUR SOLUTION. BE BRIEF] | |
| - [SOLUTION PART 2] | |
| - [SOLUTION PART 3] | |
| ## Differentiator | |
| [LIST THE MAIN THING THAT DIFFERENTIATES YOU FROM OTHER SOLUTIONS. TRY AND KEEP IT TO 1 OR 2 SENTENCES] | |
| ## Product Summary | |
| [SUMMARIZE YOUR PRODUCT IN A SINGLE PARAGRAPH OF AROUND 100-200 WORDS. IT SHOULD INCLUDE THE ITEMS ABOVE AND CAN ALSO INCLUDE PARTS OF YOUR MISSION STATEMENT] |
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/context-generator.mdc
around lines 11 to 33, the search_replace step risks altering repeated headings
because there are no unique start/end anchors for each editable section; add
concrete, unique anchors (e.g., <!-- START:ProblemStatement --> ... <!--
END:ProblemStatement -->) immediately before and after each listed section
heading (Problem Statement, Business Field, Type of Business, Target Customers,
Specific Solution, Differentiator, Product Summary), then update only the text
between those anchors per the diff instructions so the replacement targets are
unambiguous and all other content/metadata/structure remains unchanged.
| Then, create a Product Requirements Document, following this comprehensive structure: | ||
|
|
There was a problem hiding this comment.
Incorrect artifact name: this is a Lean Canvas, not a PRD.
Change wording to avoid confusing the workflow.
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/lean-canvas-template.mdc
around lines 10-11, the text currently says "Then, create a Product Requirements
Document, following this comprehensive structure:" but the file is a Lean Canvas
template; change the wording to correctly reference a Lean Canvas (e.g., "Then,
complete the Lean Canvas using the following structure:" or similar) to avoid
confusing the workflow and ensure consistency with the artifact type.
| What would be the best way to reach customers? Provide a single line bullet, with no extra text, for each of these: | ||
| 1. Potential partners to market with (if applicable)? 2. Best marketing method? 3. direct or indirect marketing? | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Ambiguous instruction for Channels; make it clearly three separate one-line bullets.
Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/lean-canvas-template.mdc
around lines 31-33, the "Channels" prompt is ambiguous; replace it with three
distinct one-line bullets (no extra text, no numbering) — 1) a single-line
bullet for "Potential partners to market with (if applicable)", 2) a single-line
bullet for "Best marketing method", and 3) a single-line bullet for "direct or
indirect marketing"; ensure each bullet is exactly one line and contains only
the requested answer.
| Provide a description of the solution and technologies involved. | ||
| First, write 'Solution Technology Overview', followed by up to 4 short sentences describing a general description of what technologies, innovations or methods the solution will use. | ||
| Second, write 'Solution Dependencies', here you will list in up to 4 sentences the potential dependencies for the solution, such as other products, services, or technologies that the solution will use. | ||
| Third, write 'Solution Risks', here you will list in up to 4 sentences the potential risks for the solution, such as technical risks, market risks, or other risks. | ||
| Write only these two sections, with no extra text, in Markdown format. |
There was a problem hiding this comment.
Fix contradiction: you list three subsections but say “two”.
This will confuse the generator.
-Write only these two sections, with no extra text, in Markdown format.
+Write only these three subsections, with no extra text, in Markdown format.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Provide a description of the solution and technologies involved. | |
| First, write 'Solution Technology Overview', followed by up to 4 short sentences describing a general description of what technologies, innovations or methods the solution will use. | |
| Second, write 'Solution Dependencies', here you will list in up to 4 sentences the potential dependencies for the solution, such as other products, services, or technologies that the solution will use. | |
| Third, write 'Solution Risks', here you will list in up to 4 sentences the potential risks for the solution, such as technical risks, market risks, or other risks. | |
| Write only these two sections, with no extra text, in Markdown format. | |
| Provide a description of the solution and technologies involved. | |
| First, write 'Solution Technology Overview', followed by up to 4 short sentences describing a general description of what technologies, innovations or methods the solution will use. | |
| Second, write 'Solution Dependencies', here you will list in up to 4 sentences the potential dependencies for the solution, such as other products, services, or technologies that the solution will use. | |
| Third, write 'Solution Risks', here you will list in up to 4 sentences the potential risks for the solution, such as technical risks, market risks, or other risks. | |
| Write only these three subsections, with no extra text, in Markdown format. |
🤖 Prompt for AI Agents
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/prd-template.mdc
around lines 58 to 62: the instructions say to provide three subsections
(Solution Technology Overview, Solution Dependencies, Solution Risks) but then
state “Write only these two sections,” which is contradictory; update the
sentence to match the three subsections (e.g., change “two” to “three”) and
verify the wording clearly instructs to output only those three sections in
Markdown with no additional text.
| Write the response using Markdown format, with the \\n used above to signify new lines. | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion
Remove literal “\n” requirement; standard Markdown newlines are sufficient.
Forcing literal \n harms readability and downstream rendering.
-Write the response using Markdown format, with the \\n used above to signify new lines.
+Write the response using standard Markdown newlines (no literal “\n” characters).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Write the response using Markdown format, with the \\n used above to signify new lines. | |
| Write the response using standard Markdown newlines (no literal “\n” characters). |
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/prd-template.mdc
around lines 110-111, the template forces literal "\n" sequences for new lines
which harms readability and rendering; remove the requirement for literal "\n"
and replace instructions/examples to use standard Markdown newlines (blank line
or single-line breaks as appropriate), update any sample output and validation
logic in the file to accept normal Markdown line breaks instead of escaped "\n",
and adjust tests/docs that reference the literal "\n" to reflect standard
Markdown formatting.
| Write an Elevator Pitch for the product, that is up to 100 words, using the template from the book 'Crossing the Chasm' by Gordon Moore, and follows the following structure: | ||
| For (Customer) who (Problem), our product (Category) provides (Key Solution). Unlike (Alternative), our product (Differentiator).\ | ||
|
|
||
| Do not change the format of this template by adding any other sentences. |
There was a problem hiding this comment.
Incorrect author name for Crossing the Chasm.
It’s Geoffrey Moore, not Gordon Moore.
-Write an Elevator Pitch for the product, that is up to 100 words, using the template from the book 'Crossing the Chasm' by Gordon Moore, and follows the following structure:
+Write an Elevator Pitch for the product, up to 100 words, using the template from the book 'Crossing the Chasm' by Geoffrey Moore, and follow this structure:📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Write an Elevator Pitch for the product, that is up to 100 words, using the template from the book 'Crossing the Chasm' by Gordon Moore, and follows the following structure: | |
| For (Customer) who (Problem), our product (Category) provides (Key Solution). Unlike (Alternative), our product (Differentiator).\ | |
| Do not change the format of this template by adding any other sentences. | |
| Write an Elevator Pitch for the product, up to 100 words, using the template from the book 'Crossing the Chasm' by Geoffrey Moore, and follow this structure: | |
| For (Customer) who (Problem), our product (Category) provides (Key Solution). Unlike (Alternative), our product (Differentiator).\ | |
| Do not change the format of this template by adding any other sentences. |
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-positioning.mdc
around lines 13 to 16, the author name for "Crossing the Chasm" is incorrect;
replace "Gordon Moore" with the correct author "Geoffrey Moore" while leaving
the rest of the instruction and template unchanged.
|
|
||
| ## RICE estimation | ||
| Perform a RICE scoring analysis of the up-to 10 features you are provided with. | ||
| Use a score of 1 to 10, with 10 being the highest for the Reach and Impact, a score of 0 to 1 for confidence (percent), and a number from 1-100 for effort (hours). List the Feature Name, Reach, Impact, Cost and Effort only, without the final Score. |
There was a problem hiding this comment.
Replace “Cost” with “Confidence” to match the RICE method and your JSON/example.
“Cost” appears twice but the formula and fields use Confidence. This will misguide outputs.
@@
@@Also applies to: 59-59, 65-66
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/RICE-analysis-template.mdc
around line 22 (and also update occurrences at lines 59 and 65-66), the label
"Cost" is incorrect for the RICE method and should be replaced with
"Confidence"; change the field name(s) from "Cost" to "Confidence" so the
template and any examples/JSON align with the RICE formula and avoid misleading
outputs.
| ## Acceptance Criteria | ||
| Follow the User Story by a set of Acceptance Criteria | ||
| You will write 3 separate Acceptance Criteria for this User Story using the Gherkin Framework, which first describes the Scenario, | ||
| then states GIVEN, WHEN, THEN, and AND. Use the AND statement for any of the three operators as needed. | ||
| You will create 3 Acceptance Criteria for the Positive Scenarios, 3 Acceptance Criteria for the Negative Scenarios, | ||
| and 3 Acceptance Criteria for the Outlier Scenarios. | ||
| Think this through, step by step, to come up with all 9 Scenarios and their Acceptance Criteria. | ||
| The Positive Scenarios should be the most common. | ||
| The Negative Scenarios should deal with edge cases where the solution must cope with unexpected user input or challenges. | ||
| The Outlier Scenarios should deal with things that are unexpected, but still possible, and should be tested. | ||
| The Scenarios and Acceptance Criteria should be in the following format: 'SCENARIO : ACCEPTANCE CRITERIA'. | ||
| For each Scenario, write a single Acceptance Criteria. | ||
| Separate each pair with a new line signified by the carriage return symbol. Do not include any other text. | ||
| ### Example response format: | ||
| POSITIVE SCENARIO 1 : ACCEPTANCE CRITERIA 1 | ||
| POSITIVE SCENARIO 2 : ACCEPTANCE CRITERIA 2 | ||
| POSITIVE SCENARIO 3 : ACCEPTANCE CRITERIA 3 | ||
| NEGATIVE SCENARIO 1 : ACCEPTANCE CRITERIA 1 | ||
| NEGATIVE SCENARIO 2 : ACCEPTANCE CRITERIA 2 | ||
| NEGATIVE SCENARIO 3 : ACCEPTANCE CRITERIA 3 | ||
| OUTLIER SCENARIO 1 : ACCEPTANCE CRITERIA 1 | ||
| OUTLIER SCENARIO 2 : ACCEPTANCE CRITERIA 2 | ||
| OUTLIER SCENARIO 3 : ACCEPTANCE CRITERIA 3 No newline at end of file |
There was a problem hiding this comment.
🛠️ Refactor suggestion
Output format conflicts with Gherkin instruction; make the 9 lines truly Gherkin one-liners.
You require GIVEN/WHEN/THEN but also forbid extra text and show non-Gherkin examples. Align by using single-line Gherkin per scenario.
@@
@@Committable suggestion skipped: line range outside the PR's diff.
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-story-template.mdc
around lines 16-38, the Acceptance Criteria section contains contradictory
instructions (it requires Gherkin GIVEN/WHEN/THEN but also forbids extra text
and shows non-Gherkin examples). Update the text to require exactly nine
single-line Gherkin statements (3 Positive, 3 Negative, 3 Outlier), each on its
own line and formatted as "POSITIVE SCENARIO X : GIVEN ... WHEN ... THEN ..."
(or NEGATIVE/OUTLIER), remove the carriage-return/extra-text prohibition that
conflicts with Gherkin, and replace the example block with a concise one-line
Gherkin example for each scenario type so the template unambiguously enforces
one-line Gherkin output.
| ## To use one of these alternate templates, you need to do the following: | ||
| 1. Copy the content of the text to the original file in the .cursor/rules directory | ||
| 2. Ensure that the (new) file still lists at the top the description, and the alwasyApply: false No newline at end of file |
There was a problem hiding this comment.
Fix typo and tighten wording; consider renaming to README.md for better GitHub rendering.
- Typo in “alwasyApply” breaks the documented key.
- Wording + formatting polish.
Apply:
-## To use one of these alternate templates, you need to do the following:
-1. Copy the content of the text to the original file in the .cursor/rules directory
-2. Ensure that the (new) file still lists at the top the description, and the alwasyApply: false
+## How to use an alternate template
+1. Copy the content of this file into the corresponding file in the `.cursor/rules/` directory.
+2. Ensure the new file includes, at the top, the `description:` and `alwaysApply: false` keys.Also consider renaming this file to README.md within this folder for automatic preview on GitHub.
📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## To use one of these alternate templates, you need to do the following: | |
| 1. Copy the content of the text to the original file in the .cursor/rules directory | |
| 2. Ensure that the (new) file still lists at the top the description, and the alwasyApply: false | |
| ## How to use an alternate template | |
| 1. Copy the content of this file into the corresponding file in the `.cursor/rules/` directory. | |
| 2. Ensure the new file includes, at the top, the `description:` and `alwaysApply: false` keys. |
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/alternate-templates/alternate_read.me
around lines 1-3, fix the typo "alwasyApply" to "alwaysApply" so the documented
key works, tighten the wording and formatting of the two steps for clarity (make
step 2 explicit that the new file must include a top-level description and
alwaysApply: false), and optionally rename the file to README.md in this folder
to enable GitHub preview; keep the top of the target rule file unchanged except
for the corrected key and improved wording.
| # Epic Template Instructions | ||
| Before writing the User Stories, ask a short Clarifying Question to the user about what the Time Frame is for the feature, and what the Specific Feature is (do not provide ideas). | ||
| ONLY THEN, continue with the rest of this document. | ||
| Be sure to use the @product-context.mdc data for for initial context. |
There was a problem hiding this comment.
Fix duplicated word (“for for”).
-Be sure to use the @product-context.mdc data for for initial context.
+Be sure to use the @product-context.mdc data for initial context.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Be sure to use the @product-context.mdc data for for initial context. | |
| Be sure to use the @product-context.mdc data for initial context. |
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/alternate-templates/epic-alternate
around line 8, the sentence contains a duplicated word "for for"; remove the
extra "for" so it reads "Be sure to use the @product-context.mdc data for
initial context." and save the file.
There was a problem hiding this comment.
Actionable comments posted: 2
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
rules/documentation-product-manager-multiuse-toolkit/helper-docs/list_of_product_metrics_text_only.txt (1)
1-160: Confirm template linkage and correct bullet formatting
- Verified that
list_of_product_metrics_text_only.txtis included by the KPI template at
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/kpi-revenues-template.mdc:29- Found two inconsistent bullets in the helper docs (
rules/documentation-product-manager-multiuse-toolkit/helper-docs/list_of_product_metrics_text_only.txt):
- Line 21: change “* Cost Per Click (CPC)” to “*Cost Per Click (CPC)”
- Line 22: change “* Click-Through Rate (CTR)” to “*Click-Through Rate (CTR)”
- No occurrences of the deprecated “AAARR” acronym were detected
Please update those two lines to remove the extra space after the asterisk.
♻️ Duplicate comments (3)
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/prd-template.mdc (3)
110-111: Remove literal “\n” requirement; use standard Markdown line breaks.-Write the response using Markdown format, with the \\n used above to signify new lines. +Write the response in Markdown. Use standard line breaks and paragraphs (no literal “\n” characters).
131-131: Relax the “no other formatting” clause to avoid conflicts with headings/bullets.-Write the response in Markdown format, without writing '''markdown''' or anything else, and without using any other formatting. +Write the response in Markdown format. Do not wrap outputs in code fences or specify a language.
58-62: Fix contradiction: you list three subsections but say “two”.Change “two” → “three” so generators output all listed parts.
-Write only these two sections, with no extra text, in Markdown format. +Write only these three subsections, with no extra text, in Markdown format.
🧹 Nitpick comments (22)
rules/documentation-product-manager-multiuse-toolkit/helper-docs/extra-copy-context.txt (4)
54-57: Fix the output path so Cursor writes inside this repo, not repo root.“/product-documents/” is absolute; the repo’s directory is rules/documentation-product-manager-multiuse-toolkit/product-documents/. Update the path to avoid files being created in the wrong place.
- - **Create the file** in the `/product-documents/` directory + - **Create the file** in the `rules/documentation-product-manager-multiuse-toolkit/product-documents/` directory
6-6: Tighten instruction phrasing for clarity.“You are to always consider...” is wordy; keep it direct and professional.
-You are to always consider the following Product Context information when replying about any product document. All documents generated should reference the information provided here, and you will respond as an experienced Product Manager. +Always consider the following Product Context when generating any product document. Reference this information and respond as an experienced Product Manager.
1-4: Consider using .md or .mdc for front matter-aware tooling.This file contains YAML front matter but has a .txt extension. Renaming to .md or .mdc improves editor/rendering support and consistency with the rest of the toolkit.
40-46: Add a Mission Statement field to support dependent templates.Your PRD template references a mission statement; add it here to keep the context self-contained.
## Product Summary [SUMMARIZE YOUR PRODUCT IN A SINGLE PARAGRAPH OF AROUND 100-200 WORDS. IT SHOULD INCLUDE THE ITEMS ABOVE AND CAN ALSO INCLUDE PARTS OF YOUR MISSION STATEMENT] +## Mission Statement +[WRITE A ONE-SENTENCE MISSION STATEMENT TO GUIDE PRIORITIZATION AND TRADEOFFS]rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.md (3)
12-12: Make the 1‑liner concise and user-focused.Reduce redundancy (“coding IDE”, “use it instead”) and avoid title case mid‑sentence.
-An extension for your coding IDE that allows you to use it instead for generating Documents for Product Managers using its built-in AI generators +An IDE extension that generates Product Management documents using built‑in AI.
38-38: Replace buzzwords with a concrete, defensible differentiator.Avoid “seamlessly streamline”/“cutting‑edge”. State what’s uniquely better.
-Seamlessly streamline your document generation process within your coding IDE using cutting-edge AI technology, empowering your product management workflow like never before. +Native in‑IDE templates tuned for PM workflows (PRDs, epics, OKRs) with context‑aware prompts that auto‑pull product context—reducing doc prep time by 50%+.
33-35: Minor wording cleanup (“coding IDE” → “IDE”).-- Integrated AI-powered document generation within coding IDE for seamless workflow efficiency. +- Integrated AI-powered document generation within the IDE for workflow efficiency.rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/prd-template.mdc (3)
6-9: Ensure the agent waits for the user’s answer before generating the PRD.Be explicit to stop after the clarifying question.
-Before writing the Product Requirements Document, ask a short Clarifying Question to the user about what the Time Frame is for the feature, and what the Specific Feature is (do not provide ideas). -ONLY THEN, continue with the rest of this document. +Before writing the Product Requirements Document, ask one short clarifying question about the Time Frame and the Specific Feature (do not provide ideas). +Stop and wait for the user’s answer. ONLY AFTER the user responds, continue with the rest of this document.
14-16: Avoid unverifiable market size claims; require assumptions or citations.-Then, describe the Market Opportunity for this problem. What is the market size for this problem and field, as found in existing market reports or similar report? -Keep the description of the Market Opportunity as a single paragraph that is less than 160 words. +Then, describe the Market Opportunity. If citing market size, include a source; if sources are unavailable, state explicit assumptions (e.g., TAM/SAM/SOM estimates) and avoid unverifiable numbers. Keep it to a single paragraph under 160 words.
101-103: Normalize press-release labels.-TITLE:string -SUBTITLE: Subtitle summarizing the solution in a short sentence -'New York, NY - in another: XX mo/wk/yr +Title: <headline> +Subtitle: <short sentence summarizing the solution> +'New York, NY — <Month DD, YYYY>rules/documentation-product-manager-multiuse-toolkit/helper-docs/list_of_product_metrics_text_only.txt (12)
9-11: Remove duplicated phrase in Landing Page Conversion Rate definition.Redundant “on a specific landing page” is repeated.
-The percentage of visitors who take a desired action on a specific landing page, like signing up or starting a trial, on a specific landing page. +The percentage of visitors who take a desired action on a specific landing page (e.g., sign-up or trial start).
21-23: Normalize bullet formatting and add missing CPC/CTR definitions.Two bullets have a leading space after the asterisk and lack definitions.
-* Cost Per Click (CPC) -* Click-Through Rate (CTR) +*Cost Per Click (CPC) +The average amount paid per ad click. CPC = Ad Spend / Clicks. + +*Click-Through Rate (CTR) +The percentage of impressions that result in a click. CTR = Clicks / Impressions.
26-29: Fix fragment in TTV paragraph.Reads as a sentence fragment across lines.
-The time it takes for a user to experience the core benefits of your product after starting to use it. A shorter TTV leads to higher user satisfaction, engagement, and retention. In a product-led growth, -optimizing TTV is crucial to ensure users quickly understand the value your product delivers. +The time it takes for a user to experience the core benefits of your product after starting to use it. A shorter TTV leads to higher user satisfaction, engagement, and retention. In product-led growth, optimizing TTV is crucial so users quickly understand the value your product delivers.
32-33: Add definition for Onboarding Drop-off Rate.The metric is listed but not defined.
*Onboarding Drop-off Rate +The percentage of users who start onboarding but do not complete it.
43-45: Add concise definitions for PQA and PQL.Listed without explanations; quick definitions aid consistency with other bullets.
*Product Qualified Accounts (PQA) +Accounts that meet product-usage thresholds at the account/org level indicating buying intent (e.g., seats created, key feature adoption). *Product Qualified Leads (PQL) +Individual users who reach product-based activation thresholds and demonstrate purchase intent (e.g., completing core actions, hitting usage limits).
87-88: Add definition for Cohort Retention Analysis.Currently just a heading.
*Cohort Retention Analysis +Retention measured across user cohorts that started in the same period (e.g., signup month), tracking active/retained users over time by cohort.
92-95: Clarify units in “Customer Lifetime = 1/Churn Rate”.Formula assumes churn measured for the same period as lifetime; state it to avoid misuse.
Customer Lifetime = 1/Churn Rate +Note: Use consistent periods (e.g., monthly churn → lifetime in months).
107-110: Optionally note profit-level CLV.Many teams include gross margin when using CLV for profitability.
CLV = Customer Lifetime * ARPA +For profit-level CLV, include margin: CLV = Customer Lifetime * ARPA * Gross Margin.
114-117: Add definition for ARR.ARR is listed without an explanation.
*Annual Recurring Revenue (ARR) +The annualized value of recurring subscriptions. ARR = MRR * 12.
121-124: Add definition for Net Revenue Retention (NRR).Listed without an explanation.
*Net Revenue Retention +Recurring revenue from the prior-period cohort at period end (including expansions/reactivations, excluding new logos) divided by starting recurring revenue.
128-129: Add definition for Gross Margin.Listed without an explanation.
*Gross Margin +(Revenue - Cost of Goods Sold) / Revenue.
1-160: Consistency pass: bullets and style.Minor style nits remain (e.g., ensure all bullets use “*Metric” with no leading space, metric name on one line, definition on next). Consider a quick sweep after applying above changes.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
💡 Knowledge Base configuration:
- MCP integration is disabled by default for public repositories
- Jira integration is disabled by default for public repositories
- Linear integration is disabled by default for public repositories
You can enable these sources in your CodeRabbit configuration.
📒 Files selected for processing (15)
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/RICE-analysis-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/kpi-revenues-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/lean-canvas-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/persona-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/prd-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-context.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-positioning.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/risk-analysis-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/roadmap-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-journey-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-story-template.mdc(1 hunks)rules/documentation-product-manager-multiuse-toolkit/alternate-templates/epic-alternate(1 hunks)rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.md(1 hunks)rules/documentation-product-manager-multiuse-toolkit/helper-docs/extra-copy-context.txt(1 hunks)rules/documentation-product-manager-multiuse-toolkit/helper-docs/list_of_product_metrics_text_only.txt(1 hunks)
✅ Files skipped from review due to trivial changes (1)
- rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/RICE-analysis-template.mdc
🚧 Files skipped from review as they are similar to previous changes (10)
- rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-context.mdc
- rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/roadmap-template.mdc
- rules/documentation-product-manager-multiuse-toolkit/alternate-templates/epic-alternate
- rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-story-template.mdc
- rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/kpi-revenues-template.mdc
- rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/persona-template.mdc
- rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/product-positioning.mdc
- rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/user-journey-template.mdc
- rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/lean-canvas-template.mdc
- rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/risk-analysis-template.mdc
🧰 Additional context used
📓 Path-based instructions (2)
**/*.md
📄 CodeRabbit inference engine (.cursorrules)
Always use Markdown for documentation and README files
Files:
rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.md
**/*.{md,cursorrules}
📄 CodeRabbit inference engine (.cursorrules)
**/*.{md,cursorrules}: Use clear and concise language in all documentation and .cursorrules files
When adding examples or explanations, focus on practical use cases for Cursor AI users
Files:
rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.md
🪛 LanguageTool
rules/documentation-product-manager-multiuse-toolkit/helper-docs/example-product-context.md
[grammar] ~5-~5: There might be a mistake here.
Context: ...ger Document Generator - Product Context You are to always consider the following...
(QB_NEW_EN)
[grammar] ~8-~8: There might be a mistake here.
Context: ...Product Manager. ## Product Information Product Name: AgileGen ## 1-line Prod...
(QB_NEW_EN)
[grammar] ~14-~14: There might be a mistake here.
Context: ...t-in AI generators ## Problem Statement - Product Managers face time-consuming man...
(QB_NEW_EN)
[grammar] ~15-~15: There might be a mistake here.
Context: ... creation processes for project details. - Inefficient integration between coding I...
(QB_NEW_EN)
[grammar] ~19-~19: There might be a mistake here.
Context: ... documentation tasks. ## Business Field - Productivity Tools - SaaS Technology - P...
(QB_NEW_EN)
[grammar] ~20-~20: There might be a mistake here.
Context: ... ## Business Field - Productivity Tools - SaaS Technology - Product Management Sof...
(QB_NEW_EN)
[grammar] ~21-~21: There might be a mistake here.
Context: ...d - Productivity Tools - SaaS Technology - Product Management Software ## Type of ...
(QB_NEW_EN)
[grammar] ~24-~24: There might be a mistake here.
Context: ...Management Software ## Type of Business B2B ## Target Customers - Tech-savvy Pr...
(QB_NEW_EN)
[grammar] ~27-~27: There might be a mistake here.
Context: ...ype of Business B2B ## Target Customers - Tech-savvy Product Managers - Agile Soft...
(QB_NEW_EN)
[grammar] ~28-~28: There might be a mistake here.
Context: ... Customers - Tech-savvy Product Managers - Agile Software Development Teams - IT Pr...
(QB_NEW_EN)
[grammar] ~29-~29: There might be a mistake here.
Context: ...agers - Agile Software Development Teams - IT Project Management Professionals ## ...
(QB_NEW_EN)
[grammar] ~34-~34: There might be a mistake here.
Context: ...n for PMs, developers, and stakeholders through unified toolset. - Customization option...
(QB_NEW_EN)
[grammar] ~34-~34: There might be a mistake here.
Context: ...nd stakeholders through unified toolset. - Customization options tailored for vario...
(QB_NEW_EN)
[grammar] ~37-~37: There might be a mistake here.
Context: ...odologies and styles. ## Differentiator Seamlessly streamline your document gene...
(QB_NEW_EN)
[grammar] ~40-~40: There might be a mistake here.
Context: ...w like never before. ## Product Summary Our innovative product addresses the tim...
(QB_NEW_EN)
[grammar] ~47-~47: There might be a mistake here.
Context: ...tion ## Writing Style and File Format - Use clear, concise language - Avoid tech...
(QB_NEW_EN)
[grammar] ~55-~55: There might be a mistake here.
Context: ...ectory - Use the naming convention: [TYPE]-[description]-[version].md - Write file: Save the generated content...
(QB_NEW_EN)
rules/documentation-product-manager-multiuse-toolkit/helper-docs/extra-copy-context.txt
[grammar] ~5-~5: There might be a mistake here.
Context: ...ger Document Generator - Product Context You are to always consider the following...
(QB_NEW_EN)
[grammar] ~8-~8: There might be a mistake here.
Context: ...Product Manager. ## Product Information Product Name: [GIVE IT A SHORT NAME] ...
(QB_NEW_EN)
[grammar] ~11-~11: There might be a mistake here.
Context: ...ORT NAME] ## 1-line Product Description [A 1-LINER DESCRIPTION OF THE PRODUCT TH...
(QB_NEW_EN)
[grammar] ~12-~12: Ensure spelling is correct
Context: ...ME] ## 1-line Product Description [A 1-LINER DESCRIPTION OF THE PRODUCT THAT GENERAL...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
[grammar] ~14-~14: There might be a mistake here.
Context: ...IZES THE SOLUTION] ## Problem Statement - [LIST AROUND 3 PROBLEMS THAT NEED TO BE ...
(QB_NEW_EN)
[grammar] ~15-~15: There might be a mistake here.
Context: ...ROUND 3 PROBLEMS THAT NEED TO BE SOLVED] - [PROBLEM 2] - [PROBLEM 3] ## Business F...
(QB_NEW_EN)
[grammar] ~16-~16: There might be a mistake here.
Context: ...MS THAT NEED TO BE SOLVED] - [PROBLEM 2] - [PROBLEM 3] ## Business Field - [PROVID...
(QB_NEW_EN)
[grammar] ~19-~19: There might be a mistake here.
Context: ...BLEM 2] - [PROBLEM 3] ## Business Field - [PROVIDE A 1-4 WORD DESCRIPTION OF THE F...
(QB_NEW_EN)
[grammar] ~20-~20: There might be a mistake here.
Context: ...IDE A 1-4 WORD DESCRIPTION OF THE FIELD] - [FIELD 2] - [FIELD 3] ## Type of Busine...
(QB_NEW_EN)
[grammar] ~21-~21: There might be a mistake here.
Context: ...RD DESCRIPTION OF THE FIELD] - [FIELD 2] - [FIELD 3] ## Type of Business [LIST ONE...
(QB_NEW_EN)
[grammar] ~24-~24: There might be a mistake here.
Context: ...IELD 2] - [FIELD 3] ## Type of Business [LIST ONE OF THESE: B2B, B2C, B2B2C, B2G...
(QB_NEW_EN)
[grammar] ~27-~27: There might be a mistake here.
Context: ..., B2B2C, B2G, ETC.] ## Target Customers - [LIST AROUND 3 CUSTOMERS OF THE PRODUCT]...
(QB_NEW_EN)
[grammar] ~28-~28: There might be a mistake here.
Context: ...[LIST AROUND 3 CUSTOMERS OF THE PRODUCT] - [CUSTOMER 2] - [CUSTOMER 3] ## Specific...
(QB_NEW_EN)
[grammar] ~29-~29: There might be a mistake here.
Context: ...CUSTOMERS OF THE PRODUCT] - [CUSTOMER 2] - [CUSTOMER 3] ## Specific Solution - [LI...
(QB_NEW_EN)
[grammar] ~33-~33: There might be a mistake here.
Context: ...N COMPONENTS OF YOUR SOLUTION. BE BRIEF] - [SOLUTION PART 2] - [SOLUTION PART 3] #...
(QB_NEW_EN)
[grammar] ~34-~34: There might be a mistake here.
Context: ... SOLUTION. BE BRIEF] - [SOLUTION PART 2] - [SOLUTION PART 3] ## Differentiator [LI...
(QB_NEW_EN)
[grammar] ~40-~40: There might be a mistake here.
Context: ...NE OR TWO SENTENCES] ## Product Summary [SUMMARIZE YOUR PRODUCT IN A SINGLE PARA...
(QB_NEW_EN)
[grammar] ~47-~47: There might be a mistake here.
Context: ...tion ## Writing Style and File Format - Use clear, concise language - Avoid tech...
(QB_NEW_EN)
[grammar] ~55-~55: There might be a mistake here.
Context: ...ectory - Use the naming convention: [TYPE]-[description]-[version].md - Write file: Save the generated content...
(QB_NEW_EN)
rules/documentation-product-manager-multiuse-toolkit/helper-docs/list_of_product_metrics_text_only.txt
[grammar] ~12-~12: There might be a mistake here.
Context: ... *Cost of Customer Acquisition (CAC) The cost of acquiring a new customer thr...
(QB_NEW_EN)
[grammar] ~21-~21: There might be a mistake here.
Context: ...s, or paid ads. * Cost Per Click (CPC) * Click-Through Rate (CTR) **Activation M...
(QB_NEW_EN)
[grammar] ~31-~31: There might be a mistake here.
Context: ...ete the onboarding process successfully. *Onboarding Drop-off Rate *User Activat...
(QB_NEW_EN)
[grammar] ~43-~43: There might be a mistake here.
Context: ...cess. *Product Qualified Accounts (PQA) *Product Qualified Leads (PQL) **Engage...
(QB_NEW_EN)
[grammar] ~115-~115: There might be a mistake here.
Context: ...iption-based product on a monthly basis. *Annual Recurring Revenue (ARR) *Expans...
(QB_NEW_EN)
[grammar] ~122-~122: There might be a mistake here.
Context: ...-renewals within a specific time period. *Net Revenue Retention *Average Contrac...
(QB_NEW_EN)
[grammar] ~135-~135: There might be a mistake here.
Context: ...d as a ratio. *Customer Referral Rate The percentage of customers who refer ot...
(QB_NEW_EN)
| ## 11. Release Details | ||
| Considering the product being released, think of the Operational Requirements for releasing the product. This includes topics such as: Distribution, Support, Regulation, Safety, Training, 3rd Party Services, Logistics and Security. | ||
| Consider 3 different categories that are relevant for the product, and write for each of the 3 a single short sentence with up to 15 words each. Return this as Markdown, with each category being a new line, and each requirement being a dash followed by a space and then the requirement. | ||
| For example: | ||
| ### Category1 | ||
| - Requirement1 | ||
| - Requirement2 | ||
| - Requirement3 | ||
|
|
||
| ### Category2 | ||
| - Requirement1 | ||
| - Requirement2 | ||
| - Requirement3 | ||
|
|
||
| ### Category3 | ||
| - Requirement1 | ||
| - Requirement2 | ||
| - Requirement3 | ||
|
|
There was a problem hiding this comment.
Clarify Release Details: bullets vs. “single sentence” conflict.
The text asks for one sentence per category but the example shows three bullets. Align instructions to require three bullet requirements per category, each ≤15 words.
-Consider 3 different categories that are relevant for the product, and write for each of the 3 a single short sentence with up to 15 words each. Return this as Markdown, with each category being a new line, and each requirement being a dash followed by a space and then the requirement.
+Consider 3 relevant categories. For each category, list 3 requirements as bullets, each a single short sentence (≤ 15 words). Return this as Markdown with each category as a heading and its 3 bullet requirements below.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ## 11. Release Details | |
| Considering the product being released, think of the Operational Requirements for releasing the product. This includes topics such as: Distribution, Support, Regulation, Safety, Training, 3rd Party Services, Logistics and Security. | |
| Consider 3 different categories that are relevant for the product, and write for each of the 3 a single short sentence with up to 15 words each. Return this as Markdown, with each category being a new line, and each requirement being a dash followed by a space and then the requirement. | |
| For example: | |
| ### Category1 | |
| - Requirement1 | |
| - Requirement2 | |
| - Requirement3 | |
| ### Category2 | |
| - Requirement1 | |
| - Requirement2 | |
| - Requirement3 | |
| ### Category3 | |
| - Requirement1 | |
| - Requirement2 | |
| - Requirement3 | |
| ## 11. Release Details | |
| Considering the product being released, think of the Operational Requirements for releasing the product. This includes topics such as: Distribution, Support, Regulation, Safety, Training, 3rd Party Services, Logistics and Security. | |
| Consider 3 relevant categories. For each category, list 3 requirements as bullets, each a single short sentence (≤ 15 words). Return this as Markdown with each category as a heading and its 3 bullet requirements below. | |
| For example: | |
| ### Category1 | |
| - Requirement1 | |
| - Requirement2 | |
| - Requirement3 | |
| ### Category2 | |
| - Requirement1 | |
| - Requirement2 | |
| - Requirement3 | |
| ### Category3 | |
| - Requirement1 | |
| - Requirement2 | |
| - Requirement3 |
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/prd-template.mdc
around lines 79 to 97, the "Release Details" section conflicts by asking for a
single sentence per category but providing an example with three bullet
requirements; update the instructions to require three bulleted requirements per
category (each ≤15 words) and adjust the example text to match this: explicitly
state "For each of 3 categories, provide three bullets (each a single sentence
up to 15 words)" and modify the example to show three bullets under each
category.
| *Engagement Metrics | ||
| In the AAARR (Acquisition, Activation, Retention, Revenue, Referral) framework, Engagement Metrics can be considered part of the Activation and Retention. | ||
| I presented them as a separate category to emphasize the distinct metrics focusing on user interaction with the product. | ||
|
|
There was a problem hiding this comment.
Correct framework acronym: AARRR (not “AAARR”).
Standard “Pirate Metrics” acronym is AARRR: Acquisition, Activation, Retention, Revenue, Referral.
-In the AAARR (Acquisition, Activation, Retention, Revenue, Referral) framework, Engagement Metrics can be considered part of the Activation and Retention.
+In the AARRR (Acquisition, Activation, Retention, Revenue, Referral) framework, engagement metrics can be considered part of Activation and Retention.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| *Engagement Metrics | |
| In the AAARR (Acquisition, Activation, Retention, Revenue, Referral) framework, Engagement Metrics can be considered part of the Activation and Retention. | |
| I presented them as a separate category to emphasize the distinct metrics focusing on user interaction with the product. | |
| *Engagement Metrics | |
| In the AARRR (Acquisition, Activation, Retention, Revenue, Referral) framework, engagement metrics can be considered part of Activation and Retention. | |
| I presented them as a separate category to emphasize the distinct metrics focusing on user interaction with the product. |
🤖 Prompt for AI Agents
In
rules/documentation-product-manager-multiuse-toolkit/helper-docs/list_of_product_metrics_text_only.txt
around lines 151 to 154, the framework acronym is incorrectly written as
“AAARR”; update it to the correct standard “AARRR” everywhere in that sentence
(and any nearby occurrences) so it reads “AARRR (Acquisition, Activation,
Retention, Revenue, Referral)”, leaving the rest of the explanation about
Engagement Metrics unchanged.
2 participants
This isn't just a .cursorrules file, as the new version of Cursor now has a different way to do this. Instead, I created an entire built-in tool that helps you generate different documents using cursor rules. Instructions are included (including a video link). I put the entire thing in its own directory, including the instructions.
Summary by CodeRabbit
New Features
Documentation
Chores