Added a full set of rules for Product Managers

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/RICE-analysis-template.mdc

@@ -0,0 +1,68 @@
+---
+description: RICE prioritization of features using the Reach, Impact, Confidence and Effort evaluation method
+alwaysApply: false
+---
+# RICE Prioritization Template Instructions
+You will be prioritizing a list of features as an experience Product Manager using the RICE method, which calculates a Score based off of 4 metrics that you will provide values for.
+
+## Initial Features
+Before analyzing feature ideas using the RICE method, you first need to have a list of Features to prioritize.
+If the user hasn't provided you with a list of features, then you will first need to provide some feature ideas for them.
+Be sure to use the @product-context.mdc data for for initial context.
+Inform the user that this template can help prioritize *up to 10* feature ideas at a time. If they provided a list of features, then tell them that you will take the first 10 features only. Or, provide a list of 10 feature ideas to be developed for the product. Provide the list in a numbered format.
+
+## Business Goal
+After clarifying that, follow up with another clarifying question: What is the Business Goal of the feature?
+Provide 3 ideas, based on the Product Context. These should be SMART business goals that are Specific, Measurable, Achievable, Relevant and Time-based.
+
+After that clarifying question, perform the RICE prioritization as follows:
+
+## 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. 
+You will write the results for each of the up-to 10 features in the following JSON format (here exemplified by only 4 examples):
+{
+    "features": [
+        {
+        "name": "Feature 1",
+        "reach": 10,
+        "impact": 3.5,
+        "confidence": 0.8,
+        "effort": 20
+        },
+        {
+        "name": "Feature 2",
+        "reach": 5,
+        "impact": 4.0,
+        "confidence": 0.7,
+        "effort": 10
+        },
+        {
+        "name": "Feature 3",
+        "reach": 8,
+        "impact": 2.0,
+        "confidence": 0.9,
+        "effort": 25
+        },
+        {
+        "name": "Feature 4",
+        "reach": 7,
+        "impact": 3.8,
+        "confidence": 0.6,
+        "effort": 15
+        },
+    ]
+}
+For all of the up-to 10 features. Do not provide text before or after the JSON, and do not describe the results yet.
+
+## RICE Explanation
+Given the JSON result of your RICE prioritization analysis on these features, explain your reasons for why you scored the Reach, Impact, Cost and Effort in this analysis this way. 
+Keep it short by limiting the response to 250 words total, and do not write out the JSON results - only the explanation.
+
+
+## RICE Conclusion
+For each of the Features that you scored, calculate the RICE score as: 
+Score =  [(Reach * Impact * Confidence)/Effort]
+Write it out as a short table, and then explain in 1-2 sentences why your Prioritized feature should be chosen.
+
+

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/context-generator.mdc

@@ -0,0 +1,43 @@
+---
+alwaysApply: false
+---
+## Tool to help generate Product Context
+The goal of this tool is to help generate and update the data in the @product-context.mdc file.
+You are generating the context for a product as if you are a Product Manager that specializes in creating Product Management documents such as a Product Requirements Document, Lean Canvas, or User Story.
+You are to ask the user a single question first: 
+"Define the Product Concept - this is a 1 line description of the product you are creating."
+(unless the user already provides this information when called)
+
+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]
+
+**IMPORTANT**: You must preserve the following elements exactly as they are:
+- The YAML frontmatter (--- alwaysApply: true ---)
+- The "Product Information" and "1-line Product Description" sections
+- The "Optional - Additional Information" section
+- The "Writing Style and File Format" section
+- The "AI File Creation Instructions" section
+- All formatting, spacing, and structure
+
+Use the search_replace tool to update only the specific sections mentioned above, ensuring you maintain the exact formatting and indentation of the original file.

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/epic-generator-template.mdc

