@gannonh/kata 0.1.4 → 0.2.0

package/commands/kata/remove-phase.md

@@ -1,338 +1,20 @@
 ---
-name: kata:remove-phase
+name: remove-phase
 description: Remove a future phase from roadmap and renumber subsequent phases
 argument-hint: <phase-number>
+version: 0.1.0
+disable-model-invocation: true
 allowed-tools:
   - Read
   - Write
   - Bash
-  - Glob
 ---
 
-<objective>
-Remove an unstarted future phase from the roadmap and renumber all subsequent phases to maintain a clean, linear sequence.
+## Step 1: Parse Context
 
-Purpose: Clean removal of work you've decided not to do, without polluting context with cancelled/deferred markers.
-Output: Phase deleted, all subsequent phases renumbered, git commit as historical record.
-</objective>
+Arguments: "$ARGUMENTS"
 
-<execution_context>
-@.planning/ROADMAP.md
-@.planning/STATE.md
-</execution_context>
+## Step 2: Invoke Skill
 
-<process>
-
-<step name="parse_arguments">
-Parse the command arguments:
-- Argument is the phase number to remove (integer or decimal)
-- Example: `/kata:remove-phase 17` → phase = 17
-- Example: `/kata:remove-phase 16.1` → phase = 16.1
-
-If no argument provided:
-
-```
-ERROR: Phase number required
-Usage: /kata:remove-phase <phase-number>
-Example: /kata:remove-phase 17
-```
-
-Exit.
-</step>
-
-<step name="load_state">
-Load project state:
-
-```bash
-cat .planning/STATE.md 2>/dev/null
-cat .planning/ROADMAP.md 2>/dev/null
-```
-
-Parse current phase number from STATE.md "Current Position" section.
-</step>
-
-<step name="validate_phase_exists">
-Verify the target phase exists in ROADMAP.md:
-
-1. Search for `### Phase {target}:` heading
-2. If not found:
-
-   ```
-   ERROR: Phase {target} not found in roadmap
-   Available phases: [list phase numbers]
-   ```
-
-   Exit.
-</step>
-
-<step name="validate_future_phase">
-Verify the phase is a future phase (not started):
-
-1. Compare target phase to current phase from STATE.md
-2. Target must be > current phase number
-
-If target <= current phase:
-
-```
-ERROR: Cannot remove Phase {target}
-
-Only future phases can be removed:
-- Current phase: {current}
-- Phase {target} is current or completed
-
-To abandon current work, use /kata:pause-work instead.
-```
-
-Exit.
-
-3. Check for SUMMARY.md files in phase directory:
-
-```bash
-ls .planning/phases/{target}-*/*-SUMMARY.md 2>/dev/null
-```
-
-If any SUMMARY.md files exist:
-
-```
-ERROR: Phase {target} has completed work
-
-Found executed plans:
-- {list of SUMMARY.md files}
-
-Cannot remove phases with completed work.
-```
-
-Exit.
-</step>
-
-<step name="gather_phase_info">
-Collect information about the phase being removed:
-
-1. Extract phase name from ROADMAP.md heading: `### Phase {target}: {Name}`
-2. Find phase directory: `.planning/phases/{target}-{slug}/`
-3. Find all subsequent phases (integer and decimal) that need renumbering
-
-**Subsequent phase detection:**
-
-For integer phase removal (e.g., 17):
-- Find all phases > 17 (integers: 18, 19, 20...)
-- Find all decimal phases >= 17.0 and < 18.0 (17.1, 17.2...) → these become 16.x
-- Find all decimal phases for subsequent integers (18.1, 19.1...) → renumber with their parent
-
-For decimal phase removal (e.g., 17.1):
-- Find all decimal phases > 17.1 and < 18 (17.2, 17.3...) → renumber down
-- Integer phases unchanged
-
-List all phases that will be renumbered.
-</step>
-
-<step name="confirm_removal">
-Present removal summary and confirm:
-
-```
-Removing Phase {target}: {Name}
-
-This will:
-- Delete: .planning/phases/{target}-{slug}/
-- Renumber {N} subsequent phases:
-  - Phase 18 → Phase 17
-  - Phase 18.1 → Phase 17.1
-  - Phase 19 → Phase 18
-  [etc.]
-
-Proceed? (y/n)
-```
-
-Wait for confirmation.
-</step>
-
-<step name="delete_phase_directory">
-Delete the target phase directory if it exists:
-
-```bash
-if [ -d ".planning/phases/{target}-{slug}" ]; then
-  rm -rf ".planning/phases/{target}-{slug}"
-  echo "Deleted: .planning/phases/{target}-{slug}/"
-fi
-```
-
-If directory doesn't exist, note: "No directory to delete (phase not yet created)"
-</step>
-
-<step name="renumber_directories">
-Rename all subsequent phase directories:
-
-For each phase directory that needs renumbering (in reverse order to avoid conflicts):
-
-```bash
-# Example: renaming 18-dashboard to 17-dashboard
-mv ".planning/phases/18-dashboard" ".planning/phases/17-dashboard"
-```
-
-Process in descending order (20→19, then 19→18, then 18→17) to avoid overwriting.
-
-Also rename decimal phase directories:
-- `17.1-fix-bug` → `16.1-fix-bug` (if removing integer 17)
-- `17.2-hotfix` → `17.1-hotfix` (if removing decimal 17.1)
-</step>
-
-<step name="rename_files_in_directories">
-Rename plan files inside renumbered directories:
-
-For each renumbered directory, rename files that contain the phase number:
-
-```bash
-# Inside 17-dashboard (was 18-dashboard):
-mv "18-01-PLAN.md" "17-01-PLAN.md"
-mv "18-02-PLAN.md" "17-02-PLAN.md"
-mv "18-01-SUMMARY.md" "17-01-SUMMARY.md"  # if exists
-# etc.
-```
-
-Also handle CONTEXT.md and DISCOVERY.md (these don't have phase prefixes, so no rename needed).
-</step>
-
-<step name="update_roadmap">
-Update ROADMAP.md:
-
-1. **Remove the phase section entirely:**
-   - Delete from `### Phase {target}:` to the next phase heading (or section end)
-
-2. **Remove from phase list:**
-   - Delete line `- [ ] **Phase {target}: {Name}**` or similar
-
-3. **Remove from Progress table:**
-   - Delete the row for Phase {target}
-
-4. **Renumber all subsequent phases:**
-   - `### Phase 18:` → `### Phase 17:`
-   - `- [ ] **Phase 18:` → `- [ ] **Phase 17:`
-   - Table rows: `| 18. Dashboard |` → `| 17. Dashboard |`
-   - Plan references: `18-01:` → `17-01:`
-
-5. **Update dependency references:**
-   - `**Depends on:** Phase 18` → `**Depends on:** Phase 17`
-   - For the phase that depended on the removed phase:
-     - `**Depends on:** Phase 17` (removed) → `**Depends on:** Phase 16`
-
-6. **Renumber decimal phases:**
-   - `### Phase 17.1:` → `### Phase 16.1:` (if integer 17 removed)
-   - Update all references consistently
-
-Write updated ROADMAP.md.
-</step>
-
-<step name="update_state">
-Update STATE.md:
-
-1. **Update total phase count:**
-   - `Phase: 16 of 20` → `Phase: 16 of 19`
-
-2. **Recalculate progress percentage:**
-   - New percentage based on completed plans / new total plans
-
-Do NOT add a "Roadmap Evolution" note - the git commit is the record.
-
-Write updated STATE.md.
-</step>
-
-<step name="update_file_contents">
-Search for and update phase references inside plan files:
-
-```bash
-# Find files that reference the old phase numbers
-grep -r "Phase 18" .planning/phases/17-*/ 2>/dev/null
-grep -r "Phase 19" .planning/phases/18-*/ 2>/dev/null
-# etc.
-```
-
-Update any internal references to reflect new numbering.
-</step>
-
-<step name="commit">
-Stage and commit the removal:
-
-```bash
-git add .planning/
-git commit -m "chore: remove phase {target} ({original-phase-name})"
-```
-
-The commit message preserves the historical record of what was removed.
-</step>
-
-<step name="completion">
-Present completion summary:
-
-```
-Phase {target} ({original-name}) removed.
-
-Changes:
-- Deleted: .planning/phases/{target}-{slug}/
-- Renumbered: Phases {first-renumbered}-{last-old} → {first-renumbered-1}-{last-new}
-- Updated: ROADMAP.md, STATE.md
-- Committed: chore: remove phase {target} ({original-name})
-
-Current roadmap: {total-remaining} phases
-Current position: Phase {current} of {new-total}
-
----
-
-## What's Next
-
-Would you like to:
-- `/kata:progress` — see updated roadmap status
-- Continue with current phase
-- Review roadmap
-
----
-```
-</step>
-
-</process>
-
-<anti_patterns>
-
-- Don't remove completed phases (have SUMMARY.md files)
-- Don't remove current or past phases
-- Don't leave gaps in numbering - always renumber
-- Don't add "removed phase" notes to STATE.md - git commit is the record
-- Don't ask about each decimal phase - just renumber them
-- Don't modify completed phase directories
-</anti_patterns>
-
-<edge_cases>
-
-**Removing a decimal phase (e.g., 17.1):**
-- Only affects other decimals in same series (17.2 → 17.1, 17.3 → 17.2)
-- Integer phases unchanged
-- Simpler operation
-
-**No subsequent phases to renumber:**
-- Removing the last phase (e.g., Phase 20 when that's the end)
-- Just delete and update ROADMAP.md, no renumbering needed
-
-**Phase directory doesn't exist:**
-- Phase may be in ROADMAP.md but directory not created yet
-- Skip directory deletion, proceed with ROADMAP.md updates
-
-**Decimal phases under removed integer:**
-- Removing Phase 17 when 17.1, 17.2 exist
-- 17.1 → 16.1, 17.2 → 16.2
-- They maintain their position in execution order (after current last integer)
-
-</edge_cases>
-
-<success_criteria>
-Phase removal is complete when:
-
-- [ ] Target phase validated as future/unstarted
-- [ ] Phase directory deleted (if existed)
-- [ ] All subsequent phase directories renumbered
-- [ ] Files inside directories renamed ({old}-01-PLAN.md → {new}-01-PLAN.md)
-- [ ] ROADMAP.md updated (section removed, all references renumbered)
-- [ ] STATE.md updated (phase count, progress percentage)
-- [ ] Dependency references updated in subsequent phases
-- [ ] Changes committed with descriptive message
-- [ ] No gaps in phase numbering
-- [ ] User informed of changes
-</success_criteria>
+Run the following skill:
+`Skill("kata-removing-phases")`

package/commands/kata/research-phase.md

@@ -1,180 +1,20 @@
 ---
-name: kata:research-phase
+name: research-phase
 description: Research how to implement a phase (standalone - usually use /kata:plan-phase instead)
-argument-hint: "[phase]"
+argument-hint: [phase]
+version: 0.1.0
+disable-model-invocation: true
 allowed-tools:
   - Read
+  - Write
   - Bash
-  - Task
 ---
 
-<objective>
-Research how to implement a phase. Spawns kata-phase-researcher agent with phase context.
+## Step 1: Parse Context
 
-**Note:** This is a standalone research command. For most workflows, use `/kata:plan-phase` which integrates research automatically.
+Arguments: "$ARGUMENTS"
 
-**Use this command when:**
-- You want to research without planning yet
-- You want to re-research after planning is complete
-- You need to investigate before deciding if a phase is feasible
+## Step 2: Invoke Skill
 
-**Orchestrator role:** Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results.
-
-**Why subagent:** Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction.
-</objective>
-
-<context>
-Phase number: $ARGUMENTS (required)
-
-Normalize phase input in step 1 before any directory lookups.
-</context>
-
-<process>
-
-## 1. Normalize and Validate Phase
-
-```bash
-# Normalize phase number (8 → 08, but preserve decimals like 2.1 → 02.1)
-if [[ "$ARGUMENTS" =~ ^[0-9]+$ ]]; then
-  PHASE=$(printf "%02d" "$ARGUMENTS")
-elif [[ "$ARGUMENTS" =~ ^([0-9]+)\.([0-9]+)$ ]]; then
-  PHASE=$(printf "%02d.%s" "${BASH_REMATCH[1]}" "${BASH_REMATCH[2]}")
-else
-  PHASE="$ARGUMENTS"
-fi
-
-grep -A5 "Phase ${PHASE}:" .planning/ROADMAP.md 2>/dev/null
-```
-
-**If not found:** Error and exit. **If found:** Extract phase number, name, description.
-
-## 2. Check Existing Research
-
-```bash
-ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null
-```
-
-**If exists:** Offer: 1) Update research, 2) View existing, 3) Skip. Wait for response.
-
-**If doesn't exist:** Continue.
-
-## 3. Gather Phase Context
-
-```bash
-grep -A20 "Phase ${PHASE}:" .planning/ROADMAP.md
-cat .planning/REQUIREMENTS.md 2>/dev/null
-cat .planning/phases/${PHASE}-*/${PHASE}-CONTEXT.md 2>/dev/null
-grep -A30 "### Decisions Made" .planning/STATE.md 2>/dev/null
-```
-
-Present summary with phase description, requirements, prior decisions.
-
-## 4. Spawn gsd-researcher Agent
-
-Research modes: ecosystem (default), feasibility, implementation, comparison.
-
-```markdown
-<research_type>
-Phase Research — investigating HOW to implement a specific phase well.
-</research_type>
-
-<key_insight>
-The question is NOT "which library should I use?"
-
-The question is: "What do I not know that I don't know?"
-
-For this phase, discover:
-- What's the established architecture pattern?
-- What libraries form the standard stack?
-- What problems do people commonly hit?
-- What's SOTA vs what Claude's training thinks is SOTA?
-- What should NOT be hand-rolled?
-</key_insight>
-
-<objective>
-Research implementation approach for Phase {phase_number}: {phase_name}
-Mode: ecosystem
-</objective>
-
-<context>
-**Phase description:** {phase_description}
-**Requirements:** {requirements_list}
-**Prior decisions:** {decisions_if_any}
-**Phase context:** {context_md_content}
-</context>
-
-<downstream_consumer>
-Your RESEARCH.md will be loaded by `/kata:plan-phase` which uses specific sections:
-- `## Standard Stack` → Plans use these libraries
-- `## Architecture Patterns` → Task structure follows these
-- `## Don't Hand-Roll` → Tasks NEVER build custom solutions for listed problems
-- `## Common Pitfalls` → Verification steps check for these
-- `## Code Examples` → Task actions reference these patterns
-
-Be prescriptive, not exploratory. "Use X" not "Consider X or Y."
-</downstream_consumer>
-
-<quality_gate>
-Before declaring complete, verify:
-- [ ] All domains investigated (not just some)
-- [ ] Negative claims verified with official docs
-- [ ] Multiple sources for critical claims
-- [ ] Confidence levels assigned honestly
-- [ ] Section names match what plan-phase expects
-</quality_gate>
-
-<output>
-Write to: .planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
-</output>
-```
-
-```
-Task(
-  prompt=filled_prompt,
-  subagent_type="kata-phase-researcher",
-  description="Research Phase {phase}"
-)
-```
-
-## 5. Handle Agent Return
-
-**`## RESEARCH COMPLETE`:** Display summary, offer: Plan phase, Dig deeper, Review full, Done.
-
-**`## CHECKPOINT REACHED`:** Present to user, get response, spawn continuation.
-
-**`## RESEARCH INCONCLUSIVE`:** Show what was attempted, offer: Add context, Try different mode, Manual.
-
-## 6. Spawn Continuation Agent
-
-```markdown
-<objective>
-Continue research for Phase {phase_number}: {phase_name}
-</objective>
-
-<prior_state>
-Research file: @.planning/phases/${PHASE}-{slug}/${PHASE}-RESEARCH.md
-</prior_state>
-
-<checkpoint_response>
-**Type:** {checkpoint_type}
-**Response:** {user_response}
-</checkpoint_response>
-```
-
-```
-Task(
-  prompt=continuation_prompt,
-  subagent_type="kata-phase-researcher",
-  description="Continue research Phase {phase}"
-)
-```
-
-</process>
-
-<success_criteria>
-- [ ] Phase validated against roadmap
-- [ ] Existing research checked
-- [ ] kata-phase-researcher spawned with context
-- [ ] Checkpoints handled correctly
-- [ ] User knows next steps
-</success_criteria>
+Run the following skill:
+`Skill("kata-researching-phases")`

