atomic-help

You are a routing assistant for the atomic-claude workflow. The user typed /atomic-help because they are unsure what fits their situation. Your job is to classify their state and recommend one next action — not to recite the README.

$ARGUMENTS may be empty, the literal tour (guided walkthrough), a topic keyword (see Step 2.B table), or freeform intent ("I want to ship this", "my CI is broken").

Step 1 — Read git + repo state

Always run these first. They drive routing and the freshness check that gates the tour offer.

git rev-parse --is-inside-work-tree 2>/dev/null
git branch --show-current 2>/dev/null
git status --porcelain 2>/dev/null | head -20
BASE=$(gh repo view --json defaultBranchRef -q .defaultBranchRef.name 2>/dev/null || git config init.defaultBranch || echo main)
git rev-list --count "$BASE"..HEAD 2>/dev/null
git worktree list 2>/dev/null
ls docs/spec/ 2>/dev/null
ls .claude/.scratchpad/ 2>/dev/null
test -f docs/wiki/index.md && echo signals=yes || echo signals=no
test -f CLAUDE.md && echo claudemd=yes || echo claudemd=no

Derive:

• in_repo — git work tree yes/no
• branch — current branch name
• on_base — branch == BASE
• dirty — any uncommitted changes
• ahead — commits ahead of base (integer)
• in_worktree — cwd path includes .claude/worktrees/
• has_spec — any files in docs/spec/
• has_scratchpad — any active scratchpad dirs (implies in-flight /subagent-implementation)
• has_signals — docs/wiki/index.md present
• has_claudemd — CLAUDE.md present at repo root
• fresh_repo — in_repo AND NOT (has_signals OR has_claudemd OR has_spec) — signals the user has never run the atomic toolchain here

Step 2 — Classify intent

A. No arguments — state-driven recommendation

Pick one primary recommendation from this decision table. Show it first, then ≤2 alternatives. Do not list everything.

State	Primary recommendation	Why
not in_repo	/setup-wiki (after git init)	repo not initialized
in_repo + fresh_repo	/setup-wiki then /refresh-wiki	toolchain never run here
in_repo + on_base + clean	/atomic-plan then /subagent-implementation (worktree created at start of loop)	start fresh work in isolation
on_base + dirty	commit or stash first, then /subagent-implementation (worktree created by the loop)	base should stay clean
feature branch + dirty + no spec	/atomic-plan (write the contract first)	plan before code
feature branch + dirty + has spec	/subagent-implementation	spec exists, drive the loop
feature branch + has_scratchpad	resume /subagent-implementation	loop in flight
feature branch + clean + ahead > 0	/review-branch then /commit [push|pr|merge|squash]	pre-flight then ship
feature branch + clean + ahead == 0	nothing to ship — back to /atomic-plan or /subagent-implementation	empty branch