The interactive init wizard

# Set up Smithers exactly how you want it.

No more all-or-nothing scaffold. Check off the workflows, skills, and agents you actually want. Or skip the picking entirely: describe a workflow in plain English and watch it get built.

$ smithers init
À la carte selection Describe a workflow, get one --yes for CI
smithers init
$ smithers init
Workflows
[x]open-code-reviewreview PRs
[x]docs-driven-developmentdocs as contract
[ ]release-contentchangelog + thread
Skills
[x]smithersagent onboarding
Agents
[x]codex5.6 Sol · Terra · Luna · default
[ ]claudefallback only
↑↓ move space toggle ⏎ install a all

Why this changed

## Setup used to hand you everything, or nothing.

The old init dumped every workflow, skill, and agent doc into your repo whether you wanted them or not, and then you deleted half of them. New users could not tell what any of it was, so they took the whole pile or bounced.

Two ways in

## Pick it, or describe it.

à la carte

### Check exactly what you want

An OpenTUI wizard groups everything into workflows, skills, and agents. Toggle each item, read what it does, and install only that. Your choices are remembered.

# interactive by default
$ smithers init
# non-interactive for CI
$ smithers init --yes
make-workflow

### Say it in English

Do not know what to pick? Describe the job. The builder turns your sentence into a real, editable workflow and drops it into your repo, ready to run.

$ smithers make-workflow \
"review my open PRs every night"
# -> .smithers/workflows/review-prs.tsx

What you get

## Onboarding that respects your repo.

☑ per-item

### Choose down to the item

Not "all workflows" but the three you want. Same for skills and per-agent doc sets. Deselections stick.

✎ natural language

### Describe, then edit

make-workflow scaffolds a real workflow from a sentence. It is yours to tweak, not a black box.

◎ agent-aware

### Finds your agents

It detects the coding agents you already have installed and offers to wire them up, no guessing.

⚙ --yes

### Scriptable too

Every interactive path has a non-interactive flag, so the same init runs clean in CI and Dockerfiles.

## Start with just what you need.

Run the wizard and check a few boxes, or describe the first workflow you want and let it build one.

$ bunx smithers-orchestrator init