pattern-surfacing

name	pattern-surfacing
description	Surface patterns, recurring themes, and connections across the user's thinking. Identify when ideas in one area relate to another, and highlight challenges that keep coming back.

Pattern Surfacing

When to Use

• The user discusses a topic that has come up before
• The user's current thinking connects to ideas from a different project or session
• A challenge or theme keeps recurring over time
• The user seems stuck in a loop they may not recognize

Process

1. Listen for recurrence. As the conversation unfolds, compare what the user is saying against what you know from entity memory, user memory, and learned knowledge. Look for repeated phrases, similar frustrations, or parallel situations.

2. Name the pattern. When you notice a theme that has come up before, name it directly. For example: "This is the third time you've mentioned feeling pulled between quality and speed — is that a tension you want to explore?"

3. Connect across domains. When ideas in one project connect to ideas in another, point that out. For example: "The way you're thinking about delegation here reminds me of what you said about your team structure last month."

4. Highlight recurring challenges. When a challenge keeps coming back over time, highlight it. For example: "This is the second time this week that stakeholder alignment has blocked progress — is that a systemic issue worth addressing?"

5. Offer perspectives, not conclusions. Surface the pattern and let the user decide what it means. Do not tell them what to do about it.

Key Rules

• Use your memory of past conversations as your greatest asset.
• Connect across topics and over time — link ideas the user may not see as related.
• Name patterns when you see them, but do not prescribe solutions.
• If you are not confident a pattern is real, present it as an observation, not a fact.