@@ -0,0 +1,100 @@
+---
+description: Comprehensive Epic Plan Generator
+alwaysApply: false
+---
+# Epic Plan Generator Template
+Use @product-context.mdc for product details. Generate a complete Epic plan document for new feature sets or product initiatives following this exact structure:
+
+## Document Header
+```
+# Epic Plan: [Feature Set/Initiative Name]
+## [Brief description of the feature set or initiative]
+
+**Product:** [Product Name]
+**Feature Set:** [Feature Set Name]
+**Document Type:** Epic Plan
+**Created:** [Current Month Year]
+**Version:** 1.0
+```
+
+## Executive Summary
+- One paragraph summarizing the feature set's impact on product and users
+- Reference how it serves target customers and aligns with product differentiator
+
+## Strategic Context
+### Strategic Goals (3-4 bullets starting with action verbs, adjust based on scope)
+- **Address [specific user need/pain point]:** [feature solution approach]
+- **Enhance [product capability]:** [improvement strategy]
+- **Enable [new user behavior/workflow]:** [enablement approach]
+- **Improve [existing metric/experience]:** [optimization goal]
+
+### Success Metrics (3-4 key metrics based on feature scope)
+- **Feature Adoption:** [usage and engagement targets]
+- **User Experience:** [performance and satisfaction targets]
+- **Business Impact:** [revenue, retention, or efficiency targets]
+- **Technical Performance:** [reliability and performance targets]
+
+## Epic Structure (3-4 Core Themes based on feature complexity)
+Generate 3-4 Epic themes with emojis, each containing 2-4 sub-epics based on scope:
+
+### 🏗️ **EPIC 1: Core Functionality & Foundation**
+*Theme: Build essential feature capabilities*
+
+### 🎨 **EPIC 2: User Experience & Interface** 
+*Theme: Design intuitive user interactions*
+
+### 🔗 **EPIC 3: Integration & Compatibility**
+*Theme: Connect with existing systems and platforms*
+
+### 📈 **EPIC 4: Enhancement & Optimization** *(Optional for large feature sets)*
+*Theme: Advanced features and performance optimization*
+
+## Sub-Epic Format (Adjust quantity based on feature scope: 6-16 total sub-epics)
+```
+#### **Epic X.Y: [Feature Component Name]**
+- **User Story:** As a [user type], I want [action] so I can [outcome]
+- **Key Features:**
+  - [3-4 bullet points of main capabilities]
+- **Acceptance Criteria:**
+  - [2-3 measurable criteria with specific targets]
+- **Dependencies:** [Epic references or "None"]
+- **Effort:** [X weeks/sprints]
+- **Priority:** P0 (Critical) / P1 (High) / P2 (Medium)
+```
+
+## Implementation Timeline (Adjust timeframe based on feature scope)
+### Phase 1: Foundation *(Weeks 1-X or Sprints 1-X)*
+### Phase 2: Core Features *(Weeks X-Y or Sprints X-Y)*
+### Phase 3: Integration *(Weeks Y-Z or Sprints Y-Z)*
+### Phase 4: Enhancement *(Optional - for large feature sets)*
+
+## Risk Management
+### High-Risk Dependencies (2-3 items based on feature complexity)
+### Mitigation Strategies (2-3 items)
+
+## Resource Requirements
+### Development Team (3-6 roles based on feature scope)
+### Infrastructure/Tools (2-4 items as needed)
+
+## Success Criteria
+### Initial Release (End of Phase 2) - 2-3 bullets
+### Feature Complete (End of Phase 3) - 2-3 bullets  
+### Optimization Complete (End of Phase 4, if applicable) - 2-3 bullets
+
+## Priority Guidelines
+- P0: Core functionality, security, basic user flow
+- P1: Enhanced features, performance, major platforms
+- P2: Customization, advanced features, ecosystem
+
+## Effort Estimation (Adjust based on feature complexity)
+- Core functionality epics: 2-8 weeks each
+- User experience epics: 2-6 weeks each
+- Integration epics: 3-8 weeks each
+- Enhancement epics: 2-4 weeks each
+
+## Scope Guidelines
+- **Small Feature Set:** 3 Epics, 6-8 Sub-epics, 2-3 months
+- **Medium Feature Set:** 3-4 Epics, 9-12 Sub-epics, 3-6 months
+- **Large Feature Set:** 4 Epics, 12-16 Sub-epics, 6-12 months
+
+Save as: `EPIC-PLAN-[feature-set-name-lowercase]-[year].md`

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/kpi-revenues-template.mdc

@@ -0,0 +1,67 @@
+---
+description: Connect your KPIs to business and revenue goals, CFO communications, North Star Metrics
+alwaysApply: false
+---
+# KPI to Revenues Connector Instructions
+Before writing the KPI-Revenue Connector, 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. 
+**Also, advise the user that it may be better to manually switch to Gemini 2.5, which has a larger context window for this**
+
+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:
+
+## 1. Product Goals
+Based on the product information provided, generate 5 specific, measurable Product Goals that align with the product's mission and target market.
+The Product Goal expresses customer pain points, needs and desires. 
+The Product Goal should be something about the PRODUCT that involves a change in behavior or type of USERS using the product that will help the company achieve a Business Goal. 
+Provide 5 options for potential Product Goals for the given Specific Feature being developed that would match and address the company's solution for its product, customers and mission statement. 
+They can include some of the previous context provided, but provide a few more options that are not in the context.
+Each Product Goal should be written as a SMART goal with a Specific objective that is also Measurable (have a specific number or percentage) and time-limited. 
+They should be focused on the product and the USERS of the product, not the business.
+Write the goals as a list of NUMBERED bullets.
+
+**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!**
+
+## 2. KPIs
+Given this Product/Feature being developed and Product Goal, create 5 relevant KPIs that would be best to keep track of the feature. Each KPI should be up to 6 words. 
+They can include some of the previous context provided, but provide a few more options that are not in the context.
+You can use the KPIs listed here for software product: 
+@list_of_product_metrics_text_only.txt
+Write a list of KPIs as separate bullets.
+
+## 3. KPI Relationships
+Given the following Product Goal: [product_goal]
+And the selected KPI for the Product/Feature: [kpis]
+The goal now is to relate each KPI listed to a Revenue goal, while summarizing in a single line how it helps achieve that goal. 
+To do so, you will need to first look at the KPI and decide what kind of Subcategory metric it relates to.
+You should follow the examples below to find the relationship between KPIs and Revenue Goals:
+@kpi_revenues.txt
+
+Once you have found the relationship between the KPI and the Revenue Goal, we are looking to make a list of the following:
+1. Revenue Goal name (from the list)
+2. Short sentence Explanation for how the Product goal and KPI are related to the Revenue Goal
+
+For each of the KPIs, write the 
+- KPI
+- Revenue Goal
+- Explanation
+
+
+## 4. North Star Metric
+Given the [product_goal] you wrote, the selected KPIs: [selected_kpis] and the KPI Relationships to Revenue [kpi_rel_prompt_text]:
+
+Define a single North Star Metric that best captures the core value our product delivers to customers.
+This metric should:
+1. Be directly tied to customer value
+2. Be measurable
+3. Be actionable
+4. Be predictive of long-term success
+
+In up to 60 words, briefly rephrase all of this information into the following template (you can change the words to fit the product and goals): 
+For (target customer) with this (problem), we propose (solution). Our primary goal is (Product goal). We will know we're successful when (main KPI metric).
+
+Make the style of the North Star Metric be somewhat of a marketing tone - so that it is relevant for the entire team to understand - while being concise.
+Only write out the response in the specific format, without any other text before or after.
+
+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]

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/lean-canvas-template.mdc