package/commands/kata/resume-work.md

@@ -1,40 +1,20 @@
 ---
-name: kata:resume-work
+name: resume-work
 description: Resume work from previous session with full context restoration
+argument-hint: <description>
+version: 0.1.0
+disable-model-invocation: true
 allowed-tools:
   - Read
-  - Bash
   - Write
-  - AskUserQuestion
-  - SlashCommand
+  - Bash
 ---
 
-<objective>
-Restore complete project context and resume work seamlessly from previous session.
-
-Routes to the resume-project workflow which handles:
-
-- STATE.md loading (or reconstruction if missing)
-- Checkpoint detection (.continue-here files)
-- Incomplete work detection (PLAN without SUMMARY)
-- Status presentation
-- Context-aware next action routing
-  </objective>
-
-<execution_context>
-@~/.claude/kata/workflows/resume-project.md
-</execution_context>
+## Step 1: Parse Context
 
-<process>
-**Follow the resume-project workflow** from `@~/.claude/kata/workflows/resume-project.md`.
+Arguments: "$ARGUMENTS"
 
-The workflow handles all resumption logic including:
+## Step 2: Invoke Skill
 
-1. Project existence verification
-2. STATE.md loading or reconstruction
-3. Checkpoint and incomplete work detection
-4. Visual status presentation
-5. Context-aware option offering (checks CONTEXT.md before suggesting plan vs discuss)
-6. Routing to appropriate next command
-7. Session continuity updates
-   </process>
+Run the following skill:
+`Skill("kata-resuming-work")`

