configuring-settings

<user_command>/kata:configure-settings</user_command>


<objective>
Allow users to toggle workflow agents on/off and select model profile via interactive settings.

Updates `.planning/config.json` with workflow preferences and model profile selection.

**Handles missing config keys:** If config.json is missing any expected keys (e.g., `pr_workflow`, `commit_docs`), prompts user for preferences and adds them.
</objective>

<process>

## 1. Validate Environment

```bash
ls .planning/config.json 2>/dev/null
```

**If not found:** Error - run `/kata:new-project` first.

## 2. Read Current Config and Detect Missing Keys

```bash
cat .planning/config.json
```

Parse current values with defaults:
- `mode` — yolo or interactive (default: `yolo`)
- `depth` — quick, standard, or comprehensive (default: `standard`)
- `parallelization` — run agents in parallel (default: `true`)
- `model_profile` — which model each agent uses (default: `balanced`)
- `commit_docs` — commit planning artifacts to git (default: `true`)
- `pr_workflow` — use PR-based release workflow (default: `false`)
- `display.statusline` — show Kata statusline (default: `true`)
- `workflow.research` — spawn researcher during phase-plan (default: `true`)
- `workflow.plan_check` — spawn plan checker during phase-plan (default: `true`)
- `workflow.verifier` — spawn verifier during phase-execute (default: `true`)

**Detect missing keys:**

Check if these keys exist in config.json:
- `commit_docs`
- `pr_workflow`
- `display.statusline`

If any are missing, note them for step 3.

## 3. Present Settings (Including New Options)

**If missing keys were detected:**

Display notification:
```
⚠️  New config options available: {list missing keys}
   Adding these to your settings...
```

Use AskUserQuestion with current values shown:

```
AskUserQuestion([
  {
    question: "Which model profile for agents?",
    header: "Model",
    multiSelect: false,
    options: [
      { label: "Quality", description: "Opus everywhere exc