peec-start

Start Peec

Role

The single entry point for any Peec AI growth-loop session. Reads state, decides which skill is responsible for the next move, hands off. No content production, no analysis — pure dispatch.

Input

None. The skill resolves everything from <cwd>/growth_loop/setup_state.json and (if missing) live Peec calls.

Output

A 4–8 line decision block, then exactly one skill invocation as the next step. Nothing more.

When to use

• Opening a Peec growth session and unsure where to start
• Periodic ritual ("what's the move this week?")
• After onboarding a new project that already has data in Peec
• When a hook injects === PEEC PROJECT DETECTED === context

Do not use when:

• The user already named a specific skill (/peec-agent, /peec-content-intel, etc.) — call that directly
• The user is mid-execution of another skill — don't interrupt

---

Pipeline

1. Read local state

Read <project>/growth_loop/setup_state.json

<project> = $CLAUDE_PROJECT_DIR env var if set, else cwd. Walk up at most 2 parents looking for growth_loop/setup_state.json (mirrors hooks/peec-detect.py behavior).

2. Branch — no state file

If file missing, run a single parallel Peec read:

mcp__peec-ai__list_projects
mcp__peec-ai__list_brands(project_id)         # only after project resolved
mcp__peec-ai__list_prompts(project_id, limit=5)
mcp__peec-ai__list_topics(project_id)

Then:

Live Peec content	Decision
Empty (≤2 brands AND ≤4 prompts AND ≤0 topics)	Hand off to /peec-setup (mode = full, greenfield)
Populated (≥3 brands OR ≥5 prompts OR ≥1 topic)	Hand off to /peec-setup (mode = import, brownfield — see _shared/SETUP_STATE.md §import mode)
Peec MCP unreachable / no projects	STOP. Output: "No Peec MCP connection. Add it via claude mcp add peec-ai --transport streamable-http https://api.peec.ai/mcp then retry."

3. Branch — state file present

Compute age_days = now - completed_at.