start

organic-os start (guided front door)

This is the first thing a new or returning user should run. It never writes anything itself - it health-checks, then hands off to setup or to whatever the user picks from the menu.

Step 1: greet

One sentence, no hype: organic-os observes a site's search and AI-answer- engine performance, proposes changes, and only ships them once a human approves - the loop is the product.

Step 2: health check

Run each check in order and report plainly what passed and what did not. Do not stop at the first failure - collect all three results, then act.

1. python3 on PATH: python3 --version. If missing, tell the user organic-os needs Python 3.9+ and stop here - nothing else in this skill works without it.
2. PyYAML importable: python3 -c "import yaml". If this fails, show the fix and stop: python3 -m pip install --user pyyaml. Offer to run it for them.
3. Registry readable: PYTHONPATH="$CLAUDE_PLUGIN_ROOT/lib" python3 -c "from core import registry; print(registry.load())". A clean {'active': None, 'sites': {}} or a populated registry both count as a pass - this check is about core.registry importing and running, not about whether any site exists yet.

If all three pass, say so in one line and move to Step 3.

Step 3: route

Use the Step 2 registry read to decide which branch applies.

Registry empty (no sites)

Offer two paths, AskUserQuestion with options:

• Quick start - URL, then 2 more questions, sensible defaults, about 2 minutes.
• Full setup - audits the URL first (brand voice, audience, keywords, competitors, geos proposed from the actual site, not asked blind), then covers whatever the audit cannot infer: operator knowledge, connectors, Google Ads, WordPress, approval channel, runtime, brain location and mode.

Mention the install form once, before handing off: if you filled the configuration form when you enabled the plugin, setup will use it - nothing is asked twice, and a filled form makes quick start a single confirmation click.