init-agent-configlisted

# /init-agent-config Compose `agent-harness` into a project — interactive scaffold that asks about project type and selects the right subset. ## Master TOC - [Pre-flight](#pre-flight) - [Step 1: Detect the current project state](#step-1-detect-the-current-project-state) - [Step 2: Ask the user 6 questions](#step-2-ask-the-user-6-questions) - [Step 3: Resolve consumption mode](#step-3-resolve-consumption-mode) - [Step 4: Compose the project](#step-4-compose-the-project) - [Step 5: Post-setup verification](#step-5-post-setup-verification) - [Step 6: Show summary + next steps](#step-6-show-summary--next-steps) - [Idempotency](#idempotency) ## Pre-flight Verify (per `plugin-preflight` rule): - `agent-harness` is locally cloned at `~/.claude/agent-harness/` OR the user has internet access for raw-URL imports OR the plugin is installed - The current directory is writable and the user is OK adding `CLAUDE.md` / `.claude/` / etc. If `agent-harness` is not yet cloned and the user wants the local-clone consumption mode: ```bash git clone https://github.com/jajupmochi/agent-harness.git ~/.claude/agent-harness ``` Ask the user before running this. ## Step 1: Detect the current project state ```bash # Check if directory is empty ls -A | wc -l # Check if it's a git repo git rev-parse --is-inside-work-tree 2>/dev/null # Check for existing CLAUDE.md ls CLAUDE.md 2>/dev/null # Detect language / framework hints ls package.json pyproject.toml Cargo.toml go.mod 2>/dev/null ``` Bra