---
name: balance
description: Show how the user's hours split between building and marketing, per project, from git history (and Wingspan posts if connected), and say what to do next. A company spends about 20% on R&D; a founder who codes with AI usually spends far more. Use when the user types /balance, or asks "am I building too much", "build vs marketing", "where is my time going", "should I build or market now". ALSO passive: before starting a new build task on a project that is far over its build share, say so in one line and suggest a marketing move.
---

# Balance: build vs market

A company's P&L puts about **20% into R&D**. The rest goes to selling it. A solo founder is the whole company, so their hours should look similar. With an AI agent, building is cheap and feels like progress, so it quietly takes over.

## Run it

```
python3 ~/.claude/skills/balance/balance.py            # last 14 days
python3 ~/.claude/skills/balance/balance.py --days 30
python3 ~/.claude/skills/balance/balance.py --json
```

**Default setup:** with no config it reads every git repo in `~/Code`, and each repo is one row. You can change three things in `config.json`, next to the script:

- **Folder:** `code_dir`, or set `BALANCE_CODE_DIR`.
- **Target:** `target_build_pct` (default 20).
- **Products:** list them under `projects`, each with its repos and an optional Wingspan `brand`:

```json
"projects": {
  "myapp": { "repos": ["myapp-api", "myapp-web"], "brand": "myapp" }
}
```

## How it counts

- **Build hours:** your commits, grouped into work sessions. A gap of more than 2 h starts a new one, and each session counts its span plus 30 min.
- **Commits that count as marketing:** a commit that only touches marketing paths (blog, landing pages, README, images).
- **Wingspan posts:** if the `wingspan` CLI is installed and a project has a `brand`, published posts count 0.75 h each and drafts 0.4 h each.
- **What's read:** only commit times and file paths. Nothing leaves the machine.

The numbers are estimates, good enough to see the split. Calls, demos and DMs aren't counted.

## How to present

1. Show the table as markdown.
2. Give one line per project that's off target, in hours.
3. If off-product repos take a lot of time, name them.
4. Give **one** next move: the most useful marketing action for the most over-built project, tied to what was just built. Example: "you shipped X this week. Write the post about it now."

Keep it short.

## Passive rule

Before starting a new feature on a project whose build share is above target + 15 (35% by default), say so in one line, suggest the marketing move, and then do what the user decides. Mention it at most once per project per session.