package/commands/kata/set-profile.md

@@ -0,0 +1,20 @@
+---
+name: set-profile
+description: Switch model profile for Kata agents (quality/balanced/budget)
+argument-hint: <description>
+version: 0.1.0
+disable-model-invocation: true
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+## Step 1: Parse Context
+
+Arguments: "$ARGUMENTS"
+
+## Step 2: Invoke Skill
+
+Run the following skill:
+`Skill("kata-setting-profiles")`

package/commands/kata/settings.md

@@ -0,0 +1,20 @@
+---
+name: settings
+description: Configure Kata workflow toggles and model profile
+argument-hint: <description>
+version: 0.1.0
+disable-model-invocation: true
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+## Step 1: Parse Context
+
+Arguments: "$ARGUMENTS"
+
+## Step 2: Invoke Skill
+
+Run the following skill:
+`Skill("kata-configuring-settings")`

package/commands/kata/start-milestone.md

@@ -0,0 +1,20 @@
+---
+name: start-milestone
+description: Start a new milestone cycle — update PROJECT.md and route to requirements
+argument-hint: [milestone name, e.g., 'v1.1 Notifications']
+version: 0.1.0
+disable-model-invocation: true
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+## Step 1: Parse Context
+
+Arguments: "$ARGUMENTS"
+
+## Step 2: Invoke Skill
+
+Run the following skill:
+`Skill("kata-starting-milestones")`

package/commands/kata/start-new-milestone.md

@@ -0,0 +1,20 @@
+---
+name: start-new-milestone
+description: Start a new milestone cycle — update PROJECT.md and route to requirements
+argument-hint: [milestone name, e.g., 'v1.1 Notifications']
+version: 0.1.0
+disable-model-invocation: true
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+## Step 1: Parse Context
+
+Arguments: "$ARGUMENTS"
+
+## Step 2: Invoke Skill
+
+Run the following skill:
+`Skill("kata-starting-new-milestones")`

package/commands/kata/start-project.md

@@ -0,0 +1,20 @@
+---
+name: start-project
+description: Initialize a new project with deep context gathering and PROJECT.md
+argument-hint: <description>
+version: 0.1.0
+disable-model-invocation: true
+allowed-tools:
+  - Read
+  - Write
+  - Bash
+---
+
+## Step 1: Parse Context
+
+Arguments: "$ARGUMENTS"
+
+## Step 2: Invoke Skill
+
+Run the following skill:
+`Skill("kata-starting-projects")`