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.
If worktree was just enabled (changed from false to true):
# setup-worktrees.sh requires a clean working tree.# Commit all pending config changes first.
git add .planning/config.json 2>/dev/null
git commit -m "chore: update kata settings" 2>/dev/null || true# Run setup after committingif ! bash scripts/setup-worktrees.sh; thenecho"Error: Worktree setup failed. Reverting worktree.enabled to false."
node scripts/kata-lib.cjs set-config "worktree.enabled""false"fi
The settings flow continues regardless of setup outcome (non-fatal).
After successful worktree setup, inform the user:
Worktree layout created. main/ is now your project root. Restart Claude Code from inside main/ to continue working. All skills, git commands, and file edits run from main/.
If worktree was just disabled (changed from true to false):
Inform the user:
Worktree isolation disabled. Phase execution will run all plans in the shared working directory. The bare repo layout is preserved — continue working from main/.
If commit_docs changed to false:
Add .planning/ to .gitignore (create if needed)
Note: User should run git rm -r --cached .planning/ if already tracked
5. Confirm Changes
Display:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Kata > SETTINGS UPDATED
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
**Session Settings** (config.json)
| Setting | Value |
| ------------------ | ------------------------- |
| Model Profile | {quality/balanced/budget} |
| Commit Docs | {On/Off} |
| PR Workflow | {On/Off} |
| Git Worktrees | {On/Off} |
| Plan Researcher | {On/Off} |
| Plan Checker | {On/Off} |
| Execution Verifier | {On/Off} |
**Workflow Variants** (config.json)
| Setting | Value |
| ------------------------- | --------------- |
| Post-task Command | {value or none} |
| Commit Style | {value} |
| Commit Scope Format | {value} |
| Extra Verification Cmds | {value or none} |
| Version Files | {value or auto} |
| Pre-release Commands | {value or none} |
These settings apply to future /kata-plan-phase and /kata-execute-phase runs.
Quick commands:
/kata-set-profile - switch model profile
/kata-plan-phase --research - force research
/kata-plan-phase --skip-research - skip research
/kata-plan-phase --skip-verify - skip plan check
If PR Workflow was just enabled (changed from Off to On), append:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
RECOMMENDED: Enable Branch Protection
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
PR workflow is enabled. Protect your main branch:
https://github.com/{owner}/{repo}/settings/branches
Settings for `main`:
- Require a pull request before merging
- Do not allow bypassing the above settings
- Allow force pushes (uncheck)
This ensures ALL changes go through PRs.
<success_criteria>
Current config read via kata-lib.cjs read-pref (no inline grep/cat parsing)
User presented with 2 config sections: session settings, workflow variants
Config written via kata-lib.cjs set-config (no inline node JSON manipulation for config.json)
.gitignore updated if commit_docs set to false
Changes confirmed to user with two-section display
</success_criteria>
