arthai-marketplace

/onboard

Session onboarding — project briefing, work prioritization, and guided setup.

Synopsis

/onboard

When to use it

At the start of a session, to see where things stand and what to work on
After time away — “where did I leave off?” — to recover branch, plan, and PR context
On a brand-new (empty) project, to get pointed at the right first steps
Not for: deep project learning and toolkit configuration — that’s /calibrate; or populating CLAUDE.md — that’s /scan

Quickstart

/onboard

What you’ll see: any toolkit updates since your last session, then a tiered briefing — 🔴 Fix first, 🟡 Waiting on you, 🔵 Continue, ⚪ Available — with PR/issue numbers, uncommitted files, plan progress (e.g., “Step 3/5” or “Phase 2”), and a menu of available workflows. It presents and waits; it never auto-starts work.

Examples

/onboard            # the only form — behavior adapts to your project's state

What it does

Detects project state — greenfield (no code, no CLAUDE.md, fresh git history) vs brownfield (existing code).
Greenfield flow — asks one question via AskUserQuestion (“What are you building?”) — a user-confirmation checkpoint — then suggests a tech stack and asks you to confirm or adjust it (user-confirmation checkpoint). It then runs /scan to scaffold CLAUDE.md, and creates a project plan via /planning if the feature is non-trivial — or scaffolds directly if it’s simple enough.
Brownfield: toolkit update check (always first) — compares the toolkit’s current version against what this project last saw and shows new commits, new skills, and updated agents. If the project has never been calibrated, it shows a /calibrate hint.
Deep context gathering (no questions asked) — in parallel: git state (branch, status, recent commits, stashes), GitHub state via gh (your open PRs, review requests, assigned issues, recent merges, unassigned issues), active plan files, and environment health from the CLAUDE.md ## Environments table (Docker containers, health endpoints — production is checked read-only). Also checks whether the tech-debt baseline (written by /tech-debt) is stale: if it’s more than 14 days old and there have been 5+ commits since, a hint appears in the ⚪ Available tier suggesting you run /tech-debt to refresh it; if no baseline exists yet, it suggests creating one.
Prioritizes — weights findings by the nature of your project (production app vs early-stage vs library) and by labels (bug/critical/security → fix first; CHANGES_REQUESTED or stale PRs → waiting on you).
Presents the briefing — only the tiers that have items, with actionable detail (who’s waiting, how long, which files, which plan step) plus the workflow menu (/planning, /fix, /qa, /pr, …).
Routes on your choice — picks the right skill or fix command for whatever you select. If you type something specific at any point, onboarding gets out of the way.

Output & artifacts

The briefing itself, in the conversation — no code or config changes
.claude/.toolkit-last-seen-sha — updated so toolkit changes are only announced once
Greenfield path may chain into /scan (writes CLAUDE.md) or /planning

Troubleshooting

Problem	Fix
No PR/issue section in the briefing	`gh` CLI isn’t installed or authenticated — onboard degrades gracefully and shows git-only state
“Everything looks clean” and nothing else	That’s the real state: main branch, no uncommitted work, no open PRs/issues — just tell it what to build
Briefing shows only 3 items per tier	With 10+ findings it truncates to the top 3 per tier — ask to see the full list
Environment checks missing	CLAUDE.md has no `## Environments` table yet — onboard still checks Docker containers and `.env.local` as a fallback, but run /calibrate or /scan `environments` to document your full environment config for a richer check next time

/calibrate — first-time deep project learning (onboard hints at it when missing)
/scan — populates CLAUDE.md; onboard runs it for greenfield projects
/welcome — the non-engineer equivalent (intent menu instead of a briefing)
/planning — where feature work usually goes next