kata-configure-settings

What this skill does

<objective>
Allow users to configure all Kata settings through a single skill: session settings and workflow variants.

Updates `.planning/config.json` using accessor scripts.
</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 Values via Accessor Scripts

```bash
# Session settings
MODE=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "mode" "yolo")
DEPTH=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "depth" "standard")
MODEL_PROFILE=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "model_profile" "balanced")
COMMIT_DOCS=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "commit_docs" "true")
PR_WORKFLOW=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "pr_workflow" "false")
RESEARCH=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "workflow.research" "true")
PLAN_CHECK=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "workflow.plan_check" "true")
VERIFIER=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "workflow.verifier" "true")
WORKTREE_ENABLED=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "worktree.enabled" "false")
PR_WORKFLOW_VAL=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "pr_workflow" "false")

# Workflow variants
EXEC_POST_TASK=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "workflows.execute-phase.post_task_command" "")
EXEC_COMMIT_STYLE=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "workflows.execute-phase.commit_style" "conventional")
EXEC_SCOPE_FMT=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "workflows.execute-phase.commit_scope_format" "{phase}-{plan}")
VERIFY_EXTRA_CMDS=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "workflows.verify-work.extra_verification_commands" "[]")
MILESTONE_VERSION_FILES=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "workflows.complete-milestone.version_files" "[]")
MILESTONE_PRE_RELEASE=$(node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" read-pref "workflows.complete-milestone.pre_release_commands" "[]")
```

## 3. Present Settings in Two Sections

Present each section to the user via AskUserQuestion. Pre-select current values.

### Section A: Session Settings (config.json)

```
AskUserQuestion([
  {
    question: "Which model profile for agents?",
    header: "Model Profile",
    multiSelect: false,
    options: [
      { label: "Quality", description: "Opus everywhere except verification (highest cost)" },
      { label: "Balanced (Recommended)", description: "Opus for planning, Sonnet for execution/verification" },
      { label: "Budget", description: "Sonnet for writing, Haiku for research/verification (lowest cost)" }
    ]
  },
  {
    question: "Commit planning docs to git?",
    header: "Commit Docs",
    multiSelect: false,
    options: [
      { label: "Yes (Recommended)", description: "Track planning artifacts in git history" },
      { label: "No", description: "Keep planning private (add .planning/ to .gitignore)" }
    ]
  },
  {
    question: "Use PR-based release workflow?",
    header: "PR Workflow",
    multiSelect: false,
    options: [
      { label: "Yes (Recommended)", description: "Protect main, create PRs, tag via GitHub Release" },
      { label: "No", description: "Commit directly to main, create tags locally" }
    ]
  },
  // If PR_WORKFLOW_VAL = "true", include the Git Worktrees question:
  {
    question: "Enable git worktree isolation per plan?",
    header: "Git Worktrees",
    multiSelect: false,
    options: [
      { label: "Yes (Recommended)", description: "Each plan gets isolated worktree and branch" },
      { label: "No", description: "Plans share the working directory (standard)" }
    ]
  },
  // If PR_WORKFLOW_VAL = "false", omit the Git Worktrees question entirely.
  <!-- If pr_workflow is false, skip Git Worktrees question — worktrees require PR workflow -->
  {
    question: "Spawn Plan Researcher? (researches domain before planning)",
    header: "Research",
    multiSelect: false,
    options: [
      { label: "Yes", description: "Research phase goals before planning" },
      { label: "No", description: "Skip research, plan directly" }
    ]
  },
  {
    question: "Spawn Plan Checker? (verifies plans before execution)",
    header: "Plan Check",
    multiSelect: false,
    options: [
      { label: "Yes", description: "Verify plans meet phase goals" },
      { label: "No", description: "Skip plan verification" }
    ]
  },
  {
    question: "Spawn Execution Verifier? (verifies phase completion)",
    header: "Verifier",
    multiSelect: false,
    options: [
      { label: "Yes", description: "Verify must-haves after execution" },
      { label: "No", description: "Skip post-execution verification" }
    ]
  }
])
```

### Section B: Workflow Variants (config.json workflows section)

Present workflow variant settings. For text inputs, show current value and ask if user wants to change.

```
AskUserQuestion([
  {
    question: "Commit style for execute-phase?",
    header: "Commit Style",
    multiSelect: false,
    options: [
      { label: "conventional", description: "Conventional Commits (default)" },
      { label: "semantic", description: "Semantic commit messages" },
      { label: "simple", description: "Plain descriptive messages" }
    ]
  }
])
```

For the remaining text-input workflow variant settings, display current values and ask user:

```
Current workflow variant settings:

| Setting                 | Current Value                         |
| ----------------------- | ------------------------------------- |
| Post-task Command       | {EXEC_POST_TASK or "none"}            |
| Commit Scope Format     | {EXEC_SCOPE_FMT}                      |
| Extra Verification Cmds | {VERIFY_EXTRA_CMDS or "none"}         |
| Version Files           | {MILESTONE_VERSION_FILES or "auto"}   |
| Pre-release Commands    | {MILESTONE_PRE_RELEASE or "none"}     |

Enter new values or press Enter to keep current.
```

Use AskUserQuestion to confirm whether the user wants to change any text-input values. If yes, collect new values.

## 4. Write Updates

### Session Settings (via kata-lib.cjs set-config)

```bash
node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" set-config "mode" "$NEW_MODE"
node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" set-config "depth" "$NEW_DEPTH"
node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" set-config "model_profile" "$NEW_MODEL_PROFILE"
node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" set-config "commit_docs" "$NEW_COMMIT_DOCS"
node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" set-config "pr_workflow" "$NEW_PR_WORKFLOW"
node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" set-config "worktree.enabled" "$NEW_WORKTREE_ENABLED"
node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" set-config "workflow.research" "$NEW_RESEARCH"
node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" set-config "workflow.plan_check" "$NEW_PLAN_CHECK"
node "${CLAUDE_PLUGIN_ROOT}/skills/kata-configure-settings/scripts/kata-lib.cjs" set-config "workflow.verifier" "$NEW_VERIFIER"
```

### Workflow Varia