# Kata Configure Settings > Configure kata session settings and workflow variants. Triggers include "settings", "configure", "preferences", "workflow config", "workflow variants". - Skill: `gannonh-kata-skills/kata-configure-settings` (Agent Skill, multi-file: 3 files) - Install (CLI): `npx skillmds@latest add gannonh-kata-skills/kata-configure-settings` - Raw SKILL.md: https://api.skillmd.com/api/skills/gannonh-kata-skills/kata-configure-settings/raw - Safety review: pending - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: Productivity - Author: gannonh (https://skillmd.com/u/gannonh-kata-skills) - Updated: 2026-09-10 - Page: https://skillmd.com/skills/gannonh-kata-skills/kata-configure-settings --- Allow users to configure all Kata settings through a single skill: session settings and workflow variants. Updates `.planning/config.json` using accessor scripts. ## 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 scripts/kata-lib.cjs read-pref "mode" "yolo") DEPTH=$(node scripts/kata-lib.cjs read-pref "depth" "standard") MODEL_PROFILE=$(node scripts/kata-lib.cjs read-pref "model_profile" "balanced") COMMIT_DOCS=$(node scripts/kata-lib.cjs read-pref "commit_docs" "true") PR_WORKFLOW=$(node scripts/kata-lib.cjs read-pref "pr_workflow" "false") RESEARCH=$(node scripts/kata-lib.cjs read-pref "workflow.research" "true") PLAN_CHECK=$(node scripts/kata-lib.cjs read-pref "workflow.plan_check" "true") VERIFIER=$(node scripts/kata-lib.cjs read-pref "workflow.verifier" "true") WORKTREE_ENABLED=$(node scripts/kata-lib.cjs read-pref "worktree.enabled" "false") PR_WORKFLOW_VAL=$(node scripts/kata-lib.cjs read-pref "pr_workflow" "false") # Workflow variants EXEC_POST_TASK=$(node scripts/kata-lib.cjs read-pref "workflows.execute-phase.post_task_command" "") EXEC_COMMIT_STYLE=$(node scripts/kata-lib.cjs read-pref "workflows.execute-phase.commit_style" "conventional") EXEC_SCOPE_FMT=$(node scripts/kata-lib.cjs read-pref "workflows.execute-phase.commit_scope_format" "{phase}-{plan}") VERIFY_EXTRA_CMDS=$(node scripts/kata-lib.cjs read-pref "workflows.verify-work.extra_verification_commands" "[]") MILESTONE_VERSION_FILES=$(node scripts/kata-lib.cjs read-pref "workflows.complete-milestone.version_files" "[]") MILESTONE_PRE_RELEASE=$(node 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. { 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 scripts/kata-lib.cjs set-config "mode" "$NEW_MODE" node scripts/kata-lib.cjs set-config "depth" "$NEW_DEPTH" node scripts/kata-lib.cjs set-config "model_profile" "$NEW_MODEL_PROFILE" node scripts/kata-lib.cjs set-config "commit_docs" "$NEW_COMMIT_DOCS" node scripts/kata-lib.cjs set-config "pr_workflow" "$NEW_PR_WORKFLOW" node scripts/kata-lib.cjs set-config "worktree.enabled" "$NEW_WORKTREE_ENABLED" node scripts/kata-lib.cjs set-config "workflow.research" "$NEW_RESEARCH" node scripts/kata-lib.cjs set-config "workflow.plan_check" "$NEW_PLAN_CHECK" node scripts/kata-lib.cjs set-config "workflow.verifier" "$NEW_VERIFIER" ``` ### Workflow Variants (via kata-lib.cjs set-config) ```bash node scripts/kata-lib.cjs set-config "workflows.execute-phase.post_task_command" "$NEW_POST_TASK_CMD" node scripts/kata-lib.cjs set-config "workflows.execute-phase.commit_style" "$NEW_COMMIT_STYLE" node scripts/kata-lib.cjs set-config "workflows.execute-phase.commit_scope_format" "$NEW_SCOPE_FMT" node scripts/kata-lib.cjs set-config "workflows.verify-work.extra_verification_commands" "$NEW_EXTRA_CMDS" node scripts/kata-lib.cjs set-config "workflows.complete-milestone.version_files" "$NEW_VERSION_FILES" node scripts/kata-lib.cjs set-config "workflows.complete-milestone.pre_release_commands" "$NEW_PRE_RELEASE" ``` ## Side-Effects **If worktree was just enabled (changed from false to true):** ```bash # 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 committing if ! bash scripts/setup-worktrees.sh; then echo "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. ``` - [ ] 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