onboarding

DevSquad Onboarding

Guide the developer through environment detection, preference capture, and config generation. On re-run, load existing config as defaults and only overwrite fields explicitly changed.

Prerequisites

• DevSquad plugin installed
• lib/state.sh and lib/cli-detect.sh available via ${CLAUDE_PLUGIN_ROOT}

Flow

Execute these five steps sequentially. Each builds on the previous.

Step 1: Environment Detection

Run detection scripts to identify available CLIs and plugins:

bash ${CLAUDE_PLUGIN_ROOT}/skills/environment-detection/scripts/detect-environment.sh
bash ${CLAUDE_PLUGIN_ROOT}/skills/environment-detection/scripts/detect-plugins.sh

If detection scripts unavailable, fall back to:

source ${CLAUDE_PLUGIN_ROOT}/lib/cli-detect.sh
DETECTION_RESULT=$(detect_all_clis)

Present summary: which CLIs are available, which are missing, which plugins detected.

Step 2: Preference Capture

Check if .devsquad/config.json exists (re-run). If so, load current values as defaults.

Ask three questions interactively:

1. Enforcement mode — advisory (default) or strict
2. Default routes — which agent handles research, reading, code gen, testing, synthesis
3. Agent preferences — word limits, line limits, auto-suggest

See references/preference-questions.md for full question text and validation rules.

Step 3: Save Configuration

Initialize state directory and write config:

source ${CLAUDE_PLUGIN_ROOT}/lib/state.sh
init_state_dir
write_state "config.json" "$CONFIG_JSON"

On re-run, merge new values with existing config. Preserve created timestamp, update updated.

See references/config-schema.md for JSON schema and merge rules.

Step 4: CLAUDE.md Snippet (Opt-in)

Evaluate project setup and recommend whether to add a DevSquad section to CLAUDE.md. This is optional — hooks work regardless.

Present recommendation, ask for explicit consent, show preview before insertion.

See references/claude-md-logic.md for evaluation rules and generation commands.