@gannonh/kata 1.1.0 → 1.1.1

package/agents/kata-codebase-mapper.md

@@ -8,7 +8,7 @@ color: cyan
 <role>
 You are a Kata codebase mapper. You explore a codebase for a specific focus area and write analysis documents directly to `.planning/codebase/`.
 
-You are spawned by `/kata:project-analyze` with one of four focus areas:
+You are spawned by `/kata:mapping-codebases` with one of four focus areas:
 - **tech**: Analyze technology stack and external integrations → write STACK.md and INTEGRATIONS.md
 - **arch**: Analyze architecture and file structure → write ARCHITECTURE.md and STRUCTURE.md
 - **quality**: Analyze coding conventions and testing patterns → write CONVENTIONS.md and TESTING.md
@@ -20,7 +20,7 @@ Your job: Explore thoroughly, then write document(s) directly. Return confirmati
 <why_this_matters>
 **These documents are consumed by other Kata commands:**
 
-**`/kata:phase-plan`** loads relevant codebase docs when creating implementation plans:
+**`/kata:planning-phases`** loads relevant codebase docs when creating implementation plans:
 | Phase Type                | Documents Loaded                |
 | ------------------------- | ------------------------------- |
 | UI, frontend, components  | CONVENTIONS.md, STRUCTURE.md    |
@@ -31,7 +31,7 @@ Your job: Explore thoroughly, then write document(s) directly. Return confirmati
 | refactor, cleanup         | CONCERNS.md, ARCHITECTURE.md    |
 | setup, config             | STACK.md, STRUCTURE.md          |
 
-**`/kata:phase-execute`** references codebase docs to:
+**`/kata:executing-phases`** references codebase docs to:
 - Follow existing conventions when writing code
 - Know where to place new files (STRUCTURE.md)
 - Match testing patterns (TESTING.md)
@@ -82,11 +82,11 @@ Explore the codebase thoroughly for your focus area.
 **For tech focus:**
 ```bash
 # Package manifests
-ls package.json requirements.txt Cargo.toml go.mod pyproject.toml 2>/dev/null
+(ls package.json requirements.txt Cargo.toml go.mod pyproject.toml 2>/dev/null || true) || true
 cat package.json 2>/dev/null | head -100
 
 # Config files
-ls -la *.config.* .env* tsconfig.json .nvmrc .python-version 2>/dev/null
+(ls -la *.config.* .env* tsconfig.json .nvmrc .python-version 2>/dev/null || true) || true
 
 # Find SDK/API imports
 grep -r "import.*stripe\|import.*supabase\|import.*aws\|import.*@" src/ --include="*.ts" --include="*.tsx" 2>/dev/null | head -50
@@ -98,7 +98,7 @@ grep -r "import.*stripe\|import.*supabase\|import.*aws\|import.*@" src/ --includ
 find . -type d -not -path '*/node_modules/*' -not -path '*/.git/*' | head -50
 
 # Entry points
-ls src/index.* src/main.* src/app.* src/server.* app/page.* 2>/dev/null
+(ls src/index.* src/main.* src/app.* src/server.* app/page.* 2>/dev/null || true) || true
 
 # Import patterns to understand layers
 grep -r "^import" src/ --include="*.ts" --include="*.tsx" 2>/dev/null | head -100
@@ -107,15 +107,15 @@ grep -r "^import" src/ --include="*.ts" --include="*.tsx" 2>/dev/null | head -10
 **For quality focus:**
 ```bash
 # Linting/formatting config
-ls .eslintrc* .prettierrc* eslint.config.* biome.json 2>/dev/null
-cat .prettierrc 2>/dev/null
+(ls .eslintrc* .prettierrc* eslint.config.* biome.json 2>/dev/null || true) || true
+cat .prettierrc 2>/dev/null || true
 
 # Test files and config
-ls jest.config.* vitest.config.* 2>/dev/null
+(ls jest.config.* vitest.config.* 2>/dev/null || true) || true
 find . -name "*.test.*" -o -name "*.spec.*" | head -30
 
 # Sample source files for convention analysis
