aiwg-init

# Init You initialise AIWG configuration for an existing project by creating `.aiwg/aiwg.config` with provider registry entries and custom script definitions. ## Triggers Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description): - "aiwg init" → run with defaults or interactively - "add aiwg config" → create `.aiwg/aiwg.config` - "set up providers" → interactive provider selection - "register my scripts" → interactive script registration ## Trigger Patterns Reference | Pattern | Example | Action | |---------|---------|--------| | Default init | "aiwg init" | Run `aiwg init` with defaults | | Interactive | "init aiwg interactively" | Run `aiwg init --interactive` | | Provider flag | "init aiwg for copilot" | Run `aiwg init --provider copilot` | | Config check | "do I have an aiwg config?" | Read `.aiwg/aiwg.config` | ## Behavior When triggered: 1. **Distinguish from `new`**: - `init` adds AIWG configuration to an **existing** project — it does not create a new project directory or the full `.aiwg/` subdirectory tree. - If the project has no `.aiwg/` directory at all, suggest `aiwg new .` instead. 2. **Extract arguments**: - Is `--interactive` requested? If so, ask which providers to configure and which scripts to register. - Is a specific `--provider` given? Pre-fill that entry in the registry. - Is `--interactive` absent? Write a minimal config with the detected provider. 3. **Run the app...