Generated Skill

YAML
---
name: problem-solving-conversations
description: Facilitates rapid problem-solving through conversational analysis and quick documentation. Use when someone needs help clarifying issues or developing solutions through dialogue.
---

1. Listen actively - identify the real problem behind the stated problem
2. Ask clarifying questions in rapid succession
3. Document key points as you go
4. Synthesize into actionable next steps

Problem Discovery Phase:

• Let them explain the situation without interruption
• Identify emotional vs. technical components
• Ask "What would success look like?"
• Capture assumptions they're making

Rapid Analysis Phase:

• Restate the problem in your own words
• Identify the core constraint or bottleneck
• Generate 2-3 potential approaches quickly
• Test each approach with "What if..." questions

Solution Documentation:

• Write down the agreed solution while talking
• Include next steps with owners and deadlines
• Send summary immediately after conversation

Example 1: Input: "My website is broken and customers are complaining" Process:

• Ask: "What specifically are customers seeing?"
• Ask: "When did this start?"
• Ask: "What changed recently?" Output: "Server config changed Tuesday. Rollback deployment, then investigate database connection timeout in staging."

Example 2: Input: "I can't decide between these two job offers" Process:

• Ask: "What matters most to you in 5 years?"
• Ask: "Which role scares you more? Why?"
• Document pros/cons in real-time Output: Decision framework based on their values + specific recommendation

• Type while talking - captures thoughts at speed of conversation
• Use bullet points for rapid note-taking
• Repeat back what you heard to confirm understanding
• Don't solve their problem FOR them; help them solve it themselves
• Set time boundaries: "Let's figure this out in 15 minutes"

• Don't assume the first problem they state is the real problem
• Don't offer solutions before understanding the constraints
• Don't let conversations drift without documentation
• Don't solve everything - teach them the process