@gannonh/kata 0.1.5 → 0.1.7

package/README.md

@@ -28,6 +28,27 @@ npx @gannonh/kata
 
 ---
 
+## Talk to It Like a Person
+
+Drive your entire workflow with **natural language**. 🗣️
+
+No memorizing commands. No syntax. Just say what you want:
+
+| You say...               | Kata does...                           |
+| ------------------------ | -------------------------------------- |
+| "Start a new project"    | Launches full project initialization   |
+| "What's the status?"     | Shows progress, next steps, blockers   |
+| "Plan phase 2"           | Researches and creates execution plans |
+| "Execute the phase"      | Runs all plans with parallel agents    |
+| "I'm done for today"     | Creates handoff for session resumption |
+| "Debug this login issue" | Spawns systematic debugging workflow   |
+
+Every workflow responds to natural language. Slash commands exist for precision when you want them (`/kata:plan-phase 2`), but you never *need* them.
+
+**This isn't autocomplete. It's intent recognition.** Kata understands what you're trying to accomplish and routes to the right workflow — research, planning, execution, verification — automatically.
+
+---
+
 ## Who This Is For
 
 Teams and individuals that want to describe what they want and have it built correctly.
@@ -137,8 +158,9 @@ If you prefer not to use that flag, add this to your project's `.claude/settings
 ### 1. Initialize Project
 
 ```
-/kata:new-project
+"Start a new project"
 ```
+<sub>or `/kata:new-project`</sub>
 
 One command, one flow. The system:
 
@@ -156,8 +178,9 @@ You approve the roadmap. Now you're ready to build.
 ### 2. Discuss Phase
 
 ```
-/kata:discuss-phase 1
+"Let's discuss phase 1"
 ```
+<sub>or `/kata:discuss-phase 1`</sub>
 
 **This is where you shape the implementation.**
 
@@ -184,8 +207,9 @@ The deeper you go here, the more the system builds what you actually want. Skip
 ### 3. Plan Phase
 
 ```
-/kata:plan-phase 1
+"Plan phase 1"
 ```
+<sub>or `/kata:plan-phase 1`</sub>
 
 The system:
 
@@ -202,8 +226,9 @@ Each plan is small enough to execute in a fresh context window. No degradation,
 ### 4. Execute Phase
 
 ```
-/kata:execute-phase 1
+"Execute phase 1"
 ```
+<sub>or `/kata:execute-phase 1`</sub>
 
 The system:
 
@@ -221,8 +246,9 @@ Walk away, come back to completed work with clean git history.
 ### 5. Verify Work
 
 ```
-/kata:verify-work 1
+"Verify phase 1"
 ```
+<sub>or `/kata:verify-work 1`</sub>
 
 **This is where you confirm it actually works.**
 
@@ -244,13 +270,13 @@ If everything passes, you move on. If something's broken, you don't manually deb
 ### 6. Repeat → Complete → Next Milestone
 
 ```
-/kata:discuss-phase 2
-/kata:plan-phase 2
-/kata:execute-phase 2
-/kata:verify-work 2
+"Discuss phase 2"
+"Plan phase 2"
+"Execute phase 2"
+"Verify phase 2"
 ...
-/kata:complete-milestone
-/kata:new-milestone
+"Complete the milestone"
+"Start the next milestone"
 ```
 
 Loop **discuss → plan → execute → verify** until milestone complete.
@@ -266,8 +292,9 @@ Then `/kata:new-milestone` starts the next version — same flow as `new-project
 ### Quick Mode
 
 ```
