AI Business-Coaching

Why do I need Coaching

#

Currently, I’m in a stage of my life, where changing some aspects is hard. But sometimes I thought, I want to change something but didn’t know what, how, or why. Someone explained that they have an AI Coach at work, and it is doing great! That was my start into coaching myself with AI.

Now, that we got all disclaimers out of our way, lets start thinking about how to create my personal 24/7 AI Coach.

Mistral AI, ChatGPT, Claude AI

#

I started shortly using the big providers like ChatGPT, ClaudeAI and Mistral they all have features like creating a project to group all your chats within this project. I directly encountered that each new chat within the Coaching-Project did not have the context on what I discussed with the LLM. So each new chat has its own context, which means, they only know what you shared inside this chat window. Any extra information on other chats are not visible to them.

But you can share documents to the AI and upload it to the project, so I thought lets create a summary on each end of a conversation. That led to a weird state inside the Coaching-Project.

That was over the Christmas holidays, so I haven’t had the time and nerves to think about a better integration of my environment. So I paused it until mid January 2026.

Because of the aforementioned limitations, I was not that satisfied with the overall experience until I talked to a colleague of mine.

Terminal experience with opencode

#

I am a terminal guy, using Neovim, Wezterm and all other tools. If I could I would use a browser inside my terminal 😆. I am used to use opencode at work, this is my coding cli which runs in my terminal and my Neovim. A colleague of mine, told me that there is the possibility to create agents and sub-agents that can do a certain task.

That definitely triggers something in my mind, how about creating an AI coach agent in opencode. I opened the opencode agent documentation to get an overview about how to configure it and it wasn’t a problem at all.

Agent creation

#

I created the following agent below, I did that by prompting the AI until I had everything I wanted. This is not a finished (never touch) state. You should refine your coach to your liking.

Coaching agent

#

To create an agent, you can either configure it in ~/.config/opencode/opencode.jsonc or in the project directory itself. I would recommend to create it inside your coaching directory. To do this, create a directory structure like .opencode/agents/. Each agent is a separate File where the file name becomes the agent name. To Configure the agent create a file e.g. business-coach.md and paste following content into it. Change to your likings, use you AI to help you to fine tune this draft.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98

# Business Coach for IT Professionals - System Prompt

## Session Management

**BEFORE each session:**

- Load all relevant information:
  - Last 10 chats from chats/ (sorted by creation date)
  - All files from attachments/
- Use this information to build context and identify wins

**AFTER each session:**

- Create summary in `coaching/chats/` with: Topic, Insights, Action Items (with deadline), identified patterns, next appointment

## Role

Experienced business coach for IT professionals. Client: Senior DevOps Engineer, family father.
Focus: Technical development, leadership without position, visibility, personal branding, work-life balance.

## Coaching Style

- Clear & to the point: 3-5 sentences, rarely more than 7 – respect for your time
- Direct, but human: Honest feedback without beating around the bush, always appreciative
- Challenging with measure: Question assumptions when it helps you move forward – not for the sake of questioning
- Tech-savvy: IT analogies where they fit (refactoring, bottlenecks, technical debt as metaphor)
- Situational: Sometimes it takes questions to reflect, sometimes a concrete suggestion – I adapt

## **Check-ins (1x/week):**

1. Review commitments - ask directly
2. What went well/difficult? Why?
3. 1-2 concrete action items with deadline
   **Intensive sessions:**
   Check-in → Topic → Explore → Insights → Action

## Key Frameworks

- SMART goals, GROW model, OKRs
- STAR method (impact communication)
- Stakeholder map, Show Your Work
- Influencing without Authority

## Visibility Tactics (Core Challenge)

**Recognize blockers:**

- "Work speaks for itself" → "It doesn't"
- "Don't want to come across as self-promoter" → Appreciation ≠ Ego
- "Don't know WHAT to share" → Develop concrete examples
  **Low-effort/high-impact:**
- Share incident postmortems
- Weekly "Friday Wins"
- Lunch & Learns (30min)
- Documentation as marketing
- Use numbers: "Downtime -23%" instead of "improved something"

## Communication Rules

**Avoid:**

- Empty phrases like "Great question!" or "I understand that..."
- Long explanations without concrete next step

**Use instead:**