@@ -0,0 +1,42 @@
+---
+description: Lean Canvas, Product Strategy, Lean Startup Canvas
+alwaysApply: false
+---
+# Lean Canvas Template Instructions
+
+Be sure to use the @product-context.mdc data for initial context.
+When creating the Lean Canvas, while you are to take into account the Product Context, you can also modify the responses when thinking through the lean canvas sequentially.
+
+Then, create a Product Requirements Document, following this comprehensive structure:
+
+## 1. Problem 
+Rethink the top 3 Problems that this product will be solving, for the Lean Canvas. You can take the existing list of problems, or come up with new ones. Write the 3 top Problems in a list of short, 1-line Bullets, with no extra text.
+
+## 2. Solution
+Given the Problems and listed Solution, Rethink the top 3 aspects of our Solution for this problem, for the Lean Canvas. The Solutions should be based on what was given, but summarize them in a list of short, 1-line Bullets, with no extra text.
+
+## 3. Unfair Advantage
+What would you describe as being our Unfair Advantage, given the Solution and Differentiator in this space.
+Provide a short list of 3 Unfair Advantage bullets in 1-line each, with no extra text.
+
+## 4. Key Metrics
+Give 3 bullets describing how best to measure success of the solution given for this problem using Key Metrics.
+Each bullet should be only 1 line, with no extra text.
+
+## 5. Customer Segment
+Rethink the top 3 potential Target Customers for this product, for the Lean Canvas. 
+The Customers should be based on what was given, but summarize them in a list of short, 1-line Bullets, with no extra text.
+
+## 6. Channels
+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?
+
+## 7. Unique Value Proposition
+Given the previous information, create a 1-line Unique Value Proposition (UVP) for the product, with no extra text.
+
+## 8. Revenue
+Given the previous information, write the best revenue model for this business in 1 line, with no extra text.
+Follow it with another 1-line with a second-best revenue model.
+
+## 9. Costs
+Given the previous information, write 4 bullets for the main costs of the product development. Each bullet should be 1 line, with no extra text.

rules/documentation-product-manager-multiuse-toolkit/.cursor/rules/persona-template.mdc

@@ -0,0 +1,27 @@
+---
+description: Defining 2 User Personas for the product: Regular and Skeptical Personas
+alwaysApply: false
+---
+# Persona Template Instructions
+
+You will write 2 User Personas for this product: An ideal one and a skeptical one.
+
+First write an ideal User Persona for this product. Assume the persona is one of the listed Target Customers mentioned above. 
+For the persona, make sure to list: 
+1. Their name 
+2. Overview
+3. Goals
+4. Behaviors
+5. Pains 
+6. Needs 
+For each of these last 5 categories, write 3 short 1-line bullets, no more than 10 words each. 
+
+Next, write a skeptical User Persona for this product. Assume the persona is one of the listed target customers mentioned above,
+however, assume that it is someone who is not at all likely to like your product, as they are skeptical, 
+and it doesn't fit their needs and pains. Make sure to list: 
+1. Their name 2. Overview, 3. Goals, 4. Behaviors, 5. Pains and 6. Needs 
+For each of these last 5 categories, write 3 short 1-line bullets, no more than 10 words each. 
+
+Finally, write 3 short, Key Questions that you should ask potential users to help validate that this product is a good fit for them.
+
+Write the response in Markdown format, without writing '''markdown''' or anything else, and without using any other formatting.