-ls src/**/*.ts 2>/dev/null | head -10
+(ls src/**/*.ts 2>/dev/null || true) | head -10
 ```
 
 **For concerns focus:**

package/agents/kata-debugger.md

@@ -1,6 +1,6 @@
 ---
 name: kata-debugger
-description: Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /kata:issue-debug orchestrator.
+description: Investigates bugs using scientific method, manages debug sessions, handles checkpoints. Spawned by /kata:debugging orchestrator.
 tools: Read, Write, Edit, Bash, Grep, Glob, WebSearch
 color: orange
 ---
@@ -10,7 +10,7 @@ You are a Kata debugger. You investigate bugs using systematic scientific method
 
 You are spawned by:
 
-- `/kata:issue-debug` command (interactive debugging)
+- `/kata:debugging` command (interactive debugging)
 - `diagnose-issues` workflow (parallel UAT diagnosis)
 
 Your job: Find the root cause through hypothesis testing, maintain debug file state, optionally fix and verify (depending on mode).
@@ -826,7 +826,7 @@ The file IS the debugging brain.
 **First:** Check for active debug sessions.
 
 ```bash
-ls .planning/debug/*.md 2>/dev/null | grep -v resolved
+(ls .planning/debug/*.md 2>/dev/null || true) | grep -v resolved
 ```
 
 **If active sessions exist AND no $ARGUMENTS:**
@@ -894,7 +894,7 @@ Gather symptoms through questioning. Update file after EACH answer.
   - Otherwise -> proceed to fix_and_verify
 - **ELIMINATED:** Append to Eliminated section, form new hypothesis, return to Phase 2
 
-**Context management:** After 5+ evidence entries, ensure Current Focus is updated. Suggest "/clear - run /kata:issue-debug to resume" if context filling up.
+**Context management:** After 5+ evidence entries, ensure Current Focus is updated. Suggest "/clear - run /kata:debugging to resume" if context filling up.
 </step>
 
 <step name="resume_from_file">

package/agents/kata-entity-generator.md

@@ -79,7 +79,7 @@ For each file path:
 
 4. **Check if entity exists:**
    ```bash
-   ls .planning/intel/entities/{slug}.md 2>/dev/null
+   (ls .planning/intel/entities/{slug}.md 2>/dev/null || true) || true
    ```
    If exists, increment already_existed and skip to next file.
 

package/agents/kata-executor.md

@@ -8,7 +8,7 @@ color: yellow
 <role>
 You are a Kata plan executor. You execute PLAN.md files atomically, creating per-task commits, handling deviations automatically, pausing at checkpoints, and producing SUMMARY.md files.
 
-You are spawned by `/kata:phase-execute` orchestrator.
+You are spawned by `/kata:executing-phases` orchestrator.
 
 Your job: Execute the plan completely, commit each task, create SUMMARY.md, update STATE.md.
 </role>
@@ -19,7 +19,7 @@ Your job: Execute the plan completely, commit each task, create SUMMARY.md, upda
 Before any operation, read project state:
 
 ```bash
-cat .planning/STATE.md 2>/dev/null
+cat .planning/STATE.md 2>/dev/null || true
 ```
 
 **If file exists:** Parse and internalize:

package/agents/kata-integration-checker.md

@@ -59,7 +59,7 @@ For each phase, extract what it provides and what it should consume.
 # Key exports from each phase
 for summary in .planning/phases/*/*-SUMMARY.md; do
   echo "=== $summary ==="
-  grep -A 10 "Key Files\|Exports\|Provides" "$summary" 2>/dev/null
+  grep -A 10 "Key Files\|Exports\|Provides" "$summary" 2>/dev/null || true
 done
 ```
 
@@ -176,7 +176,7 @@ Check that routes requiring auth actually check auth.
 protected_patterns="dashboard|settings|profile|account|user"
 
 # Find components/pages matching these patterns
-grep -r -l "$protected_patterns" src/ --include="*.tsx" 2>/dev/null
+grep -r -l "$protected_patterns" src/ --include="*.tsx" 2>/dev/null || true
 ```
 
 **Check auth usage in protected areas:**

package/agents/kata-phase-researcher.md

@@ -1,6 +1,6 @@
 ---
 name: kata-phase-researcher
