setuplisted

Install Clio's project memory into the repository at the current working directory. Do every step yourself with Bash, in order. The user answers three `AskUserQuestion` batches (steps 0, 2, 5) and approves the two drafted files (step 2) — nothing else. Never guess, never ask permission for an action listed here, never write `CLAUDE.md` or the context file without the step-2 yes. ## 0. Take stock, then ASK batch 1 ```bash for t in bash jq git awk sed; do command -v $t >/dev/null || echo "MISSING: $t"; done git rev-parse --git-dir >/dev/null 2>&1 || echo "NOT A GIT REPO" [ -d .claude/clio ] && echo "ALREADY SET UP" ls CLAUDE.md .claude/CLAUDE.md .claude/CONTEXT.md 2>/dev/null ``` `MISSING` → stop, tell the user. `ALREADY SET UP` → say so and stop. Do not run `/init`. **ASK batch 1**, one call, only the items that apply: - `NOT A GIT REPO` → `git init`? Never without a yes. - Does the repo already have code, or is it empty (spec only)? Empty = **greenfield**. - Requirements: **Full** (a requirement document exists — which file?) or **Lite** (none)? - `CLAUDE.md` / `.claude/CONTEXT.md` / `.claude/rules/` already exist → they are the user's; Clio adds only the `@` import and the `## Project memory` block. One extra question: **bring them to Clio's format?** — the layout of `${CLAUDE_PLUGIN_ROOT}/skills/setup/templates/CLAUDE.md` and `CONTEXT.md`, trimmed to the ~150-line budget, path-specific bullets moved to `rules/`. Yes → step 2 shows the diff and asks again before w