-/kata:quick
+"Quick task: add dark mode toggle"
 ```
+<sub>or `/kata:quick`</sub>
 
 **For ad-hoc tasks that don't need full planning.**
 
@@ -373,10 +400,12 @@ You're never locked in. The system adapts.
 
 ## Commands
 
+> **Remember:** All commands also respond to natural language. "What's my progress?" works the same as `/kata:progress`.
+
 ### Core Workflow
 
-| Command                     | What it does                                                       |
-| --------------------------- | ------------------------------------------------------------------ |
+| Command                      | What it does                                                       |
+| ---------------------------- | ------------------------------------------------------------------ |
 | `/kata:new-project`          | Full initialization: questions → research → requirements → roadmap |
 | `/kata:discuss-phase [N]`    | Capture implementation decisions before planning                   |
 | `/kata:plan-phase [N]`       | Research + plan + verify for a phase                               |
@@ -388,23 +417,23 @@ You're never locked in. The system adapts.
 
 ### Navigation
 
-| Command          | What it does                                  |
-| ---------------- | --------------------------------------------- |
+| Command           | What it does                                  |
+| ----------------- | --------------------------------------------- |
 | `/kata:progress`  | Where am I? What's next?                      |
 | `/kata:help`      | Show all commands and usage guide             |
 | `/kata:whats-new` | See what changed since your installed version |
-| `/kata:update`    | Update Kata with changelog preview             |
+| `/kata:update`    | Update Kata with changelog preview            |
 
 ### Brownfield
 
-| Command             | What it does                                 |
-| ------------------- | -------------------------------------------- |
+| Command              | What it does                                 |
+| -------------------- | -------------------------------------------- |
 | `/kata:map-codebase` | Analyze existing codebase before new-project |
 
 ### Phase Management
 
-| Command                           | What it does                                   |
-| --------------------------------- | ---------------------------------------------- |
+| Command                            | What it does                                   |
+| ---------------------------------- | ---------------------------------------------- |
 | `/kata:add-phase`                  | Append phase to roadmap                        |
 | `/kata:insert-phase [N]`           | Insert urgent work between phases              |
 | `/kata:remove-phase [N]`           | Remove future phase, renumber                  |
@@ -413,21 +442,21 @@ You're never locked in. The system adapts.
 
 ### Session
 
-| Command            | What it does                           |
-| ------------------ | -------------------------------------- |
+| Command             | What it does                           |
+| ------------------- | -------------------------------------- |
 | `/kata:pause-work`  | Create handoff when stopping mid-phase |
 | `/kata:resume-work` | Restore from last session              |
 
 ### Utilities
 
-| Command                      | What it does                                   |
-| ---------------------------- | ---------------------------------------------- |
+| Command                       | What it does                                   |
+| ----------------------------- | ---------------------------------------------- |
 | `/kata:settings`              | Configure model profile and workflow agents    |
 | `/kata:set-profile <profile>` | Switch model profile (quality/balanced/budget) |
 | `/kata:add-todo [desc]`       | Capture idea for later                         |
 | `/kata:check-todos`           | List pending todos                             |
 | `/kata:debug [desc]`          | Systematic debugging with persistent state     |
-| `/kata:quick`                 | Execute ad-hoc task with Kata guarantees        |
+| `/kata:quick`                 | Execute ad-hoc task with Kata guarantees       |
 
 <sup>¹ Contributed by reddit user OracleGreyBeard</sup>
 
@@ -531,4 +560,6 @@ MIT License. See [LICENSE](LICENSE) for details.
 
 **Claude Code is powerful. Kata makes it reliable.**
 
+*Just tell it what you want.*
+
 </div>

package/bin/install.js

@@ -410,17 +410,34 @@ function install(isGlobal) {
     }
   }
 
-  // Copy hooks
+  // Copy hooks (recursively to handle subdirectories like dist/)
   const hooksSrc = path.join(src, 'hooks');
   if (fs.existsSync(hooksSrc)) {
     const hooksDest = path.join(claudeDir, 'hooks');
+    // Clean install: remove existing to prevent orphaned files
+    if (fs.existsSync(hooksDest)) {
+      fs.rmSync(hooksDest, { recursive: true });
+    }
     fs.mkdirSync(hooksDest, { recursive: true });
-    const hookEntries = fs.readdirSync(hooksSrc);
-    for (const entry of hookEntries) {
-      const srcFile = path.join(hooksSrc, entry);
-      const destFile = path.join(hooksDest, entry);
-      fs.copyFileSync(srcFile, destFile);
+
+    function copyHooksRecursive(srcDir, destDir) {
+      const entries = fs.readdirSync(srcDir, { withFileTypes: true });
+      for (const entry of entries) {
+        // Skip dist/ directory - it's for npm publishing only
+        if (entry.name === 'dist') continue;
+
+        const srcPath = path.join(srcDir, entry.name);
+        const destPath = path.join(destDir, entry.name);
+        if (entry.isDirectory()) {
+          fs.mkdirSync(destPath, { recursive: true });
+          copyHooksRecursive(srcPath, destPath);
+        } else {
+          fs.copyFileSync(srcPath, destPath);
+        }
+      }
     }
+
+    copyHooksRecursive(hooksSrc, hooksDest);
     if (verifyInstalled(hooksDest, 'hooks')) {
       console.log(`  ${green}✓${reset} Installed hooks`);
     } else {

package/kata/references/planning-config.md

@@ -1,21 +1,58 @@
 <planning_config>
 
-Configuration options for `.planning/` directory behavior.
+Configuration options for Kata projects in `.planning/config.json`.
 
 <config_schema>
+
+**Full schema:**
+
 ```json