-description: Researches how to implement a phase before planning. Produces RESEARCH.md consumed by kata-planner. Spawned by /kata:phase-plan orchestrator.
+description: Researches how to implement a phase before planning. Produces RESEARCH.md consumed by kata-planner. Spawned by /kata:planning-phases orchestrator.
 tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, mcp__context7__*
 color: cyan
 ---
@@ -10,8 +10,8 @@ You are a Kata phase researcher. You research how to implement a specific phase
 
 You are spawned by:
 
-- `/kata:phase-plan` orchestrator (integrated research before planning)
-- `/kata:phase-research` orchestrator (standalone research)
+- `/kata:planning-phases` orchestrator (integrated research before planning)
+- `/kata:researching-phases` orchestrator (standalone research)
 
 Your job: Answer "What do I need to know to PLAN this phase well?" Produce a single RESEARCH.md file that the planner consumes immediately.
 
@@ -24,7 +24,7 @@ Your job: Answer "What do I need to know to PLAN this phase well?" Produce a sin
 </role>
 
 <upstream_input>
-**CONTEXT.md** (if exists) — User decisions from `/kata:phase-discuss`
+**CONTEXT.md** (if exists) — User decisions from `/kata:discussing-phases`
 
 | Section                  | How You Use It                                    |
 | ------------------------ | ------------------------------------------------- |
@@ -446,10 +446,10 @@ Orchestrator provides:
 ```bash
 # Match both zero-padded (05-*) and unpadded (5-*) folders
 PADDED_PHASE=$(printf "%02d" ${PHASE} 2>/dev/null || echo "${PHASE}")
-PHASE_DIR=$(ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE}-* 2>/dev/null | head -1)
+PHASE_DIR=$((ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE}-* 2>/dev/null || true) | head -1)
 
-# Read CONTEXT.md if exists (from /kata:phase-discuss)
-cat "${PHASE_DIR}"/*-CONTEXT.md 2>/dev/null
+# Read CONTEXT.md if exists (from /kata:discussing-phases)
+cat "${PHASE_DIR}"/*-CONTEXT.md 2>/dev/null || true
 
 # Check if planning docs should be committed (default: true)
 COMMIT_PLANNING_DOCS=$(cat .planning/config.json 2>/dev/null | grep -o '"commit_docs"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")

package/agents/kata-plan-checker.md

@@ -1,6 +1,6 @@
 ---
 name: kata-plan-checker
-description: Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /kata:phase-plan orchestrator.
+description: Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /kata:planning-phases orchestrator.
 tools: Read, Bash, Glob, Grep
 color: green
 ---
@@ -10,7 +10,7 @@ You are a Kata plan checker. You verify that plans WILL achieve the phase goal,
 
 You are spawned by:
 
-- `/kata:phase-plan` orchestrator (after planner creates PLAN.md files)
+- `/kata:planning-phases` orchestrator (after planner creates PLAN.md files)
 - Re-verification (after planner revises based on your feedback)
 
 Your job: Goal-backward verification of PLANS before execution. Start from what the phase SHOULD deliver, verify the plans address it.
@@ -246,16 +246,16 @@ Gather verification context from the phase directory and project state.
 ```bash
 # Normalize phase and find directory
 PADDED_PHASE=$(printf "%02d" ${PHASE_ARG} 2>/dev/null || echo "${PHASE_ARG}")
-PHASE_DIR=$(ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE_ARG}-* 2>/dev/null | head -1)
+PHASE_DIR=$((ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE_ARG}-* 2>/dev/null || true) | head -1)
 
 # List all PLAN.md files
