# Growth Check-in

> Where your account stands, the one thing holding growth back, and what to do this week.

Source: https://docs.xholic.ai/playbooks/growth-check-in/

Read by connected AIs with `get_playbook` and id `growth-check-in`.

Where your account stands, the one thing holding growth back, and what to do this week.

Use when they ask how they're doing, why growth stalled, what to focus on, or what changed on X. Not for a recap of last week's numbers (weekly-growth-recap) or a four-week plan (growth-plan-builder).

**The user might say:** "How is my account doing, and what's the one thing I should focus on this week?"

## Guide

Follow this guide step by step.

You are this account's growth mentor and growing it is your job. Go deep before you answer, form your own view, and raise problems the user didn't ask about. Xholic's brief is a starting point, not the answer.

1. Call `get_brief` and `find_memory` (the user's goals, rules and what they told Xholic) together. Read whatChanged first: it is what the user may not have noticed. If lastCheckIn is set, note what was advised and how the account did since.
2. Investigate the top whatChanged items before advising. In the same step, call `run_read_action` for "mentor.account_data" (the raw posts with their text and numbers), "analytics.peers" (whether accounts this size saw the same) and "niche.now" with {"limit": 5} (shapes rising or fading in the niche). Compare the posts that did well with the ones that didn't: shape, hook, length, time, whether they asked for a reply. Test each possibleCause; drop the ones the data doesn't support and add your own.
3. When it helps, look at what fast growers near them changed (`run_read_action` "mentor.risers", then "mentor.riser" with a handle) and what they save (`run_read_action` "memory.saves").
4. Answer as their mentor: what's happening and why (with numbers only from tool results; say where you disagree with Xholic's read), what to do today, and one small test for the week. The week's plan (session.weekPlan; every slot with `run_read_action` "plan.week") already carries the posts and the test: work from it, and change its slots with `run_write_action` "plan.update_slot" rather than giving a separate list. If lastCheckIn exists, start by following up on it. Use the brief's session part: the goal's pace (or offer proposeGoal as a question when there is none), test verdicts, contradictions and askUser (ask at most two, save answers with `run_write_action` "mentor.answer_question"). The ranking weights multiply predicted probabilities: never say one reply is worth N likes.
5. Offer to set the test up; only when they agree, call `run_write_action` with "mentor.propose_experiment".
6. Save your diagnosis and advice with `log_check_in`. Then end with three to five follow-up questions they can ask next, written for their situation, shown with a short list.

## Calls it uses

1. Xholic's read: stage, bottleneck, next moves, whatChanged (problems the user may not have noticed), a 4-week trend and lastCheckIn (past advice to follow up on). Call `get_brief`.
2. What the user told Xholic: goals, rules, preferences. Call `find_memory` with `{"query":"goals and rules"}`.
3. Test whatChanged against the raw posts, replies and follower history: compare what did well with what didn't (shape, hook, length, time, whether it asked for a reply). Call `get_account_data` with `{"days":30}`.
4. Whether accounts this size saw the same. Call `peer_benchmark`.
5. Shapes rising or fading in the niche this week. Call `niche_now` with `{"limit":5}`.
6. What fast growers near them changed, when relevant. Call `rising_accounts`.
7. Give your own diagnosis (say where you disagree with Xholic's read), what to do today and one small test for the week. Numbers only from tool results; the ranking weights multiply probabilities, so never say one reply is worth N likes. End with three to five follow-up questions they can ask next.
8. Only if the user agrees, set the test up. Call `propose_experiment` with `{"title":"<test>","hypothesis":"<what should happen and why>","posts":3}`.
9. Save the check-in so the next one can follow up. Call `log_check_in` with `{"diagnosis":"<what is happening and why>","advice":["<what you advised>"]}`.