-"planning": {
-  "commit_docs": true,
-  "search_gitignored": false
+{
+  "mode": "yolo|interactive",
+  "depth": "quick|standard|comprehensive",
+  "parallelization": true|false,
+  "model_profile": "quality|balanced|budget",
+  "commit_docs": true|false,
+  "pr_workflow": true|false,
+  "workflow": {
+    "research": true|false,
+    "plan_check": true|false,
+    "verifier": true|false
+  }
 }
 ```
 
 | Option | Default | Description |
 |--------|---------|-------------|
+| `mode` | `yolo` | `yolo` = auto-approve, `interactive` = confirm at each step |
+| `depth` | `standard` | `quick` (3-5 phases), `standard` (5-8), `comprehensive` (8-12) |
+| `parallelization` | `true` | Run independent plans simultaneously |
+| `model_profile` | `balanced` | Which AI models for agents (see model-profiles.md) |
 | `commit_docs` | `true` | Whether to commit planning artifacts to git |
-| `search_gitignored` | `false` | Add `--no-ignore` to broad rg searches |
+| `pr_workflow` | `false` | Use PR-based release workflow vs direct commits |
+| `workflow.research` | `true` | Spawn researcher before planning each phase |
+| `workflow.plan_check` | `true` | Verify plans achieve phase goals before execution |
+| `workflow.verifier` | `true` | Confirm deliverables after phase execution |
+
 </config_schema>
 
+<reading_config>
+
+**Standard pattern for reading config values:**
+
+```bash
+# Read a string value with default
+MODEL_PROFILE=$(cat .planning/config.json 2>/dev/null | grep -o '"model_profile"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "balanced")
+
+# Read a boolean value with default
+PR_WORKFLOW=$(cat .planning/config.json 2>/dev/null | grep -o '"pr_workflow"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "false")
+
+# Read nested boolean (workflow.*)
+RESEARCH=$(cat .planning/config.json 2>/dev/null | grep -o '"research"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
+```
+
+</reading_config>
+
 <commit_docs_behavior>
 
 **When `commit_docs: true` (default):**
@@ -38,7 +75,7 @@ COMMIT_DOCS=$(cat .planning/config.json 2>/dev/null | grep -o '"commit_docs"[[:s
 git check-ignore -q .planning 2>/dev/null && COMMIT_DOCS=false
 ```
 
-**Auto-detection:** If `.planning/` is gitignored, `commit_docs` is automatically `false` regardless of config.json. This prevents git errors when users have `.planning/` in `.gitignore`.
+**Auto-detection:** If `.planning/` is gitignored, `commit_docs` is automatically `false` regardless of config.json. This prevents git errors.
 
 **Conditional git operations:**
 
@@ -51,30 +88,73 @@ fi
 
 </commit_docs_behavior>
 
-<search_behavior>
+<pr_workflow_behavior>
+
+**When `pr_workflow: false` (default):**
+- Commit directly to main branch
+- Create git tags locally after milestone completion
+- Push tags to remote when ready
+
+**When `pr_workflow: true`:**
+- Work on feature branches
+- Create PRs for phase completion
+- Create git tags via GitHub Release after merge
+- Enables GitHub Actions for CI/CD (e.g., npm publish)
+
+**Checking the config:**
+
+```bash
+PR_WORKFLOW=$(cat .planning/config.json 2>/dev/null | grep -o '"pr_workflow"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "false")
+```
+
+**Usage in kata-completing-milestones:**
+
+```bash
+if [ "$PR_WORKFLOW" = "true" ]; then
+  # Skip git tag, defer to GitHub Release
+  echo "Tag will be created via GitHub Release after merge"
+else
+  # Create tag locally
+  git tag -a v1.0.0 -m "Release v1.0.0"
+fi
+```
+
+</pr_workflow_behavior>
+
+<workflow_agents>
+
+These settings control optional agent spawning during Kata workflows:
 
-**When `search_gitignored: false` (default):**
-- Standard rg behavior (respects .gitignore)
-- Direct path searches work: `rg "pattern" .planning/` finds files
-- Broad searches skip gitignored: `rg "pattern"` skips `.planning/`
+**`workflow.research`** — Spawn kata-phase-researcher before kata-planner
+- Investigates domain, finds patterns, surfaces gotchas
+- Adds tokens/time but improves plan quality
 
-**When `search_gitignored: true`:**
-- Add `--no-ignore` to broad rg searches that should include `.planning/`
-- Only needed when searching entire repo and expecting `.planning/` matches
+**`workflow.plan_check`** — Spawn kata-plan-checker after kata-planner
+- Verifies plan actually achieves the phase goal
+- Catches gaps before execution starts
 
-**Note:** Most Kata operations use direct file reads or explicit paths, which work regardless of gitignore status.
+**`workflow.verifier`** — Spawn kata-verifier after kata-executor
+- Confirms must-haves were delivered
+- Validates phase success criteria
 
-</search_behavior>
+**Checking workflow config:**
+
+```bash
+RESEARCH=$(cat .planning/config.json 2>/dev/null | grep -o '"research"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
+PLAN_CHECK=$(cat .planning/config.json 2>/dev/null | grep -o '"plan_check"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
+VERIFIER=$(cat .planning/config.json 2>/dev/null | grep -o '"verifier"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
+```
+
+</workflow_agents>
 
 <setup_uncommitted_mode>
 
-To use uncommitted mode:
+To use uncommitted mode (keep planning private):
 
 1. **Set config:**
    ```json
-   "planning": {
-     "commit_docs": false,
-     "search_gitignored": true
+   {
+     "commit_docs": false
    }
    ```
 
@@ -91,4 +171,16 @@ To use uncommitted mode:
 
 </setup_uncommitted_mode>
 
+<updating_settings>
+
+Run `/kata:settings` to update config preferences interactively.
+
+The settings skill will:
+1. Detect any missing config keys from schema evolution
+2. Prompt for preferences on new options
+3. Preserve existing values for unchanged settings
+4. Update `.planning/config.json` with merged config
+
+</updating_settings>
+
 </planning_config>

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gannonh/kata",
-  "version": "0.1.5",
+  "version": "0.1.7",
   "type": "module",
   "description": "Spec-driven development framework for Claude Code.",
   "scripts": {

package/skills/kata-completing-milestones/SKILL.md

@@ -20,8 +20,8 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 <execution_context>
 **Load these files NOW (before proceeding):**
 
-- @~/.claude/get-shit-done/workflows/complete-milestone.md (main workflow)
-- @~/.claude/get-shit-done/templates/milestone-archive.md (archive template)
+- @~/.claude/kata/workflows/complete-milestone.md (main workflow)
+- @~/.claude/kata/templates/milestone-archive.md (archive template)
   </execution_context>
 
 <context>
@@ -145,7 +145,56 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 
    **If `PR_WORKFLOW=true`:**
 
-   Skip git tag creation. Display:
+   Skip git tag creation. Offer to create PR:
+
+   Use AskUserQuestion:
+   - header: "Create PR"
+   - question: "Would you like me to create a PR for this milestone?"
+   - options:
+     - "Yes, create PR" — Create PR to merge to main
+     - "No, I'll do it manually" — Show instructions only
+
+   **If "Yes, create PR":**
+
+   ```bash
+   # Get current branch
+   CURRENT_BRANCH=$(git branch --show-current)
+
+   # Push branch if not already pushed
+   git push -u origin "$CURRENT_BRANCH" 2>/dev/null || true
+
+   # Create PR
+   gh pr create \
+     --title "v{{version}}: [Milestone Name]" \
+     --body "$(cat <<'EOF'
+   ## Summary
+
+   Completes milestone v{{version}}.
+
+   **Key accomplishments:**
+   - [accomplishment 1]
+   - [accomplishment 2]
+   - [accomplishment 3]
+
+   ## After Merge
+
+   Create GitHub Release with tag `v{{version}}` to trigger npm publish (if configured).
+   EOF
+   )"
+   ```
+
+   Display PR URL and next steps:
+   ```
+   ✓ PR created: [PR URL]
+
+   After merge:
+   → Create GitHub Release with tag v{{version}}
+   → GitHub Actions will publish to npm (if configured)
+   ```
+
+   **If "No, I'll do it manually":**
+
+   Display:
    ```
    ⚡ PR workflow mode — tag will be created via GitHub Release after merge
 
@@ -173,7 +222,7 @@ Output: Milestone archived (roadmap + requirements), PROJECT.md evolved, git tag
 - `.planning/REQUIREMENTS.md` deleted (fresh for next milestone)
 - ROADMAP.md collapsed to one-line entry
 - PROJECT.md updated with current state
-- Git tag v{{version}} created (if pr_workflow=false) OR deferred to GitHub Release (if pr_workflow=true)
+- Git tag v{{version}} created (if pr_workflow=false) OR PR created/instructions given (if pr_workflow=true)
 - Commit successful
 - User knows next steps (including need for fresh requirements)
   </success_criteria>

package/skills/kata-configuring-settings/SKILL.md

@@ -14,6 +14,8 @@ allowed-tools:
 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>
@@ -26,20 +28,40 @@ ls .planning/config.json 2>/dev/null
 
 **If not found:** Error - run `/kata:new-project` first.
 
-## 2. Read Current Config
+## 2. Read Current Config and Detect Missing Keys
 
 ```bash
 cat .planning/config.json
 ```
 
-Parse current values (default to `true` if not present):
-- `workflow.research` — spawn researcher during plan-phase
-- `workflow.plan_check` — spawn plan checker during plan-phase
-- `workflow.verifier` — spawn verifier during execute-phase
+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`)
+- `workflow.research` — spawn researcher during plan-phase (default: `true`)
+- `workflow.plan_check` — spawn plan checker during plan-phase (default: `true`)
+- `workflow.verifier` — spawn verifier during execute-phase (default: `true`)
+
+**Detect missing keys:**
+
+Check if these keys exist in config.json:
+- `commit_docs`
+- `pr_workflow`
+
+If any are missing, note them for step 3.
 
-## 3. Present Settings
+## 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:
 
@@ -55,6 +77,24 @@ AskUserQuestion([
       { 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", description: "Protect main, create PRs, tag via GitHub Release" },
+      { label: "No (Recommended)", description: "Commit directly to main, create tags locally" }
+    ]
+  },
   {
     question: "Spawn Plan Researcher? (researches domain before planning)",
     header: "Research",
@@ -81,40 +121,38 @@ AskUserQuestion([
       { label: "Yes", description: "Verify must-haves after execution" },
       { label: "No", description: "Skip post-execution verification" }
     ]
-  },
-  {
-    question: "Use PR-based release workflow?",
-    header: "PR Workflow",
-    multiSelect: false,
-    options: [
-      { label: "Yes", description: "Protect main, create PRs, tag via GitHub Release" },
-      { label: "No", description: "Commit directly to main, create tags locally" }
-    ]
   }
 ])
 ```
 
-**Pre-select based on current config values.**
+**Pre-select based on current config values (use defaults for missing keys).**
 
 ## 4. Update Config
 
-Merge new settings into existing config.json:
+Merge new settings into existing config.json (preserving existing keys like `mode`, `depth`, `parallelization`):
 
 ```json
 {
-  ...existing_config,
-  "model_profile": "quality" | "balanced" | "budget",
-  "pr_workflow": true/false,
+  "mode": "yolo|interactive",
+  "depth": "quick|standard|comprehensive",
+  "parallelization": true|false,
+  "model_profile": "quality|balanced|budget",
+  "commit_docs": true|false,
+  "pr_workflow": true|false,
   "workflow": {
-    "research": true/false,
-    "plan_check": true/false,
-    "verifier": true/false
+    "research": true|false,
+    "plan_check": true|false,
+    "verifier": true|false
   }
 }
 ```
 
 Write updated config to `.planning/config.json`.
 
+**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:
@@ -127,6 +165,7 @@ Display:
 | Setting              | Value |
 |----------------------|-------|
 | Model Profile        | {quality/balanced/budget} |
+| Commit Docs          | {On/Off} |
 | PR Workflow          | {On/Off} |
 | Plan Researcher      | {On/Off} |
 | Plan Checker         | {On/Off} |
@@ -145,7 +184,8 @@ Quick commands:
 
 <success_criteria>
 - [ ] Current config read
-- [ ] User presented with 5 settings (profile + pr_workflow + 3 toggles)
-- [ ] Config updated with model_profile, pr_workflow, and workflow section
+- [ ] Missing keys detected and user notified
+- [ ] User presented with 6 settings (profile + commit_docs + pr_workflow + 3 toggles)
+- [ ] Config updated with complete schema
 - [ ] Changes confirmed to user
 </success_criteria>

package/skills/kata-discussing-phases/SKILL.md

@@ -23,8 +23,8 @@ Extract implementation decisions that downstream agents need — researcher and
 </objective>
 
 <execution_context>
-@~/.claude/get-shit-done/workflows/discuss-phase.md
-@~/.claude/get-shit-done/templates/context.md
+@~/.claude/kata/workflows/discuss-phase.md
+@~/.claude/kata/templates/context.md
 </execution_context>
 
 <context>

package/skills/kata-executing-phases/SKILL.md

@@ -19,8 +19,8 @@ Context budget: ~15% orchestrator, 100% fresh per subagent.
 </objective>
 
 <execution_context>
-@~/.claude/get-shit-done/references/ui-brand.md
-@~/.claude/get-shit-done/workflows/execute-phase.md
+@~/.claude/kata/references/ui-brand.md
+@~/.claude/kata/workflows/execute-phase.md
 </execution_context>
 
 <context>
@@ -278,7 +278,7 @@ Plans with `autonomous: false` have checkpoints. The execute-phase.md workflow h
 - Orchestrator presents to user, collects response
 - Spawns fresh continuation agent (not resume)
 
-See `@~/.claude/get-shit-done/workflows/execute-phase.md` step `checkpoint_handling` for complete details.
+See `@~/.claude/kata/workflows/execute-phase.md` step `checkpoint_handling` for complete details.
 </checkpoint_handling>
 
 <deviation_rules>

package/skills/kata-listing-phase-assumptions/SKILL.md

@@ -18,7 +18,7 @@ Output: Conversational output only (no file creation) - ends with "What do you t
 </objective>
 
 <execution_context>
-@~/.claude/get-shit-done/workflows/list-phase-assumptions.md
+@~/.claude/kata/workflows/list-phase-assumptions.md
 </execution_context>
 
 <context>

package/skills/kata-mapping-codebases/SKILL.md

@@ -19,7 +19,7 @@ Output: .planning/codebase/ folder with 7 structured documents about the codebas
 </objective>
 
 <execution_context>
-@~/.claude/get-shit-done/workflows/map-codebase.md
+@~/.claude/kata/workflows/map-codebase.md
 </execution_context>
 
 <context>

package/skills/kata-planning-phases/SKILL.md

@@ -11,7 +11,7 @@ allowed-tools:
 ---
 
 <execution_context>
-@~/.claude/get-shit-done/references/ui-brand.md
+@~/.claude/kata/references/ui-brand.md
 </execution_context>
 
 <objective>

package/skills/kata-providing-help/SKILL.md

@@ -43,7 +43,7 @@ Kata evolves fast. Check for updates periodically:
 Shows what changed since your installed version. Update with:
 
 ```bash
-npx get-shit-done-cc@latest
+npx kata-cc@latest
 ```
 
 ## Core Workflow
@@ -355,7 +355,7 @@ Update Kata to latest version with changelog preview.
 
 - Shows what changed before updating
 - Confirms before running install
-- Better than raw `npx get-shit-done-cc`
+- Better than raw `npx kata-cc`
 
 Usage: `/kata:update`
 

package/skills/kata-resuming-work/SKILL.md

@@ -23,11 +23,11 @@ Routes to the resume-project workflow which handles:
   </objective>
 
 <execution_context>
-@~/.claude/get-shit-done/workflows/resume-project.md
+@~/.claude/kata/workflows/resume-project.md
 </execution_context>
 
 <process>
-**Follow the resume-project workflow** from `@~/.claude/get-shit-done/workflows/resume-project.md`.
+**Follow the resume-project workflow** from `@~/.claude/kata/workflows/resume-project.md`.
 
 The workflow handles all resumption logic including:
 

package/skills/kata-showing-whats-new/SKILL.md

@@ -22,7 +22,7 @@ Shows version comparison, changelog entries for missed versions, and update inst
 Read installed version from VERSION file:
 
 ```bash
-cat ~/.claude/get-shit-done/VERSION 2>/dev/null
+cat ~/.claude/kata/VERSION 2>/dev/null
 ```
 
 **If VERSION file missing:**
@@ -33,7 +33,7 @@ cat ~/.claude/get-shit-done/VERSION 2>/dev/null
 
 Your installation doesn't include version tracking.
 
-**To fix:** `npx get-shit-done-cc --global`
+**To fix:** `npx @gannonh/kata --global`
 
 This will reinstall with version tracking enabled.
 ```
@@ -45,13 +45,13 @@ STOP here if no VERSION file.
 Fetch latest CHANGELOG.md from GitHub:
 
 Use WebFetch tool with:
-- URL: `https://raw.githubusercontent.com/glittercowboy/get-shit-done/main/CHANGELOG.md`
+- URL: `https://raw.githubusercontent.com/gannnonh/kata/main/CHANGELOG.md`
 - Prompt: "Extract all version entries with their dates and changes. Return in Keep-a-Changelog format."
 
 **If fetch fails:**
 Fall back to local changelog:
 ```bash
-cat ~/.claude/get-shit-done/CHANGELOG.md 2>/dev/null
+cat ~/.claude/kata/CHANGELOG.md 2>/dev/null
 ```
 
 Note to user: "Couldn't check for updates (offline or GitHub unavailable). Showing local changelog."
@@ -82,7 +82,7 @@ Format output clearly:
 
 You're on the latest version.
 
-[View full changelog](https://github.com/glittercowboy/get-shit-done/blob/main/CHANGELOG.md)
+[View full changelog](https://github.com/gannnonh/kata/blob/main/CHANGELOG.md)
 ```
 
 **If updates available:**
@@ -112,9 +112,9 @@ You're on the latest version.
 
 ---
 
-[View full changelog](https://github.com/glittercowboy/get-shit-done/blob/main/CHANGELOG.md)
+[View full changelog](https://github.com/gannnonh/kata/blob/main/CHANGELOG.md)
 
-**To update:** `npx get-shit-done-cc --global`
+**To update:** `npx @gannonh/kata --global`
 ```
 
 **Breaking changes:** Surface prominently with **BREAKING:** prefix in the output.

package/skills/kata-starting-milestones/SKILL.md

@@ -28,10 +28,10 @@ This is the brownfield equivalent of new-project. The project exists, PROJECT.md
 </objective>
 
 <execution_context>
-@~/.claude/get-shit-done/references/questioning.md
-@~/.claude/get-shit-done/references/ui-brand.md
-@~/.claude/get-shit-done/templates/project.md
-@~/.claude/get-shit-done/templates/requirements.md
+@~/.claude/kata/references/questioning.md
+@~/.claude/kata/references/ui-brand.md
+@~/.claude/kata/templates/project.md
+@~/.claude/kata/templates/requirements.md
 </execution_context>
 
 <context>
@@ -218,7 +218,7 @@ Your STACK.md feeds into roadmap creation. Be prescriptive:
 
 <output>
 Write to: .planning/research/STACK.md
-Use template: ~/.claude/get-shit-done/templates/research-project/STACK.md
+Use template: ~/.claude/kata/templates/research-project/STACK.md
 </output>
 ", subagent_type="kata-project-researcher", model="{researcher_model}", description="Stack research")
 
@@ -259,7 +259,7 @@ Your FEATURES.md feeds into requirements definition. Categorize clearly:
 
 <output>
 Write to: .planning/research/FEATURES.md
-Use template: ~/.claude/get-shit-done/templates/research-project/FEATURES.md
+Use template: ~/.claude/kata/templates/research-project/FEATURES.md
 </output>
 ", subagent_type="kata-project-researcher", model="{researcher_model}", description="Features research")
 
@@ -301,7 +301,7 @@ Your ARCHITECTURE.md informs phase structure in roadmap. Include:
 
 <output>
 Write to: .planning/research/ARCHITECTURE.md
-Use template: ~/.claude/get-shit-done/templates/research-project/ARCHITECTURE.md
+Use template: ~/.claude/kata/templates/research-project/ARCHITECTURE.md
 </output>
 ", subagent_type="kata-project-researcher", model="{researcher_model}", description="Architecture research")
 
@@ -339,7 +339,7 @@ Your PITFALLS.md prevents mistakes in roadmap/planning. For each pitfall:
 
 <output>
 Write to: .planning/research/PITFALLS.md
-Use template: ~/.claude/get-shit-done/templates/research-project/PITFALLS.md
+Use template: ~/.claude/kata/templates/research-project/PITFALLS.md
 </output>
 ", subagent_type="kata-project-researcher", model="{researcher_model}", description="Pitfalls research")
 ```
@@ -362,7 +362,7 @@ Read these files:
 
 <output>
 Write to: .planning/research/SUMMARY.md
-Use template: ~/.claude/get-shit-done/templates/research-project/SUMMARY.md
+Use template: ~/.claude/kata/templates/research-project/SUMMARY.md
 Commit after writing.
 </output>
 ", subagent_type="kata-research-synthesizer", model="{synthesizer_model}", description="Synthesize research")

package/skills/kata-starting-projects/SKILL.md

@@ -32,10 +32,10 @@ This is the most leveraged moment in any project. Deep questioning here means be
 
 <execution_context>
 
-@~/.claude/get-shit-done/references/questioning.md
-@~/.claude/get-shit-done/references/ui-brand.md
-@~/.claude/get-shit-done/templates/project.md
-@~/.claude/get-shit-done/templates/requirements.md
+@~/.claude/kata/references/questioning.md
+@~/.claude/kata/references/ui-brand.md
+@~/.claude/kata/templates/project.md
+@~/.claude/kata/templates/requirements.md
 
 </execution_context>
 
@@ -286,8 +286,8 @@ questions: [
     question: "Use PR-based release 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" }
+      { label: "Yes", description: "Protect main, create PRs, tag via GitHub Release" },
+      { label: "No (Recommended)", description: "Commit directly to main, create tags locally" }
     ]
   }
 ]
@@ -389,6 +389,137 @@ EOF
 
 **Note:** Run `/kata:settings` anytime to update these preferences.
 
+**If pr_workflow = Yes:**
+
+Ask about GitHub Actions release workflow:
+
+```
+AskUserQuestion([
+  {
+    header: "GitHub Actions",
+    question: "Scaffold a GitHub Actions workflow to auto-publish on release?",
+    multiSelect: false,
+    options: [
+      { label: "Yes (Recommended)", description: "Create .github/workflows/release.yml for npm publish" },
+      { label: "No", description: "I'll set up CI/CD myself" }
+    ]
+  }
+])
+```
+
+**If "Yes":**
+
+Create `.github/workflows/release.yml`:
+
+```bash
+mkdir -p .github/workflows
+```
+
+Write the workflow file:
+
+```yaml
+name: Publish to npm
+
+on:
+  push:
+    branches:
+      - main
+
+jobs:
+  publish:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: '20'
+          registry-url: 'https://registry.npmjs.org'
+
+      - name: Get package info
+        id: package
+        run: |
+          LOCAL_VERSION=$(node -p "require('./package.json').version")
+          PACKAGE_NAME=$(node -p "require('./package.json').name")
+          echo "local_version=$LOCAL_VERSION" >> $GITHUB_OUTPUT
+          echo "package_name=$PACKAGE_NAME" >> $GITHUB_OUTPUT
+
+          # Get published version (returns empty if not published)
+          PUBLISHED_VERSION=$(npm view "$PACKAGE_NAME" version 2>/dev/null || echo "")
+          echo "published_version=$PUBLISHED_VERSION" >> $GITHUB_OUTPUT
+
+          echo "Local version: $LOCAL_VERSION"
+          echo "Published version: $PUBLISHED_VERSION"
+
+      - name: Check if should publish
+        id: check
+        run: |
+          LOCAL="${{ steps.package.outputs.local_version }}"
+          PUBLISHED="${{ steps.package.outputs.published_version }}"
+
+          if [ -z "$PUBLISHED" ]; then
+            echo "Package not yet published, will publish"
+            echo "should_publish=true" >> $GITHUB_OUTPUT
+          elif [ "$LOCAL" != "$PUBLISHED" ]; then
+            echo "Version changed ($PUBLISHED -> $LOCAL), will publish"
+            echo "should_publish=true" >> $GITHUB_OUTPUT
+          else
+            echo "Version unchanged ($LOCAL), skipping publish"
+            echo "should_publish=false" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Publish to npm
+        if: steps.check.outputs.should_publish == 'true'
+        run: npm publish --access public
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+
+      - name: Create GitHub Release
+        if: steps.check.outputs.should_publish == 'true'
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: v${{ steps.package.outputs.local_version }}
+          name: v${{ steps.package.outputs.local_version }}
+          generate_release_notes: true
+          make_latest: true
+```
+
+Commit the workflow:
+
+```bash
+git add .github/workflows/release.yml
+git commit -m "$(cat <<'EOF'
+ci: add npm publish workflow
+
+Publishes to npm and creates GitHub Release when:
+- Push to main
+- package.json version differs from published version
+
+Requires NPM_TOKEN secret in repository settings.
+EOF
+)"
+```
+
+Display setup instructions:
+
+```
+✓ Created .github/workflows/release.yml
+
+## Setup Required
+
+Add NPM_TOKEN secret to your GitHub repository:
+1. Go to repo Settings → Secrets and variables → Actions
+2. Click "New repository secret"
+3. Name: NPM_TOKEN
+4. Value: Your npm access token (from npmjs.com → Access Tokens)
+
+The workflow will auto-publish when you merge PRs that bump package.json version.
+```
+
 ## Phase 5.5: Resolve Model Profile
 
 Read model profile for agent spawning:
@@ -487,7 +618,7 @@ Your STACK.md feeds into roadmap creation. Be prescriptive:
 
 <output>
 Write to: .planning/research/STACK.md
-Use template: ~/.claude/get-shit-done/templates/research-project/STACK.md
+Use template: ~/.claude/kata/templates/research-project/STACK.md
 </output>
 ", subagent_type="kata-project-researcher", model="{researcher_model}", description="Stack research")
 
@@ -526,7 +657,7 @@ Your FEATURES.md feeds into requirements definition. Categorize clearly:
 
 <output>
 Write to: .planning/research/FEATURES.md
-Use template: ~/.claude/get-shit-done/templates/research-project/FEATURES.md
+Use template: ~/.claude/kata/templates/research-project/FEATURES.md
 </output>
 ", subagent_type="kata-project-researcher", model="{researcher_model}", description="Features research")
 
@@ -565,7 +696,7 @@ Your ARCHITECTURE.md informs phase structure in roadmap. Include:
 
 <output>
 Write to: .planning/research/ARCHITECTURE.md
-Use template: ~/.claude/get-shit-done/templates/research-project/ARCHITECTURE.md
+Use template: ~/.claude/kata/templates/research-project/ARCHITECTURE.md
 </output>
 ", subagent_type="kata-project-researcher", model="{researcher_model}", description="Architecture research")
 
@@ -604,7 +735,7 @@ Your PITFALLS.md prevents mistakes in roadmap/planning. For each pitfall:
 
 <output>
 Write to: .planning/research/PITFALLS.md
-Use template: ~/.claude/get-shit-done/templates/research-project/PITFALLS.md
+Use template: ~/.claude/kata/templates/research-project/PITFALLS.md
 </output>
 ", subagent_type="kata-project-researcher", model="{researcher_model}", description="Pitfalls research")
 ```
@@ -627,7 +758,7 @@ Read these files:
 
 <output>
 Write to: .planning/research/SUMMARY.md
-Use template: ~/.claude/get-shit-done/templates/research-project/SUMMARY.md
+Use template: ~/.claude/kata/templates/research-project/SUMMARY.md
 Commit after writing.
 </output>
 ", subagent_type="kata-research-synthesizer", model="{synthesizer_model}", description="Synthesize research")

package/skills/kata-updating/SKILL.md

@@ -13,7 +13,7 @@ allowed-tools:
 <objective>
 Check for Kata updates, install if available, and display what changed.
 
-Provides a better update experience than raw `npx get-shit-done-cc` by showing version diff and changelog entries.
+Provides a better update experience than raw `npx @gannonh/kata` by showing version diff and changelog entries.
 </objective>
 
 <process>
@@ -22,7 +22,7 @@ Provides a better update experience than raw `npx get-shit-done-cc` by showing v
 Read installed version:
 
 ```bash
-cat ~/.claude/get-shit-done/VERSION 2>/dev/null
+cat ~/.claude/kata/VERSION 2>/dev/null
 ```
 
 **If VERSION file missing:**
@@ -43,14 +43,14 @@ Proceed to install step (treat as version 0.0.0 for comparison).
 Check npm for latest version:
 
 ```bash
-npm view get-shit-done-cc version 2>/dev/null
+npm view kata-cc version 2>/dev/null
 ```
 
 **If npm check fails:**
 ```
 Couldn't check for updates (offline or npm unavailable).
 
-To update manually: `npx get-shit-done-cc --global`
+To update manually: `npx kata-cc --global`
 ```
 
 STOP here if npm unavailable.
@@ -114,7 +114,7 @@ STOP here if ahead.
 
 ⚠️  **Note:** The installer performs a clean install of Kata folders:
 - `~/.claude/commands/kata/` will be wiped and replaced
-- `~/.claude/get-shit-done/` will be wiped and replaced
+- `~/.claude/kata/` will be wiped and replaced
 - `~/.claude/agents/kata-*` files will be replaced
 
 Your custom files in other locations are preserved:
@@ -139,7 +139,7 @@ Use AskUserQuestion:
 Run the update:
 
 ```bash
-npx get-shit-done-cc --global
+npx kata-cc --global
 ```
 
 Capture output. If install fails, show error and STOP.
@@ -161,7 +161,7 @@ Format completion message (changelog was already shown in confirmation step):
 
 ⚠️  Restart Claude Code to pick up the new commands.
 
-[View full changelog](https://github.com/glittercowboy/get-shit-done/blob/main/CHANGELOG.md)
+[View full changelog](https://github.com/glittercowboy/kata/blob/main/CHANGELOG.md)
 ```
 </step>
 

package/skills/kata-verifying-work/SKILL.md

@@ -19,8 +19,8 @@ Output: {phase}-UAT.md tracking all test results. If issues found: diagnosed gap
 </objective>
 
 <execution_context>
-@~/.claude/get-shit-done/workflows/verify-work.md
-@~/.claude/get-shit-done/templates/UAT.md
+@~/.claude/kata/workflows/verify-work.md
+@~/.claude/kata/templates/UAT.md
 </execution_context>
 
 <context>