-ls "$PHASE_DIR"/*-PLAN.md 2>/dev/null
+(ls "$PHASE_DIR"/*-PLAN.md 2>/dev/null || true) || true
 
 # Get phase goal from ROADMAP
 grep -A 10 "Phase ${PHASE_NUM}" .planning/ROADMAP.md | head -15
 
 # Get phase brief if exists
-ls "$PHASE_DIR"/*-BRIEF.md 2>/dev/null
+(ls "$PHASE_DIR"/*-BRIEF.md 2>/dev/null || true) || true
 ```
 
 **Extract:**
@@ -658,7 +658,7 @@ When all checks pass:
 
 ### Ready for Execution
 
-Plans verified. Run `/kata:phase-execute {phase}` to proceed.
+Plans verified. Run `/kata:executing-phases {phase}` to proceed.
 ```
 
 ## ISSUES FOUND

package/agents/kata-planner.md

@@ -1,6 +1,6 @@
 ---
 name: kata-planner
-description: Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /kata:phase-plan orchestrator.
+description: Creates executable phase plans with task breakdown, dependency analysis, and goal-backward verification. Spawned by /kata:planning-phases orchestrator.
 tools: Read, Write, Bash, Glob, Grep, WebFetch, mcp__context7__*
 color: green
 ---
@@ -10,9 +10,9 @@ You are a Kata planner. You create executable phase plans with task breakdown, d
 
 You are spawned by:
 
-- `/kata:phase-plan` orchestrator (standard phase planning)
-- `/kata:phase-plan --gaps` orchestrator (gap closure planning from verification failures)
-- `/kata:phase-plan` orchestrator in revision mode (updating plans based on checker feedback)
+- `/kata:planning-phases` orchestrator (standard phase planning)
+- `/kata:planning-phases --gaps` orchestrator (gap closure planning from verification failures)
+- `/kata:planning-phases` orchestrator in revision mode (updating plans based on checker feedback)
 
 Your job: Produce PLAN.md files that Claude executors can implement without interpretation. Plans are prompts, not documents that become prompts.
 
@@ -112,7 +112,7 @@ Discovery is MANDATORY unless you can prove current context exists.
 - Level 2+: New library not in package.json, external API, "choose/select/evaluate" in description
 - Level 3: "architecture/design/system", multiple external services, data modeling, auth design
 
-For niche domains (3D, games, audio, shaders, ML), suggest `/kata:phase-research` before phase-plan.
+For niche domains (3D, games, audio, shaders, ML), suggest `/kata:researching-phases` before phase-plan.
 
 </discovery_levels>
 
@@ -810,13 +810,13 @@ Triggered by `--gaps` flag. Creates plans to address verification or UAT failure
 ```bash
 # Match both zero-padded (05-*) and unpadded (5-*) folders
 PADDED_PHASE=$(printf "%02d" ${PHASE_ARG} 2>/dev/null || echo "${PHASE_ARG}")
-PHASE_DIR=$(ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE_ARG}-* 2>/dev/null | head -1)
+PHASE_DIR=$((ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE_ARG}-* 2>/dev/null || true) | head -1)
 
 # Check for VERIFICATION.md (code verification gaps)
-ls "$PHASE_DIR"/*-VERIFICATION.md 2>/dev/null
+(ls "$PHASE_DIR"/*-VERIFICATION.md 2>/dev/null || true) || true
 
 # Check for UAT.md with diagnosed status (user testing gaps)
-grep -l "status: diagnosed" "$PHASE_DIR"/*-UAT.md 2>/dev/null
+grep -l "status: diagnosed" "$PHASE_DIR"/*-UAT.md 2>/dev/null || true
 ```
 
 **2. Parse gaps:**
@@ -1019,7 +1019,7 @@ Store `COMMIT_PLANNING_DOCS` for use in git operations.
 Check for codebase map:
 
 ```bash
-ls .planning/codebase/*.md 2>/dev/null
+(ls .planning/codebase/*.md 2>/dev/null || true) || true
 ```
 
 If exists, load relevant documents based on phase type:
@@ -1095,16 +1095,16 @@ Understand:
 ```bash
 # Match both zero-padded (05-*) and unpadded (5-*) folders
 PADDED_PHASE=$(printf "%02d" ${PHASE} 2>/dev/null || echo "${PHASE}")
-PHASE_DIR=$(ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE}-* 2>/dev/null | head -1)
+PHASE_DIR=$((ls -d .planning/phases/${PADDED_PHASE}-* .planning/phases/${PHASE}-* 2>/dev/null || true) | head -1)
 
-# Read CONTEXT.md if exists (from /kata:phase-discuss)
-cat "${PHASE_DIR}"/*-CONTEXT.md 2>/dev/null
+# Read CONTEXT.md if exists (from /kata:discussing-phases)
+cat "${PHASE_DIR}"/*-CONTEXT.md 2>/dev/null || true
 
-# Read RESEARCH.md if exists (from /kata:phase-research)
-cat "${PHASE_DIR}"/*-RESEARCH.md 2>/dev/null
+# Read RESEARCH.md if exists (from /kata:researching-phases)
+cat "${PHASE_DIR}"/*-RESEARCH.md 2>/dev/null || true
 
 # Read DISCOVERY.md if exists (from mandatory discovery)
-cat "${PHASE_DIR}"/*-DISCOVERY.md 2>/dev/null
+cat "${PHASE_DIR}"/*-DISCOVERY.md 2>/dev/null || true
 ```
 
 **If CONTEXT.md exists:** Honor user's vision, prioritize their essential features, respect stated boundaries. These are locked decisions - do not revisit.
@@ -1208,7 +1208,7 @@ Update ROADMAP.md to finalize phase placeholders created by phase-add or phase-i
 
 **Plans** (always update):
 - `**Plans:** 0 plans` → `**Plans:** {N} plans`
-- `**Plans:** (created by /kata:phase-plan)` → `**Plans:** {N} plans`
+- `**Plans:** (created by /kata:planning-phases)` → `**Plans:** {N} plans`
 
 **Plan list** (always update):
 - Replace `Plans:\n- [ ] TBD ...` with actual plan checkboxes:
@@ -1271,7 +1271,7 @@ Return structured planning outcome to orchestrator.
 
 ### Next Steps
 
-Execute: `/kata:phase-execute {phase}`
+Execute: `/kata:executing-phases {phase}`
 
 <sub>`/clear` first - fresh context window</sub>
 ```
@@ -1315,7 +1315,7 @@ Execute: `/kata:phase-execute {phase}`
 
 ### Next Steps
 
-Execute: `/kata:phase-execute {phase} --gaps-only`
+Execute: `/kata:executing-phases {phase} --gaps-only`
 ```
 
 ## Revision Complete
@@ -1381,6 +1381,6 @@ Planning complete when:
 - [ ] PLAN file(s) exist with gap_closure: true
 - [ ] Each plan: tasks derived from gap.missing items
 - [ ] PLAN file(s) committed to git
-- [ ] User knows to run `/kata:phase-execute {X}` next
+- [ ] User knows to run `/kata:executing-phases {X}` next
 
 </success_criteria>

package/agents/kata-project-researcher.md

@@ -1,6 +1,6 @@
 ---
 name: kata-project-researcher
-description: Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /kata:project-new or /kata:milestone-new orchestrators.
+description: Researches domain ecosystem before roadmap creation. Produces files in .planning/research/ consumed during roadmap creation. Spawned by /kata:starting-projects or /kata:starting-milestones orchestrators.
 tools: Read, Write, Bash, Grep, Glob, WebSearch, WebFetch, mcp__context7__*
 color: cyan
 ---
@@ -10,8 +10,8 @@ You are a Kata project researcher. You research the domain ecosystem before road
 
 You are spawned by:
 
-- `/kata:project-new` orchestrator (Phase 6: Research)
-- `/kata:milestone-new` orchestrator (Phase 6: Research)
+- `/kata:starting-projects` orchestrator (Phase 6: Research)
+- `/kata:starting-milestones` orchestrator (Phase 6: Research)
 
 Your job: Answer "What does this domain ecosystem look like?" Produce research files that inform roadmap creation.
 

package/agents/kata-research-synthesizer.md

@@ -1,6 +1,6 @@
 ---
 name: kata-research-synthesizer
-description: Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /kata:project-new after 4 researcher agents complete.
+description: Synthesizes research outputs from parallel researcher agents into SUMMARY.md. Spawned by /kata:starting-projects after 4 researcher agents complete.
 tools: Read, Write, Bash
 color: purple
 ---
@@ -10,7 +10,7 @@ You are a Kata research synthesizer. You read the outputs from 4 parallel resear
 
 You are spawned by:
 
-- `/kata:project-new` orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
+- `/kata:starting-projects` orchestrator (after STACK, FEATURES, ARCHITECTURE, PITFALLS research completes)
 
 Your job: Create a unified research summary that informs roadmap creation. Extract key findings, identify patterns across research files, and produce roadmap implications.
 
@@ -106,7 +106,7 @@ This is the most important section. Based on combined research:
 - Which pitfalls it must avoid
 
 **Add research flags:**
-- Which phases likely need `/kata:phase-research` during planning?
+- Which phases likely need `/kata:researching-phases` during planning?
 - Which phases have well-documented patterns (skip research)?
 
 ## Step 5: Assess Confidence

package/agents/kata-roadmapper.md

@@ -1,6 +1,6 @@
 ---
 name: kata-roadmapper
-description: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /kata:project-new orchestrator.
+description: Creates project roadmaps with phase breakdown, requirement mapping, success criteria derivation, and coverage validation. Spawned by /kata:starting-projects orchestrator.
 tools: Read, Write, Bash, Glob, Grep
 color: purple
 ---
@@ -10,7 +10,7 @@ You are a Kata roadmapper. You create project roadmaps that map requirements to
 
 You are spawned by:
 
-- `/kata:project-new` orchestrator (unified project initialization)
+- `/kata:starting-projects` orchestrator (unified project initialization)
 
 Your job: Transform requirements into a phase structure that delivers the project. Every v1 requirement maps to exactly one phase. Every phase has observable success criteria.
 
@@ -24,7 +24,7 @@ Your job: Transform requirements into a phase structure that delivers the projec
 </role>
 
 <downstream_consumer>
-Your ROADMAP.md is consumed by `/kata:phase-plan` which uses it to:
+Your ROADMAP.md is consumed by `/kata:planning-phases` which uses it to:
 
 | Output               | How phase-plan Uses It           |
 | -------------------- | -------------------------------- |
@@ -182,7 +182,7 @@ Track coverage as you go.
 **Integer phases (1, 2, 3):** Planned milestone work.
 
 **Decimal phases (2.1, 2.2):** Urgent insertions after planning.
-- Created via `/kata:phase-insert`
+- Created via `/kata:inserting-phases`
 - Execute between integers: 1 → 1.1 → 1.2 → 2
 
 **Starting number:**
@@ -515,7 +515,7 @@ After incorporating user feedback and updating files:
 
 ### Ready for Planning
 
-Next: `/kata:phase-plan 1`
+Next: `/kata:planning-phases 1`
 ```
 
 ## Roadmap Blocked

package/agents/kata-verifier.md

@@ -34,7 +34,7 @@ Then verify each level against the actual codebase.
 Before starting fresh, check if a previous VERIFICATION.md exists:
 
 ```bash
-cat "$PHASE_DIR"/*-VERIFICATION.md 2>/dev/null
+cat "$PHASE_DIR"/*-VERIFICATION.md 2>/dev/null || true
 ```
 
 **If previous verification exists with `gaps:` section → RE-VERIFICATION MODE:**
@@ -57,14 +57,14 @@ Gather all verification context from the phase directory and project state.
 
 ```bash
 # Phase directory (provided in prompt)
-ls "$PHASE_DIR"/*-PLAN.md 2>/dev/null
-ls "$PHASE_DIR"/*-SUMMARY.md 2>/dev/null
+(ls "$PHASE_DIR"/*-PLAN.md 2>/dev/null || true) || true
+(ls "$PHASE_DIR"/*-SUMMARY.md 2>/dev/null || true) || true
 
 # Phase goal from ROADMAP
 grep -A 5 "Phase ${PHASE_NUM}" .planning/ROADMAP.md
 
 # Requirements mapped to this phase
-grep -E "^| ${PHASE_NUM}" .planning/REQUIREMENTS.md 2>/dev/null
+grep -E "^| ${PHASE_NUM}" .planning/REQUIREMENTS.md 2>/dev/null || true
 ```
 
 Extract phase goal from ROADMAP.md. This is the outcome to verify, not the tasks.
@@ -78,7 +78,7 @@ Determine what must be verified. In re-verification mode, must-haves come from S
 Check if any PLAN.md has `must_haves` in frontmatter:
 
 ```bash
-grep -l "must_haves:" "$PHASE_DIR"/*-PLAN.md 2>/dev/null
+grep -l "must_haves:" "$PHASE_DIR"/*-PLAN.md 2>/dev/null || true
 ```
 
 If found, extract and use:
@@ -372,7 +372,7 @@ verify_state_render_link() {
 If REQUIREMENTS.md exists and has requirements mapped to this phase:
 
 ```bash
-grep -E "Phase ${PHASE_NUM}" .planning/REQUIREMENTS.md 2>/dev/null
+grep -E "Phase ${PHASE_NUM}" .planning/REQUIREMENTS.md 2>/dev/null || true
 ```
 
 For each requirement:
@@ -406,13 +406,13 @@ scan_antipatterns() {
     [ -f "$file" ] || continue
 
     # TODO/FIXME comments
-    grep -n -E "TODO|FIXME|XXX|HACK" "$file" 2>/dev/null
+    grep -n -E "TODO|FIXME|XXX|HACK" "$file" 2>/dev/null || true
 
     # Placeholder content
-    grep -n -E "placeholder|coming soon|will be here" "$file" -i 2>/dev/null
+    grep -n -E "placeholder|coming soon|will be here" "$file" -i 2>/dev/null || true
 
     # Empty implementations
-    grep -n -E "return null|return \{\}|return \[\]|=> \{\}" "$file" 2>/dev/null
+    grep -n -E "return null|return \{\}|return \[\]|=> \{\}" "$file" 2>/dev/null || true
 
     # Console.log only implementations
     grep -n -B 2 -A 2 "console\.log" "$file" 2>/dev/null | grep -E "^\s*(const|function|=>)"
@@ -486,7 +486,7 @@ score = (verified_truths / total_truths)
 
 ## Step 10: Structure Gap Output (If Gaps Found)
 
-When gaps are found, structure them for consumption by `/kata:phase-plan --gaps`.
+When gaps are found, structure them for consumption by `/kata:planning-phases --gaps`.
 
 **Output structured gaps in YAML frontmatter:**
 
@@ -527,7 +527,7 @@ gaps:
 - `artifacts`: Which files have issues and what's wrong
 - `missing`: Specific things that need to be added/fixed
 
-The planner (`/kata:phase-plan --gaps`) reads this gap analysis and creates appropriate plans.
+The planner (`/kata:planning-phases --gaps`) reads this gap analysis and creates appropriate plans.
 
 **Group related gaps by concern** when possible — if multiple truths fail because of the same root cause (e.g., "Chat component is a stub"), note this in the reason to help the planner create focused plans.
 
@@ -648,7 +648,7 @@ All must-haves verified. Phase goal achieved. Ready to proceed.
 2. **{Truth 2}** — {reason}
    - Missing: {what needs to be added}
 
-Structured gaps in VERIFICATION.md frontmatter for `/kata:phase-plan --gaps`.
+Structured gaps in VERIFICATION.md frontmatter for `/kata:planning-phases --gaps`.
 
 {If human_needed:}
 
@@ -674,7 +674,7 @@ Automated checks passed. Awaiting human verification.
 
 **DO NOT skip key link verification.** This is where 80% of stubs hide. The pieces exist but aren't connected.
 
-**Structure gaps in YAML frontmatter.** The planner (`/kata:phase-plan --gaps`) creates plans from your analysis.
+**Structure gaps in YAML frontmatter.** The planner (`/kata:planning-phases --gaps`) creates plans from your analysis.
 
 **DO flag for human verification when uncertain.** If you can't verify programmatically (visual, real-time, external service), say so explicitly.
 

package/agents/references/execute-plan.md

@@ -33,7 +33,7 @@ Store resolved model for use in Task calls below.
 Before any operation, read project state:
 
 ```bash
-cat .planning/STATE.md 2>/dev/null
+cat .planning/STATE.md 2>/dev/null || true
 ```
 
 **If file exists:** Parse and internalize:
@@ -78,8 +78,8 @@ Find the next plan to execute:
 cat .planning/ROADMAP.md
 # Look for phase with "In progress" status
 # Then find plans in that phase
-ls .planning/phases/XX-name/*-PLAN.md 2>/dev/null | sort
-ls .planning/phases/XX-name/*-SUMMARY.md 2>/dev/null | sort
+(ls .planning/phases/XX-name/*-PLAN.md 2>/dev/null || true) | sort
+(ls .planning/phases/XX-name/*-SUMMARY.md 2>/dev/null || true) | sort
 ```
 
 **Logic:**
@@ -111,7 +111,7 @@ Confirm with user if ambiguous.
 
 <config-check>
 ```bash
-cat .planning/config.json 2>/dev/null
+cat .planning/config.json 2>/dev/null || true
 ```
 </config-check>
 
@@ -564,7 +564,7 @@ Before executing, check if previous phase had issues:
 
 ```bash
 # Find previous phase summary
-ls .planning/phases/*/SUMMARY.md 2>/dev/null | sort -r | head -2 | tail -1
+(ls .planning/phases/*/SUMMARY.md 2>/dev/null || true) | sort -r | head -2 | tail -1
 ```
 
 If previous phase SUMMARY.md has "Issues Encountered" != "None" or "Next Phase Readiness" mentions blockers:
@@ -1630,7 +1630,7 @@ Check what changed across all task commits in this plan:
 FIRST_TASK=$(git log --oneline --grep="feat({phase}-{plan}):" --grep="fix({phase}-{plan}):" --grep="test({phase}-{plan}):" --reverse | head -1 | cut -d' ' -f1)
 
 # Get all changes from first task through now
-git diff --name-only ${FIRST_TASK}^..HEAD 2>/dev/null
+git diff --name-only ${FIRST_TASK}^..HEAD 2>/dev/null || true
 ```
 
 **Update only if structural changes occurred:**
@@ -1695,8 +1695,8 @@ This warning appears BEFORE "Plan complete" messaging. User sees setup requireme
 List files in the phase directory:
 
 ```bash
-ls -1 .planning/phases/[current-phase-dir]/*-PLAN.md 2>/dev/null | wc -l
-ls -1 .planning/phases/[current-phase-dir]/*-SUMMARY.md 2>/dev/null | wc -l
+(ls -1 .planning/phases/[current-phase-dir]/*-PLAN.md 2>/dev/null || true) | wc -l
+(ls -1 .planning/phases/[current-phase-dir]/*-SUMMARY.md 2>/dev/null || true) | wc -l
 ```
 
 State the counts: "This phase has [X] plans and [Y] summaries."
@@ -1744,14 +1744,14 @@ Summary: .planning/phases/{phase-dir}/{phase}-{plan}-SUMMARY.md
 
 **{phase}-{next-plan}: [Plan Name]** — [objective from next PLAN.md]
 
-`/kata:phase-execute {phase}`
+`/kata:executing-phases {phase}`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/kata:phase-verify {phase}-{plan}` — manual acceptance testing before continuing
+- `/kata:verifying-work {phase}-{plan}` — manual acceptance testing before continuing
 - Review what was built before continuing
 
 ---
@@ -1805,15 +1805,15 @@ All {Y} plans finished.
 
 **Phase {Z+1}: {Next Phase Name}** — {Goal from ROADMAP.md}
 
-`/kata:phase-plan {Z+1}`
+`/kata:planning-phases {Z+1}`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/kata:phase-verify {Z}` — manual acceptance testing before continuing
-- `/kata:phase-discuss {Z+1}` — gather context first
+- `/kata:verifying-work {Z}` — manual acceptance testing before continuing
+- `/kata:discussing-phases {Z+1}` — gather context first
 - Review phase accomplishments before continuing
 
 ---
@@ -1843,15 +1843,15 @@ All {Y} plans finished.
 
 **Complete Milestone** — archive and prepare for next
 
-`/kata:milestone-complete`
+`/kata:completing-milestones`
 
 <sub>`/clear` first → fresh context window</sub>
 
 ---
 
 **Also available:**
-- `/kata:phase-verify` — manual acceptance testing before completing milestone
-- `/kata:phase-add <description>` — add another phase before completing
+- `/kata:verifying-work` — manual acceptance testing before completing milestone
+- `/kata:adding-phases <description>` — add another phase before completing
 - Review accomplishments before archiving
 
 ---

package/package.json

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