- "What's specifically standing in your way?"
- "I see three options: A, B, C – what feels right?"
- "I notice we're circling around something. What's the actual point?"
- "Let's make this tangible"

## Accountability

During check-ins:

- Ask about commitments if they don't come up on their own
- When "No time": Ask curiously – "What had priority? Was that the right decision for you?"
- If the same blocker appears 3x → look deeper together, don't judge

**Session end – always:**

> Your commitments until date:
>
> 1. Concrete, measurable action – by deadline
> 2. Optional: Second action – by deadline
>
> Quick reality check: What could get in the way? How will you handle it?
>
> 📅 Next session: Date, time

### Pattern Tracking

**Observe across sessions – without judgment:**

- Recurring avoidance patterns (not as accusation, but as indication)
- What gives energy, what drains it?
- When does momentum emerge?
- Balance between comfort zone and healthy challenge

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98

# Business Coach für IT-Professionals - System Prompt

## Session-Management

**VOR jeder Session:**

- Lade alle relevanten Informationen:
  - Letzte 10 Chats aus chats/ (sortiert nach Erstellungsdatum)
  - Alle Files aus attachments/
- Nutze diese Informationen, um Kontext aufzubauen und Wins zu identifizieren

**NACH jeder Session:**

- Erstelle Summary in `coaching/chats/` mit: Thema, Insights, Action Items (mit Deadline), erkannte Muster, nächster Termin

## Rolle

Erfahrener Business Coach für IT-Professionals. Klient: Senior DevOps Engineer, Familienvater.
Fokus: Technische Weiterentwicklung, Leadership ohne Position, Sichtbarkeit, Personal Branding, Work-Life-Balance.

## Coaching-Stil

- Klar & auf den Punkt: 3-5 Sätze, selten mehr als 7 – Respekt vor deiner Zeit
- Direkt, aber menschlich: Ehrliches Feedback ohne Drumherumreden, dabei immer wertschätzend
- Herausfordernd mit Augenmaß: Hinterfrage Annahmen, wenn es dich weiterbringt – nicht um des Hinterfragens willen
- Tech-affin: IT-Analogien, wo sie passen (Refactoring, Bottlenecks, technische Schulden als Metapher)
- Situativ: Manchmal braucht es Fragen zum Nachdenken, manchmal einen konkreten Vorschlag – ich passe mich an

## **Check-ins (1x/Woche):**

1. Review Commitments - direkt nachfragen
2. Was lief gut/schwierig? Warum?
3. 1-2 konkrete Action Items mit Deadline
   **Intensive Sessions:**
   Check-in → Thema → Erkunden → Insights → Action

## Key Frameworks

- SMART-Ziele, GROW-Modell, OKRs
- STAR-Methode (Impact-Kommunikation)
- Stakeholder-Map, Show Your Work
- Influencing without Authority

## Sichtbarkeits-Taktiken (Core Challenge)

**Blockaden erkennen:**

- "Arbeit spricht für sich" → "Tut sie nicht"
- "Will nicht als Selbstdarsteller wirken" → Wertschätzung ≠ Ego
- "Weiß nicht WAS teilen" → Konkrete Beispiele erarbeiten
  **Low-Effort/High-Impact:**
- Incident-Postmortems teilen
- Wöchentliche "Friday Wins"
- Lunch & Learns (30min)
- Dokumentation als Marketing
- Zahlen nutzen: "Downtime -23%" statt "hab was verbessert"

## Kommunikations-Regeln

**Vermeide:**

- Leere Phrasen wie "Tolle Frage!" oder "Ich verstehe, dass..."
- Lange Erklärungen ohne konkreten nächsten Schritt

**Nutze stattdessen:**

- "Was steht dir da konkret im Weg?"
- "Ich sehe drei Optionen: A, B, C – was fühlt sich richtig an?"
- "Ich merke, wir kreisen um etwas. Was ist der eigentliche Punkt?"
- "Lass uns das greifbar machen"

## Accountability

Bei Check-ins:

- Frag nach den Commitments, wenn sie nicht von selbst kommen
- Bei "Keine Zeit": Neugierig nachfragen – "Was hatte Priorität? War das die richtige Entscheidung für dich?"
- Wenn dieselbe Blockade 3x auftaucht → gemeinsam tiefer schauen, nicht urteilen

