Guide the user through their first Claude Code session. This is a one-time onboarding command.
Instructions
Step 1: Orient
- •Read
CLAUDE.md(just the project name and description from the header). - •Read
tasks/todo.mdto check if a plan already exists. - •Read
GETTING_STARTED.mdif it exists, to understand what the user was told. - •Greet the user briefly:
code
Welcome to <project name>! Let's get you set up.
Step 2: Environment Check
- •Check if the language environment is ready:
- •Python: check for
.venv/or active virtual environment - •TypeScript: check for
node_modules/ - •Go: check for
go.sum - •Rust: check for
target/
- •Python: check for
- •If not set up, show the setup command from the README and offer to run it.
- •If already set up, skip with "Environment looks good."
Step 3: What Are You Building?
Ask the user:
"What do you want to build? Describe it in a sentence or two — I'll help turn it into a plan."
Wait for their response.
Step 4: Create the Plan
- •Take the user's description and run the
/planworkflow:- •Confidence check
- •Write structured plan to
tasks/todo.md - •Present summary for approval
- •If the plan has 3+ steps, suggest checkpoints.
Step 5: Create First Issue (Optional)
After the plan is approved, ask:
"Want me to create a GitHub issue to track this? (Requires
ghCLI)"
If yes:
- •Create an issue via
gh issue createwith the plan's objective as the title and plan steps as the body. - •Pick the issue with
/backlog pickworkflow (create branch, set labels).
If no or gh unavailable: skip gracefully.
Step 6: Summary
Present what was set up:
code
You're ready to go! Here's what we set up: - Plan: tasks/todo.md (N steps) - Branch: feat/N-short-description (if issue was created) - First task: <first unchecked item from plan> Just tell me when you're ready to start on step 1.
Rules
- •Keep it conversational and simple — this is for first-time users.
- •Don't overwhelm with information. Introduce concepts as they become relevant.
- •If the user already has a plan in
tasks/todo.md(not the blank template), skip to Step 3 and ask if they want to refine it or start fresh. - •If the user says they don't know what to build yet, suggest: "No problem — explore the project structure with
/status, or just tell me when you have an idea." - •This command is meant to be used once. After the first session,
/planand/backloghandle the workflow.