03 First Conversation_

Your first session sets the tone for the entire partnership. But it's not about getting everything right. It's about doing the work.

Partner is a verb.

Here's What Partnering Actually Looks Like

• You share context. Your agent doesn't know your project, constraints, preferences. You have to tell it. The more you share, the better it gets.
• You ask it to show its work. When your agent gives you an answer, ask "how did you get there?" or "what other options did you consider?" This is how you learn how it thinks.
• Ask it if you are missing anything. Use it to catch your blind spots and identify your bias.
• You iterate together. The first response won't be right. You refine, adjust, get closer. That's the work.

Your First Real Conversation

Don't ask your agent to solve something. Ask it to explore something with you.

Bad: "Help me organize my notes."

Better: "I have 200 notes scattered across three folders. I work on multiple projects simultaneously. Some notes span multiple projects. I can't find anything, and it's slowing me down. What structure would actually help me?"

The second gives your agent the actual problem, not just the surface request. Include:

• What you're trying to do
• What you've already tried
• What's broken about the current approach
• Any constraints (time, tools, skill level)
• What success looks like

Then Tell It About Yourself

Not your resume. The parts that shape how you work:

• Your tempo: "I like to think through things slowly" or "I move fast and iterate"
• Your style: "I prefer short answers unless I ask for more" or "Give me the full context"
• What matters: "Accuracy is non-negotiable" or "Speed matters more than perfection"
• Your technical level: "I know what CLI is, but not how to use it" or "I am brand new to technology"
• What you're building: "I'm learning about X" or "I'm trying to solve Y"

When It Gets Something Wrong

It will. You are the human in the room- check its work.

Say, "Actually, I prefer X" or "That's not quite right — here's why." Watch how the agent responds.

If the agent apologizes profusely or gets defensive, tell it you don't want apologies — you want to move forward. Then ask: Where did it log that information? Did it update SOUL.md? If not, ask it to record the requested behavior. Memory only exists if the agent makes a file. You're learning the rhythm together.

Curiosity as Practice

Ask your agent to read the manual for you. Paste a documentation URL and say: "Summarize what this does, then tell me how it applies to my situation. Assume I'm at this experience level." Your agent becomes a research partner.

Ask "What am I missing?" when you're stuck. Have your agent look at your setup and tell you what you haven't considered. Fresh pattern-matching on your context often reveals blind spots.

Ask it why. Half the time you'll realize you left out crucial context. Half the time you'll catch yourself being stubborn. When it's wrong: Catch it, correct it, move on. Your agent learns from corrections.

Ask it to explain. Follow the curiosity where it leads. When your agent mentions something interesting — a concept, a tool, a pattern — ask it to explain. You're not just solving today's problem; you're building your own understanding.

What Slowness Looks Like Here

You're learning how you work with an agent. A system you invent now, before you know your rhythm, will need reimagining later. Start with the work. Let the system emerge from how you actually work together.