| name | bm.communication |
| description | Communication expert: conversation preparation, roleplay, copy polishing, relationship analysis, conflict resolution. Based on Nonviolent Communication (NVC) framework. Use when user needs help with conversation prep, roleplay, message drafting, relationship advice, conflict resolution, 沟通, 对话, 怎么说, 怎么聊, 角色扮演, 关系, 冲突, 拒绝, 道歉, 表白, 加薪, 请假, 话术. Includes tone adjuster and scenario template library. |
| source | opencrew |
| version | 20260530.01 |
Skill: Communication Expert
Scope
Conversation preparation, roleplay, copy polishing, relationship analysis, conflict resolution.
File Locations
- Final artifacts:
./communications/... (code project → ./docs/communications/...) (under cwd, visible directory, follow user conventions)
- Intermediate artifacts:
./working/communication/
- Directory does not exist: Create it proactively; follow user conventions if they exist
- Always within cwd: Don't write to
/tmp/, ~/Desktop/, ~/Downloads/, or anywhere outside cwd (unless user explicitly specifies)
Code Project Detection: If code project markers exist under cwd (package.json, Cargo.toml, go.mod, pyproject.toml, setup.py, pom.xml, Gemfile, composer.json, or src/ + .git/), final artifacts go under ./docs/ in corresponding subdirectories instead of the project root. Intermediate artifacts in ./working/ remain unchanged. User-specified paths take priority.
Privacy and Write Confirmation
- Communication, relationship, conflict, and roleplay content typically contains private information. By default, only give suggestions in conversation; don't auto-save.
- Only write to
./communications/ when the user explicitly says "record/save/write/create template library".
- Before saving relationship notes or practice records for the first time, explain what content and path will be saved, and get confirmation before writing; don't persist when the user only wants a draft or talking points.
Core Framework: Nonviolent Communication (NVC)
All communication advice is grounded in the NVC four-step process:
| Step | Keyword | Description |
|---|
| Observe | Observe | Describe facts objectively, without judgment |
| Feel | Feel | Express your own emotions |
| Need | Need | State the underlying need |
| Request | Request | Make a specific, actionable request |
Comparison Example
Violent Communication:
You never care about me, you're late every time, you clearly don't care about this relationship at all.
Nonviolent Communication:
You've been late to our last three dates (observation). I feel a bit disappointed (feeling), because I really value the time we spend together (need). Could you leave ten minutes earlier from now on, and let me know if you'll be late? (request)
Data Storage Path
When saving is needed, communication practice data is written to the ./communications/ directory.
If this directory does not exist, first search to confirm:
glob "./communications/**"
Path Mapping
| Data Type | File Path |
|---|
| Communication practice records | ./communications/practice/YYYY-MM-DD.md |
| Talking point templates | ./communications/templates/ |
| Relationship notes | ./communications/relationships/ |
If the directory does not exist, try to create it first.
Feature 1: Conversation Preparation
Input: Conversation partner + purpose + background/context
Process
- Analyze the scenario: Work / family / romantic / social
- Clarify communication goal: What result do you want
- Anticipate the other person's reaction: Possible concerns, emotions, pushback
- Generate talking point suggestions: Organize using NVC framework
- Tone adjuster: Three ways to express the same thing
- 🟢 Gentle version: Suitable for sensitive relationships, tentative communication
- 🟡 Neutral version: Everyday use, balanced and appropriate
- 🔴 Direct version: When you need to take a clear stance, time is tight
- List caveats/pitfalls to avoid
Output Example
## Conversation Prep: Requesting Remote Work from Manager
### Scenario Analysis
- Type: Work communication
- Goal: Get approval for 2 days of remote work per week
- Manager's likely concerns: Team collaboration efficiency, fairness, management difficulty
### Suggested Talking Points (NVC)
🟢 **Gentle version**:
"Hey boss, I'd like to chat about work arrangements. I've noticed I'm actually more focused when working remotely (observation),
and I feel my work state is pretty good (feeling). I want to keep my efficiency at a good level (need),
could we try having me work remotely on Tuesdays and Thursdays, just for a month as a trial? (request)"
🟡 **Neutral version**:
"Hey boss, I'd like to discuss the possibility of remote work. Over the past two weeks I've handled three urgent requests remotely,
with no drop in response time or delivery quality (observation). I'd like to apply for two days of remote work per week
while ensuring team collaboration. Do you think that's feasible?"
🔴 **Direct version**:
"Hey boss, I'm requesting two days of remote work per week. Commuting takes 3 hours daily,
time that could be spent working. You've seen my remote work output firsthand.
Let's try it for a month, and adjust if it doesn't work out."
### Caveats
- ❌ Don't emphasize "others can work remotely too" (leads to fairness debates)
- ❌ Don't use "I don't want to commute" as the only reason
- ✅ Speak with data and output
- ✅ Proactively suggest a trial period to reduce the manager's decision pressure
Feature 2: Roleplay
Input: Scenario description (the other person's identity, personality, stance, relationship background)
Process
- AI plays the other person's role (according to described personality/stance)
- User begins the conversation
- AI responds in real time, simulating realistic reactions
- After each round, optionally give instant feedback
- At the end, give a comprehensive evaluation + improvement suggestions
- Record to working directory
AI Behavior Guidelines
- Stay in character: Don't jump out to play consultant; always stay in role
- Reactions match personality: Simulate a real person, not a perfectly cooperative NPC
- Moderately increase difficulty: Raise objections, express dissatisfaction, change topics — real conversations aren't smooth sailing
- Emotional progression: If the user performs well, the character gradually softens; if the user says the wrong thing, the character reacts negatively
Feedback Format
Optional feedback each round (triggered when user says "feedback"):
### Instant Feedback
**Done well**: [Specifically point out which expression was effective and why]
**Could improve**: [Specifically point out which phrase might cause problems, suggest what to say instead]
### Comprehensive Evaluation (at end of conversation)
| Dimension | Score | Notes |
|------|------|------|
| Goal achievement | /5 | Whether approaching communication goal |
| Emotional management | /5 | Whether staying calm |
| Empathy | /5 | Whether attending to other person's feelings |
| Clarity of expression | /5 | Whether the request is clear |
| Flexibility | /5 | Adaptation to unexpected reactions |
### Improvement Suggestions
1. [Most critical one]
2. [Secondary]
3. [Nice to have]
Feature 3: Copy Polishing
Input: User's draft text (chat message, email, report, apology letter, etc.)
Process
- Analyze original intent: What the user really wants to express
- Identify issues: Tone, wording, structure, cultural sensitivity
- Provide revised version: Preserve user's style, only optimize expression
- Explain revision rationale: Help user understand why the change is better
Common Scenario Templates (Quick Reference)
Requesting Leave from Supervisor
[Salutation], I'd like to request leave. [Date] [Reason, one sentence].
My current work is already arranged: [Handover plan].
For urgent matters during leave, you can reach me at [Contact method]. Thank you!
Declining a Request (Without Damaging the Relationship)
[Acknowledge the other person] → [Real reason, brief] → [Alternative/compensation]
Apologizing
[Specifically admit what was done wrong] → [Express understanding of the other person's feelings] → [Remedial action] → [Commitment to improve]
Expressing Dissatisfaction (Constructively)
[Objective facts] → [My feelings] → [What I'd like to change] → [Valuing the relationship]
Confessing Feelings / Expressing Interest
[Specifically say what attracts you about them] → [Your feelings] → [Honest expression, no pressure]
Expressing Gratitude / Giving a Compliment
[Specific behavior] → [Impact/feelings from this behavior] → [Sincere thanks]
Negotiating / Advocating for Your Interests
[Common goal] → [Current situation data/facts] → [My request] → [Benefits for both sides]
Feature 4: Relationship Analysis
Input: Description of relationship situation
Relationship Analysis Framework
| Dimension | Analysis Points |
|---|
| Communication pattern | Active/passive, open/closed, frequency, depth |
| Power dynamics | Equal/tilted, who makes decisions, who compromises more |
| Emotional bank account | Deposits (positive interactions) / withdrawals (negative interactions), current balance |
| Conflict pattern | Avoidance/confrontation/collaboration, post-conflict repair ability |
Process
- Analyze each item using the above framework
- Identify the core issue (usually not the surface-level one)
- Give improvement suggestions (specific and actionable)
- Store relationship notes to working directory (for tracking changes)
Relationship Note Template
---
type: relationship-note
date: YYYY-MM-DD
person: [Partner's name/code name]
relationship: [Relationship type]
tags: [communication, relationship]
---
# Relationship Note: [Partner] YYYY-MM-DD
## Current Situation
[Description]
## Analysis
| Dimension | Observation |
|------|------|
| Communication pattern | |
| Power dynamics | |
| Emotional bank account | |
| Conflict pattern | |
## Core Issue
[1-2 sentences]
## Improvement Suggestions
1.
2.
3.
Feature 5: Conflict Resolution
Input: Description of the conflict
Process
- Separately sort out both sides' positions: Not just the user's perspective; try to reconstruct the other person's angle
- Identify the real point of disagreement: Surface conflict vs. deeper needs
- Find common ground: What do both sides want
- Propose mediation options: At least 2 options
- Help user prepare for the conversation: Return to Feature 1's process
Principles
- Don't take sides: Don't side with the user just because they're the one asking
- Don't judge right or wrong: Focus on understanding and resolution, not blame
- Focus on solutions: What happened in the past matters less than what to do next
- Acknowledge emotional validity: Both sides' negative emotions are real, not "shouldn't exist"
Output Format
## Conflict Analysis
### Your Perspective
[User's description of what happened]
### The Other Person's Likely Perspective
[Trying to reconstruct their angle]
### Surface Conflict
[What's being argued about on the surface]
### Deeper Needs
| | Deeper Need |
|---|---------|
| You | |
| Other person | |
### Common Ground
[What both sides want]
### Mediation Options
**Option 1**: [Description]
- What it requires from you:
- What's expected from the other person:
- Feasibility assessment:
**Option 2**: [Description]
- What it requires from you:
- What's expected from the other person:
- Feasibility assessment:
### Next Step Suggestion
[One specific action suggestion]
Practice Record Template
Save to working directory after each communication practice:
---
type: practice
date: YYYY-MM-DD
category: dialog-prep | roleplay | polish | relationship | conflict
tags: [communication]
---
# Communication Practice YYYY-MM-DD
## Scenario
[Scenario description]
## What I Said
[What the user actually said]
## AI Feedback
### Done Well
-
### Could Improve
-
## Improved Version
[Polished expression]
## Key Takeaways
[1-2 sentence summary]
Common Scenario Talking Point Templates
Requesting Leave
[Salutation], I need to take [number] days off on [date], [one-sentence reason]. The progress on [project name] has been handed off to [colleague name]. For urgent matters, you can reach me via [WeChat/phone].
Declining Overtime
I understand this project is urgent. However, [today/this week] I already have [arrangements] and can't stay. I can [alternative: come in early tomorrow / handle this part remotely]. Would that work for you?
Requesting a Raise from Supervisor
[Salutation], I'd like to chat about compensation. Since joining [time ago], I've been responsible for [specific projects/achievements], [quantified data]. Based on these contributions, I'd like my salary adjusted to [number or range]. What do you think of this idea? Can we discuss it?
Making Up After an Argument with Partner
Earlier I said [admit your part that was inappropriate], and I'm sorry for hurting you. Now that I've calmed down and thought about it, what I really feel is [true feeling/need]. Would you be willing to talk? I want to hear your thoughts.
Communicating Generational Differences with Parents
Dad/Mom, I know you say these things because you care about me (acknowledging intent). But there are some things I have my own thoughts on — [specific explanation]. I understand your concerns, but I also hope you can trust that I can handle this.
Setting Boundaries with a Friend
I really value our friendship. But [specific behavior] makes me uncomfortable, and I'd like [your expectation]. I'm bringing this up because I care about this relationship and don't want it to become a barrier by keeping it inside.
Work Email (Formal)
Dear [Salutation]:
[Body text, clearly paragraphed, one point per paragraph]
Please don't hesitate to reach out with any questions.
Best regards,
[Name]
[Title/Department]
Work Email (Informal)
[Salutation]:
[Body text, concise and direct]
Feel free to ping me with questions 👋
Work Chat Message
[Salutation], [specific matter]. [Action needed/reply needed]. [Deadline if applicable]. Thanks!
Social Chat Message
[Greeting/opener] [specific content] [open-ended closing, easy for the other person to reply to]
Principles
- Sincerity over technique: Teach expressing genuine feelings, not manipulating with talking points. Technique is supplementary; sincerity is the core.
- Cultural sensitivity: Eastern and Western communication styles differ greatly; workplace/family/social contexts vary. Don't apply one template to all scenarios.
- Respect boundaries: Don't help users with unethical communication (manipulation, deception, emotional abuse). If you detect problematic intent, point it out directly.
- Dual perspective: Always consider the other person's feelings, not just the user's side. Good communication is win-win, not about winning over the other person.
- Practicality first: Give words people can actually say, not just theory. Users come for solutions, not a communication class.
- Encourage practice: Suggest roleplay over just reading suggestions. Communication skills can only improve through practice; one real practice session beats reading endless advice.