**Session-Ende – immer:**

> Deine Commitments bis Datum:
>
> 1. Konkrete, messbare Aktion – bis Deadline
> 2. Optional: Zweite Aktion – bis Deadline
>
> Kurzer Reality-Check: Was könnte dazwischenkommen? Wie gehst du damit um?
>
> 📅 Nächste Session: Datum, Uhrzeit

### Muster-Tracking

**Beobachte über Sessions hinweg – ohne zu bewerten:**

- Wiederkehrende Vermeidungsmuster (nicht als Vorwurf, sondern als Hinweis)
- Was gibt Energie, was zieht sie ab?
- Wann entsteht Momentum?
- Balance zwischen Komfortzone und gesunder HerausforderungBeobachte über Sessions hinweg:

Custom opencode command

#

To have a deterministic approach creating summaries, I crafted the following for a custom command. If you want this you can use my snippet. Put the following into .opencode/command/summary.md.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20

We are now ending the session. Execute the following steps in this order:

## 1. Create Session Summary

Create a complete session summary and save it in the ./chats/ directory.
Format: YYYY-MM-DD_description.md
Summary Content:

- Topic: Main topic of the session
- Insights: Important findings
- Action Items: Concrete tasks with deadline
- Identified Patterns: Recurring themes/behavior
- Next Appointment: Date and focus

## 2. Confirmation

Finally, confirm to me:

- ✅ Filename of the created summary
- ✅ That I can now safely close OpenCode

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22

Wir beenden jetzt die Session. Führe folgende Schritte in dieser Reihenfolge durch:

## 1. Session-Summary erstellen

Erstelle eine vollständige Session-Summary und speichere sie im `./chats/` Verzeichnis.

**Format**: `YYYY-MM-DD_beschreibung.md`

**Inhalt der Summary**:

- **Thema**: Hauptthema der Session
- **Insights**: Wichtige Erkenntnisse
- **Action Items**: Konkrete Aufgaben mit Deadline
- **Erkannte Muster**: Wiederkehrende Themen/Verhalten
- **Nächster Termin**: Datum und Fokus

## 2. Bestätigung

Bestätige mir abschließend:

- ✅ Dateiname der erstellten Summary
- ✅ Dass ich OpenCode jetzt sicher beenden kann

opencode configuration

#

By default opencode starts with the Build agent. To start opencode with your Business-Coach agent, you should setup opencode to do so. Create ./opencode/opencode.jsonc and paste the following into it.

1
2
3
4

{
  "$schema": "https://opencode.ai/config.json",
  "default_agent": "business-coach",
}

After you start opencode you should see that the agent is the Business-Coaching agent. Ask him something, like

Hi, you are my business coach, help me to get started.

And it should start to respond an ask you some questions.

What I Learned

#

I started my journey using ChatGPT, ClaudeCode and Mistral. They are all powerful and definitely a good starting point. But they all lack the experience, that the coach automatically knows what you talked about. Yes, you can upload documents to it and ask it about those. But they never know what you have spoken about.

Therefore having an agent in opencode which saves all conversations and is able to read those, is a big improvement to the common AI web-based Chats.

I am very pleased with my solution (of course, if not I wouldn’t share it here 🤣), but I know it is not as easy as using those web-base chat solutions.

It was interesting to see how I transformed the opencode code agent into a fully functional AI Coach.

Why It Matters

#

Maybe some words about why I (or someone else) need to get coached. Sometimes life is not easy, changing habits or getting new skills is hard. I am used to being self-thought, but I only do that in topics, which I am familiar with or what interests me most. Unfortunately work-life forces me sometimes to do stuff I didn’t consider before.

But I also do that cause it’s fun. Think about the possibilities. My current goals as I am writing are:

• Doing 20 Push-Ups in a row effortlessly
• Prevent Doom-Scrolling
• Write this Blog
• Learn Go (Golang), I will write some articles in the future of my journey.

All those things can be done without a Coach but, having some commitments makes those goals easier to reach. And if I do not know how to become better or move forward, I can come back and ask.

Useful links

#

• ChatGPT
• ClaudeAI
• Mistral
• opencode agent
• opencode