onboard

Onboard

Interactive wizard that collects parameters and generates the ## Automation Config block.

Input: $ARGUMENTS = (none) | --fresh | --update

• No arguments (default): auto-detect existing config and route accordingly
• --fresh: force fresh mode, skip config detection
• --update: force update mode, error if no config exists

Scope

Target directory = git repository root (detect via git rev-parse --show-toplevel). If not in a git repo → use CWD.

• Target file: {target_dir}/CLAUDE.md
• NEVER read or write CLAUDE.md outside of the target directory
• NEVER traverse parent directories to find CLAUDE.md
• Before any write operation, display: Target: {absolute_path}/CLAUDE.md — Is this correct? [Y/n/custom path]
• If CWD is NOT git root AND a CLAUDE.md exists in a parent directory: "You're in a subdirectory. CLAUDE.md exists at {parent}/CLAUDE.md. Write here ({CWD}) or there ({parent})? [here/THERE]"

Step 0: Detection and Routing

1. Determine the target directory per ## Scope rules above
2. Read {target_dir}/CLAUDE.md
3. Look for ## Automation Config section
4. If --fresh in $ARGUMENTS → skip detection, go to Fresh mode (step 1)
5. If --update in $ARGUMENTS and no config exists → error: "No Automation Config found. Run without --update to create one."
6. Route based on detection:

State	Action
No config exists	Fresh mode (step 1)
Config exists, current version (has Pipeline Profiles or Metrics)	Offer: "[1] Update existing config [2] Start fresh (overwrites)"
Config exists, old version (no Pipeline Profiles and no Metrics)	"Detected older config format. Update it manually to match the current format in docs/reference/automation-config.md. Continue anyway? [y/N]"

In update mode: parse entire existing config into key→value structure per section. This provides default values throughout the wizard.

Then proceed to:

• Fresh mode → step 1
• Update mode → step U0

Fresh Mode

Step 1: Template Offer