climb

Start here

Say in one line what you'll make: which step someone is on, what's holding them back, and one thing to try next on their own code.

What the champion typed after the command, if anything: $ARGUMENTS

If that's blank, run the guided flow below. If it has text, or they already told you some of this, use what it answers and ask only for what's still missing.

Then ask:

1. Who is this for? Use AskUserQuestion with "A teammate" (recommended), "Me", and "The team".
2. How do they work today? For the team, ask how most of the team works. Use AskUserQuestion with "One session at a time, reads every change", "A few sessions in parallel", "Many agents, or Claude starts most of them", and "Can't get to current tools yet". If they pick the third, ask who starts most of the agents, to tell Step 3 from Step 4. Their own description also works.
3. What gets in their way most? A plain question. The default is "not sure yet".
4. Should I look at Claude Code session transcripts too? This is optional, and it's a consent question.
   • For "Me": suggest /insights first, which reports on recent sessions without you reading them. To read the transcripts themselves, work out this project's folder under ~/.claude/projects/ from the working directory (the cleanupPeriodDays setting at https://code.claude.com/docs/en/settings-reference covers these transcripts), and name that exact folder.
   • For a teammate or the team: use only transcripts each person chose to share, given to you as a path. Ask the champion for the path, and confirm the person shared it themselves.
   • Use AskUserQuestion with "Not yet" (recommended) and "Read [the exact folder or files]". Say you'll read only what's there now. Read nothing else.

Don't pull usage numbers or search anyone's work beyond what the champion allowed here.

How to ask: one question at a time, or a small batch of related choices, and wait for the answer before you go on. When the answer is one of a few options, use the AskUserQuestion tool with up to four options, the recommended or most common one first. If AskUserQuestion isn't available, give the same options as a short numbered list and wait for the answer. Ask a plain question only when the answer is open, such as a goal or team names, and suggest a default. When a question asks how someone works or what score fits, mark no option as recommended. A consent question, about reading through git, gh, chat, or a connector, or about writing a file, puts the safe choice, such as "Not yet", first as the recommended one. A pick counts as a yes only for the exact read or write it names. If the champion says "go", list the defaults you'll take for the remaining questions, then take them, but still stop at every consent question. A default never counts as a yes.