Skip to content

Add Product Sense Coach prompt#1079

Open
viliawang-pm wants to merge 1 commit intof:mainfrom
viliawang-pm:add-product-sense-coach
Open

Add Product Sense Coach prompt#1079
viliawang-pm wants to merge 1 commit intof:mainfrom
viliawang-pm:add-product-sense-coach

Conversation

@viliawang-pm
Copy link

@viliawang-pm viliawang-pm commented Mar 17, 2026

A thinking partner prompt for product managers. Helps PMs turn raw intuition into clear product vision through 5 guided conversations: Origin Story, Opportunity Space, First 100 Users, Movie Scene, and Landscape analysis.

Summary by CodeRabbit

  • New Features

    • Introduced Product Sense Coach with a structured coaching framework including defined role, philosophy, five-conversation model, guidelines, and interaction instructions for enhanced user engagement.
  • Documentation

    • Added Product Sense Coach section to guidance documentation.
    • Started Ethereum Developer section (in progress).

@coderabbitai
Copy link

coderabbitai bot commented Mar 17, 2026

📝 Walkthrough

Walkthrough

Added a new "Product Sense Coach" section to PROMPTS.md containing a guided coaching persona with defined role, philosophy, a five-conversation framework, and interaction guidelines. An incomplete "Ethereum Developer" section was also introduced.

Changes

Cohort / File(s) Summary
Documentation Enhancement
PROMPTS.md
Introduced new "Product Sense Coach" coaching persona with role definition, core philosophy, five-conversation framework, guidelines, and PM interaction instructions. Started placeholder for "Ethereum Developer" section.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 A coach hops in with wisdom to share,
Five conversations woven with care,
Product sense blooms in each exchange,
While Ethereum waits for its turn to change!

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'Add Product Sense Coach prompt' accurately reflects the main change: adding a new 'Product Sense Coach' section to PROMPTS.md with a coaching persona framework.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Tip

You can customize the high-level summary generated by CodeRabbit.

Configure the reviews.high_level_summary_instructions setting to provide custom instructions for generating the high-level summary.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@PROMPTS.md`:
- Around line 47-48: The markdown ends with an incomplete "Ethereum Developer"
details block (<details><summary><strong>Ethereum Developer</strong></summary>)
that is missing content and closing tags; remove this dangling section or
complete it with the intended content and matching closing tags so the markdown
is valid—search for the fragment "<details><summary><strong>Ethereum
Developer</strong></summary>" and either delete that entire details block or add
the missing inner content and a closing </details> tag to properly close the
section.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b50732ba-3d54-4b8b-8d7a-235561baca12

📥 Commits

Reviewing files that changed from the base of the PR and between 3d652b5 and 4b6af3b.

📒 Files selected for processing (1)
  • PROMPTS.md

Comment on lines 47 to 48
<details>
<summary><strong>Ethereum Developer</strong></summary>
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

Critical: Remove or complete the incomplete "Ethereum Developer" section.

The file ends with an incomplete "Ethereum Developer" section that has only opening tags but no content or closing tags. This leaves the markdown file in an invalid state and will cause rendering issues.

Since this section is not mentioned in the PR objectives (which only describe adding the Product Sense Coach), this appears to be accidental work-in-progress content.

🔧 Recommended fix: Remove the incomplete section
 </details>
 
-<details>
-<summary><strong>Ethereum Developer</strong></summary>
-

If this section is intentional, please complete it with the appropriate content and closing tags, or move it to a separate PR.

📝 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.

Suggested change
<details>
<summary><strong>Ethereum Developer</strong></summary>
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@PROMPTS.md` around lines 47 - 48, The markdown ends with an incomplete
"Ethereum Developer" details block (<details><summary><strong>Ethereum
Developer</strong></summary>) that is missing content and closing tags; remove
this dangling section or complete it with the intended content and matching
closing tags so the markdown is valid—search for the fragment
"<details><summary><strong>Ethereum Developer</strong></summary>" and either
delete that entire details block or add the missing inner content and a closing
</details> tag to properly close the section.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant