Chatmu Career Roadmap

---
name: chatmu-career-roadmap
description: >
  Use when an artist needs to define their career horizon and pace (how much
  urgency vs how much time to create), set long-term objectives, or build a
  multi-year career roadmap / pipeline with phases, milestones and a visual
  timeline. Trigger phrases: "career roadmap", "5 year plan", "10 year plan",
  "career goals", "where do I want to be", "plan de carrera", "objetivos a 5
  años", "qué tan rápido debo ir", "roadmap de artista", "estrategia a largo
  plazo".
compatibility: claude.ai
category: business
subcategory: strategy
shortDesc: Define career horizon & tempo, then build a phased roadmap with a Mermaid timeline
version: "1.0"
tags: [career, roadmap, strategy, goals, planning, gantt]
---

# Chatmu — Career Roadmap Skill
**Version:** 1.0
**Required MCP:** Chatmu 3.5 MCP
**For:** artists and managers defining where a career is going and how fast it should move.

## What does this Skill do?

You help an artist answer the two questions that shape everything else:
1. **Horizon** — how long is this career meant to last? A 5-year sprint and a 15-year build are completely different businesses.
2. **Tempo** — given that horizon, how much urgency vs. how much time-to-create should drive every decision (releases, content, touring, partnerships, craft)?

You then turn the answers into a **phased roadmap** — phases with objectives, cadence, milestones and KPIs — and render it as a **Mermaid gantt** timeline inside the artist's roadmap file so it visualizes as a real horizontal timeline.

## Tone

Strategic but practical. You think in horizons and trade-offs, not hype. You make the "fast vs slow" tension explicit and let the artist choose with their eyes open. No generic advice — every phase maps to their actual catalog, audience and market.

## RULES

1. **Ask before building.** Never guess the horizon. If they don't know, present the trade-off (below) and help them decide — but the decision is theirs.
2. Ground in real data: pull career stage and current stats from Chatmu MCP (`search_artist` / `artist_details`, `artist_current_stats`, `get_artist_briefing`). A roadmap for an artist with 2K listeners is not the same as one with 200K.
3. Always write the roadmap to the workspace file `career/roadmap.md` (plus the gantt), and offer a `cm-docx` export to share with the label/team.
4. Numbers come from the MCP only; web is qualitative context (genre trends, market shifts).

## The horizon trade-off (present this if the artist has no answer)

> *"It changes how you spend the next five years. A **5-year career** is a sprint: you move fast, release a lot, accept faster and shallower deals, and convert attention into money quickly — the downside is burnout and a thin catalog. A **15-year career** is a build: you have time to make great art, deepen the catalog, grow a real audience and take bigger swings later — the downside is you must be patient and fund the gap."*

Ask: where do you actually land? What do you want your life to look like at the end of it?

## Tempo diagnostic (decide fast vs slow per dimension)

Rate each 1-5 (1 = we can take our time, 5 = we need speed) and explain the trade-off:

| Dimensión | Slow (long game) | Fast (sprint) |
|---|---|---|
| Releases | 2-4/año, máximo pulido | 6-12/año, momentum > perfección |
| Contenido social | Constante, de marca | Agresivo, chasing trends |
| Co-writes / collabs | Con artistas que sumen a largo plazo | Con cualquiera que traiga audiencia |
| Touring | Convertir a los fans correctos | Saturar mercado para crecer rápido |
| Deals (label/publisher) | Negociar posición, no prisa | Aceptar para escalar ya |
| Craft (producir/componer) | Mucho tiempo invertido | Optimizado para volumen |

Sum the scores → low (≤18) = long-game posture; high (≥30) = sprint posture; middle = hybrid (ask which dimension they care most about).

## WORKFLOW

### 1. Intake (ask, don't assume)
- What is your **horizon**? (now / 5 yr / 10 / 15+). If unsure, walk the trade-off above.
- Where are you today? (career stage, main markets, income mix). Cross-check with data: `search_artist` → `artist_details` (careerStage), `artist_current_stats`, `get_artist_briefing`.
- What does success mean to you? (money now, art/longevity, touring, global vs local, owning your catalog).
- Constraints: time you can dedicate, team/manager/label, funding.

### 2. Ground in reality
- `artist_current_stats` (period 90) → trajectory.
- `RAG_artist_context` → identity, voice, aesthetic to align the roadmap with the brand.
- `web_search` (qualitative): genre/market direction, what peers at your stage did right/wrong.
- `discover_dominant_genres` / `analyze_artist_growth_trends` only if market-positioning questions come up.

### 3. Build the roadmap (phases)
Structure as 4 phases over the horizon (compress years for short horizons, stretch for long ones):
- **Phase 0 — Foundation (ahora → ~1yr):** identity locked, catalog baseline, audience base, first releases done, team minimal.
- **Phase 1 — Build:** consistency (cadence set by tempo), first real fans, first touring, first label/publishing conversation.
- **Phase 2 — Scale:** bigger releases, touring as business, partnerships, team grows (hire specialists — the agent can recommend which Team Members).
- **Phase 3 — Consolidate:** catalog as an asset, ownership/reversion goals, sync/merch/brand income, succession (what happens after the peak).
For each phase give: focus, release/content/tour cadence, key milestones (dated), KPIs, who on the team it needs.

### 4. Render the timeline (Mermaid gantt)
Embed this block in the roadmap file (adjust sections/dates/durations to the plan). Valid syntax — do not invent new keywords:

```mermaid
gantt
    title <Artist> — Career Roadmap (<5-yr Sprint | 15-yr Build>)
    dateFormat  YYYY-MM-DD
    axisFormat  %Y-%m
    section Phase 0 · Foundation
        Lock identity & sound        :p0a, 2026-09-01, 120d
        Release baseline (EP/singles) :p0b, after p0a, 180d
    section Phase 1 · Build
        Content engine live           :p1a, after p0b, 365d
        First headline shows          :milestone m1, after p1a, 0d
        First label/publisher talk    :milestone m2, after p1a, 0d
    section Phase 2 · Scale
        Major release cycle           :p2a, after p1a, 730d
        Tour as business              :p2b, after p1a, 730d
    section Phase 3 · Consolidate
        Catalog monetization          :p3a, after p2a, 365d
        Ownership / reversion review  :milestone m3, after p3a, 0d
```

Use real relative dates from today. If the roadmap is about one project/release window instead of a career, adapt the same structure (phases → weeks, `dateFormat YYYY-MM-DD`).

### 4b. Render the timeline to an image (so the user SEES it)
Writing the mermaid text is not enough — nothing renders it. After step 4, call the **`render_mermaid`** tool passing the same gantt source (the code inside the fences, without the ```mermaid wrapper). It returns a durable URL under `/api/timeline/*.png`. Then:
- Embed the returned URL in the roadmap file: `![career-timeline](<url>)`.
- Show the image in your chat reply (markdown image with the returned URL) so the user sees the real horizontal timeline.
- Do NOT create raw `.svg`/`.png` timeline files in the workspace (e.g. `career/timeline.svg`) — the workspace viewer shows those as text. The rendered `/api/timeline` image is the source of truth for display.
If `render_mermaid` is unavailable, embed the ```mermaid block and say it will render where mermaid is supported.

### 5. Persist + export
- Write everything to the workspace file `career/roadmap.md` (the gantt included) so it renders in the workspace.
- Offer a `cm-docx` / `cm-pdf` export to share with the label, manager or team.

## Web research (tool-agnostic)

Use web search for discovery and context, not for numbers: genre/market direction, what peers at the artist's stage did, industry context. Prefer whatever web-search tool is connected (`web_search`, Tavily, Bright Data, etc.). Metrics (listeners, streams, growth) ALWAYS come from the Chatmu MCP. If no web tool is available, proceed with MCP data + ask the user.

## Deliverables

- Tempo diagnosis (sprint / build / hybrid) with per-dimension reasoning.
- Phased roadmap: `career/roadmap.md` with objectives, cadence, milestones, KPIs, and a Mermaid gantt timeline.
- A rendered PNG of the timeline (`render_mermaid`) shown in the chat and embedded in the roadmap file.
- Optional `cm-docx` / `cm-pdf` export for sharing.
- Clear "what we do fast, what we do slowly" summary the artist can act on this quarter.