Phase-Level Worktrees — main/ stays on the main branch permanently:

• Workspace architecture — Persistent workspace/ as working directory, main/ as read-only reference
• Phase worktrees — Phase execution creates a worktree instead of switching main/ off main
• Two-tier model — Plan worktrees fork from phase branch, merge back to phase worktree
• Worktree-safe merges — All merge patterns updated to work with bare repo layout

Optional plan-level agent isolation during phase execution:

• Config foundation — worktree.enabled setting with read-config.sh for nested JSON keys
• Worktree lifecycle — manage-worktree.sh creates isolated worktrees per plan, merges after wave completion
• Wave-based execution — Each plan agent gets its own branch and working directory
• Graceful fallback — When disabled (default), execution uses shared-directory model

Customize how Kata generates planning artifacts:

• Template customization — /kata-customize to list, copy, edit, and validate template overrides
• Universal resolution — Templates resolve via sibling discovery, working identically for plugin and skills-only users
• Schema validation — Required field checks r...