claude-cook 1.10.8 → 1.11.1

package/commands/cook/add-todo.md

@@ -1,193 +0,0 @@
----
-name: cook:add-todo
-description: Capture idea or task as todo from current conversation context
-argument-hint: [optional description]
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
----
-
-<objective>
-Capture an idea, task, or issue that surfaces during a COOK session as a structured todo for later work.
-
-Enables "thought → capture → continue" flow without losing context or derailing current work.
-</objective>
-
-<context>
-@.planning/STATE.md
-</context>
-
-<process>
-
-<step name="ensure_directory">
-```bash
-mkdir -p .planning/todos/pending .planning/todos/done
-```
-</step>
-
-<step name="check_existing_areas">
-```bash
-ls .planning/todos/pending/*.md 2>/dev/null | xargs -I {} grep "^area:" {} 2>/dev/null | cut -d' ' -f2 | sort -u
-```
-
-Note existing areas for consistency in infer_area step.
-</step>
-
-<step name="extract_content">
-**With arguments:** Use as the title/focus.
-- `/cook:add-todo Add auth token refresh` → title = "Add auth token refresh"
-
-**Without arguments:** Analyze recent conversation to extract:
-- The specific problem, idea, or task discussed
-- Relevant file paths mentioned
-- Technical details (error messages, line numbers, constraints)
-
-Formulate:
-- `title`: 3-10 word descriptive title (action verb preferred)
-- `problem`: What's wrong or why this is needed
-- `solution`: Approach hints or "TBD" if just an idea
-- `files`: Relevant paths with line numbers from conversation
-</step>
-
-<step name="infer_area">
-Infer area from file paths:
-
-| Path pattern | Area |
-|--------------|------|
-| `src/api/*`, `api/*` | `api` |
-| `src/components/*`, `src/ui/*` | `ui` |
-| `src/auth/*`, `auth/*` | `auth` |
-| `src/db/*`, `database/*` | `database` |
-| `tests/*`, `__tests__/*` | `testing` |
-| `docs/*` | `docs` |
-| `.planning/*` | `planning` |
-| `scripts/*`, `bin/*` | `tooling` |
-| No files or unclear | `general` |
-
-Use existing area from step 2 if similar match exists.
-</step>
-
-<step name="check_duplicates">
-```bash
-grep -l -i "[key words from title]" .planning/todos/pending/*.md 2>/dev/null
-```
-
-If potential duplicate found:
-1. Read the existing todo
-2. Compare scope
-
-If overlapping, use AskUserQuestion:
-- header: "Duplicate?"
-- question: "Similar todo exists: [title]. What would you like to do?"
-- options:
-  - "Skip" — keep existing todo
-  - "Replace" — update existing with new context
-  - "Add anyway" — create as separate todo
-</step>
-
-<step name="create_file">
-```bash
-timestamp=$(date "+%Y-%m-%dT%H:%M")
-date_prefix=$(date "+%Y-%m-%d")
-```
-
-Generate slug from title (lowercase, hyphens, no special chars).
-
-Write to `.planning/todos/pending/${date_prefix}-${slug}.md`:
-
-```markdown
----
-created: [timestamp]
-title: [title]
-area: [area]
-files:
-  - [file:lines]
----
-
-## Problem
-
-[problem description - enough context for future Claude to understand weeks later]
-
-## Solution
-
-[approach hints or "TBD"]
-```
-</step>
-
-<step name="update_state">
-If `.planning/STATE.md` exists:
-
-1. Count todos: `ls .planning/todos/pending/*.md 2>/dev/null | wc -l`
-2. Update "### Pending Todos" under "## Accumulated Context"
-</step>
-
-<step name="git_commit">
-Commit the todo and any updated state:
-
-**Check planning config:**
-
-```bash
-COMMIT_PLANNING_DOCS=$(cat .planning/config.json 2>/dev/null | grep -o '"commit_docs"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
-git check-ignore -q .planning 2>/dev/null && COMMIT_PLANNING_DOCS=false
-```
-
-**If `COMMIT_PLANNING_DOCS=false`:** Skip git operations, log "Todo saved (not committed - commit_docs: false)"
-
-**If `COMMIT_PLANNING_DOCS=true` (default):**
-
-```bash
-git add .planning/todos/pending/[filename]
-[ -f .planning/STATE.md ] && git add .planning/STATE.md
-git commit -m "$(cat <<'EOF'
-docs: capture todo - [title]
-
-Area: [area]
-EOF
-)"
-```
-
-Confirm: "Committed: docs: capture todo - [title]"
-</step>
-
-<step name="confirm">
-```
-Todo saved: .planning/todos/pending/[filename]
-
-  [title]
-  Area: [area]
-  Files: [count] referenced
-
----
-
-Would you like to:
-
-1. Continue with current work
-2. Add another todo
-3. View all todos (/cook:check-todos)
-```
-</step>
-
-</process>
-
-<output>
-- `.planning/todos/pending/[date]-[slug].md`
-- Updated `.planning/STATE.md` (if exists)
-</output>
-
-<anti_patterns>
-- Don't create todos for work in current plan (that's deviation rule territory)
-- Don't create elaborate solution sections — captures ideas, not plans
-- Don't block on missing information — "TBD" is fine
-</anti_patterns>
-
-<success_criteria>
-- [ ] Directory structure exists
-- [ ] Todo file created with valid frontmatter
-- [ ] Problem section has enough context for future Claude
-- [ ] No duplicates (checked and resolved)
-- [ ] Area consistent with existing todos
-- [ ] STATE.md updated if exists
-- [ ] Todo and state committed to git
-</success_criteria>

package/commands/cook/audit-milestone.md

@@ -1,277 +0,0 @@
----
-name: cook:audit-milestone
-description: Audit milestone completion against original intent before archiving
-argument-hint: "[version]"
-allowed-tools:
-  - Read
-  - Glob
-  - Grep
-  - Bash
-  - Task
-  - Write
----
-
-<objective>
-Verify milestone achieved its definition of done. Check requirements coverage, cross-phase integration, and end-to-end flows.
-
-**This command IS the orchestrator.** Reads existing VERIFICATION.md files (phases already verified during execute-phase), aggregates tech debt and deferred gaps, then spawns integration checker for cross-phase wiring.
-</objective>
-
-<execution_context>
-<!-- Spawns cook-integration-checker agent which has all audit expertise baked in -->
-</execution_context>
-
-<context>
-Version: $ARGUMENTS (optional — defaults to current milestone)
-
-**Original Intent:**
-@.planning/PROJECT.md
-@.planning/REQUIREMENTS.md
-
-**Planned Work:**
-@.planning/ROADMAP.md
-@.planning/config.json (if exists)
-
-**Completed Work:**
-Glob: .planning/phases/*/*-SUMMARY.md
-Glob: .planning/phases/*/*-VERIFICATION.md
-</context>
-
-<process>
-
-## 0. Resolve Model Profile
-
-Read model profile for agent spawning:
-
-```bash
-MODEL_PROFILE=$(cat .planning/config.json 2>/dev/null | grep -o '"model_profile"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "balanced")
-```
-
-Default to "balanced" if not set.
-
-**Model lookup table:**
-
-| Agent | quality | balanced | budget |
-|-------|---------|----------|--------|
-| cook-integration-checker | sonnet | sonnet | haiku |
-
-Store resolved model for use in Task call below.
-
-## 1. Determine Milestone Scope
-
-```bash
-# Get phases in milestone
-ls -d .planning/phases/*/ | sort -V
-```
-
-- Parse version from arguments or detect current from ROADMAP.md
-- Identify all phase directories in scope
-- Extract milestone definition of done from ROADMAP.md
-- Extract requirements mapped to this milestone from REQUIREMENTS.md
-
-## 2. Read All Phase Verifications
-
-For each phase directory, read the VERIFICATION.md:
-
-```bash
-cat .planning/phases/01-*/*-VERIFICATION.md
-cat .planning/phases/02-*/*-VERIFICATION.md
-# etc.
-```
-
-From each VERIFICATION.md, extract:
-- **Status:** passed | gaps_found
-- **Critical gaps:** (if any — these are blockers)
-- **Non-critical gaps:** tech debt, deferred items, warnings
-- **Anti-patterns found:** TODOs, stubs, placeholders
-- **Requirements coverage:** which requirements satisfied/blocked
-
-If a phase is missing VERIFICATION.md, flag it as "unverified phase" — this is a blocker.
-
-## 3. Spawn Integration Checker
-
-With phase context collected:
-
-```
-Task(
-  prompt="Check cross-phase integration and E2E flows.
-
-Phases: {phase_dirs}
-Phase exports: {from SUMMARYs}
-API routes: {routes created}
-
-Verify cross-phase wiring and E2E user flows.",
-  subagent_type="cook-integration-checker",
-  model="{integration_checker_model}"
-)
-```
-
-## 4. Collect Results
-
-Combine:
-- Phase-level gaps and tech debt (from step 2)
-- Integration checker's report (wiring gaps, broken flows)
-
-## 5. Check Requirements Coverage
-
-For each requirement in REQUIREMENTS.md mapped to this milestone:
-- Find owning phase
-- Check phase verification status
-- Determine: satisfied | partial | unsatisfied
-
-## 6. Aggregate into v{version}-MILESTONE-AUDIT.md
-
-Create `.planning/v{version}-v{version}-MILESTONE-AUDIT.md` with:
-
-```yaml
----
-milestone: {version}
-audited: {timestamp}
-status: passed | gaps_found | tech_debt
-scores:
-  requirements: N/M
-  phases: N/M
-  integration: N/M
-  flows: N/M
-gaps:  # Critical blockers
-  requirements: [...]
-  integration: [...]
-  flows: [...]
-tech_debt:  # Non-critical, deferred
-  - phase: 01-auth
-    items:
-      - "TODO: add rate limiting"
-      - "Warning: no password strength validation"
-  - phase: 03-dashboard
-    items:
-      - "Deferred: mobile responsive layout"
----
-```
-
-Plus full markdown report with tables for requirements, phases, integration, tech debt.
-
-**Status values:**
-- `passed` — all requirements met, no critical gaps, minimal tech debt
-- `gaps_found` — critical blockers exist
-- `tech_debt` — no blockers but accumulated deferred items need review
-
-## 7. Present Results
-
-Route by status (see `<offer_next>`).
-
-</process>
-
-<offer_next>
-Output this markdown directly (not as a code block). Route based on status:
-
----
-
-**If passed:**
-
-## ✓ Milestone {version} — Audit Passed
-
-**Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
-
-All requirements covered. Cross-phase integration verified. E2E flows complete.
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Complete milestone** — archive and tag
-
-/cook:complete-milestone {version}
-
-<sub>/clear first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-
----
-
-**If gaps_found:**
-
-## ⚠ Milestone {version} — Gaps Found
-
-**Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
-
-### Unsatisfied Requirements
-
-{For each unsatisfied requirement:}
-- **{REQ-ID}: {description}** (Phase {X})
-  - {reason}
-
-### Cross-Phase Issues
-
-{For each integration gap:}
-- **{from} → {to}:** {issue}
-
-### Broken Flows
-
-{For each flow gap:}
-- **{flow name}:** breaks at {step}
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Next Up
-
-**Plan gap closure** — create phases to complete milestone
-
-/cook:plan-milestone-gaps
-
-<sub>/clear first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-
-**Also available:**
-- cat .planning/v{version}-MILESTONE-AUDIT.md — see full report
-- /cook:complete-milestone {version} — proceed anyway (accept tech debt)
-
-───────────────────────────────────────────────────────────────
-
----
-
-**If tech_debt (no blockers but accumulated debt):**
-
-## ⚡ Milestone {version} — Tech Debt Review
-
-**Score:** {N}/{M} requirements satisfied
-**Report:** .planning/v{version}-MILESTONE-AUDIT.md
-
-All requirements met. No critical blockers. Accumulated tech debt needs review.
-
-### Tech Debt by Phase
-
-{For each phase with debt:}
-**Phase {X}: {name}**
-- {item 1}
-- {item 2}
-
-### Total: {N} items across {M} phases
-
-───────────────────────────────────────────────────────────────
-
-## ▶ Options
-
-**A. Complete milestone** — accept debt, track in backlog
-
-/cook:complete-milestone {version}
-
-**B. Plan cleanup phase** — address debt before completing
-
-/cook:plan-milestone-gaps
-
-<sub>/clear first → fresh context window</sub>
-
-───────────────────────────────────────────────────────────────
-</offer_next>
-
-<success_criteria>
-- [ ] Milestone scope identified
-- [ ] All phase VERIFICATION.md files read
-- [ ] Tech debt and deferred gaps aggregated
-- [ ] Integration checker spawned for cross-phase wiring
-- [ ] v{version}-MILESTONE-AUDIT.md created
-- [ ] Results presented with actionable next steps
-</success_criteria>

package/commands/cook/check-todos.md

@@ -1,228 +0,0 @@
----
-name: cook:check-todos
-description: List pending todos and select one to work on
-argument-hint: [area filter]
-allowed-tools:
-  - Read
-  - Write
-  - Bash
-  - Glob
-  - AskUserQuestion
----
-
-<objective>
-List all pending todos, allow selection, load full context for the selected todo, and route to appropriate action.
-
-Enables reviewing captured ideas and deciding what to work on next.
-</objective>
-
-<context>
-@.planning/STATE.md
-@.planning/ROADMAP.md
-</context>
-
-<process>
-
-<step name="check_exist">
-```bash
-TODO_COUNT=$(ls .planning/todos/pending/*.md 2>/dev/null | wc -l | tr -d ' ')
-echo "Pending todos: $TODO_COUNT"
-```
-
-If count is 0:
-```
-No pending todos.
-
-Todos are captured during work sessions with /cook:add-todo.
-
----
-
-Would you like to:
-
-1. Continue with current phase (/cook:progress)
-2. Add a todo now (/cook:add-todo)
-```
-
-Exit.
-</step>
-
-<step name="parse_filter">
-Check for area filter in arguments:
-- `/cook:check-todos` → show all
-- `/cook:check-todos api` → filter to area:api only
-</step>
-
-<step name="list_todos">
-```bash
-for file in .planning/todos/pending/*.md; do
-  created=$(grep "^created:" "$file" | cut -d' ' -f2)
-  title=$(grep "^title:" "$file" | cut -d':' -f2- | xargs)
-  area=$(grep "^area:" "$file" | cut -d' ' -f2)
-  echo "$created|$title|$area|$file"
-done | sort
-```
-
-Apply area filter if specified. Display as numbered list:
-
-```
-Pending Todos:
-
-1. Add auth token refresh (api, 2d ago)
-2. Fix modal z-index issue (ui, 1d ago)
-3. Refactor database connection pool (database, 5h ago)
-
----
-
-Reply with a number to view details, or:
-- `/cook:check-todos [area]` to filter by area
-- `q` to exit
-```
-
-Format age as relative time.
-</step>
-
-<step name="handle_selection">
-Wait for user to reply with a number.
-
-If valid: load selected todo, proceed.
-If invalid: "Invalid selection. Reply with a number (1-[N]) or `q` to exit."
-</step>
-
-<step name="load_context">
-Read the todo file completely. Display:
-
-```
-## [title]
-
-**Area:** [area]
-**Created:** [date] ([relative time] ago)
-**Files:** [list or "None"]
-
-### Problem
-[problem section content]
-
-### Solution
-[solution section content]
-```
-
-If `files` field has entries, read and briefly summarize each.
-</step>
-
-<step name="check_roadmap">
-```bash
-ls .planning/ROADMAP.md 2>/dev/null && echo "Roadmap exists"
-```
-
-If roadmap exists:
-1. Check if todo's area matches an upcoming phase
-2. Check if todo's files overlap with a phase's scope
-3. Note any match for action options
-</step>
-
-<step name="offer_actions">
-**If todo maps to a roadmap phase:**
-
-Use AskUserQuestion:
-- header: "Action"
-- question: "This todo relates to Phase [N]: [name]. What would you like to do?"
-- options:
-  - "Work on it now" — move to done, start working
-  - "Add to phase plan" — include when planning Phase [N]
-  - "Brainstorm approach" — think through before deciding
-  - "Put it back" — return to list
-
-**If no roadmap match:**
-
-Use AskUserQuestion:
-- header: "Action"
-- question: "What would you like to do with this todo?"
-- options:
-  - "Work on it now" — move to done, start working
-  - "Create a phase" — /cook:add-phase with this scope
-  - "Brainstorm approach" — think through before deciding
-  - "Put it back" — return to list
-</step>
-
-<step name="execute_action">
-**Work on it now:**
-```bash
-mv ".planning/todos/pending/[filename]" ".planning/todos/done/"
-```
-Update STATE.md todo count. Present problem/solution context. Begin work or ask how to proceed.
-
-**Add to phase plan:**
-Note todo reference in phase planning notes. Keep in pending. Return to list or exit.
-
-**Create a phase:**
-Display: `/cook:add-phase [description from todo]`
-Keep in pending. User runs command in fresh context.
-
-**Brainstorm approach:**
-Keep in pending. Start discussion about problem and approaches.
-
-**Put it back:**
-Return to list_todos step.
-</step>
-
-<step name="update_state">
-After any action that changes todo count:
-
-```bash
-ls .planning/todos/pending/*.md 2>/dev/null | wc -l
-```
-
-Update STATE.md "### Pending Todos" section if exists.
-</step>
-
-<step name="git_commit">
-If todo was moved to done/, commit the change:
-
-**Check planning config:**
-
-```bash
-COMMIT_PLANNING_DOCS=$(cat .planning/config.json 2>/dev/null | grep -o '"commit_docs"[[:space:]]*:[[:space:]]*[^,}]*' | grep -o 'true\|false' || echo "true")
-git check-ignore -q .planning 2>/dev/null && COMMIT_PLANNING_DOCS=false
-```
-
-**If `COMMIT_PLANNING_DOCS=false`:** Skip git operations, log "Todo moved (not committed - commit_docs: false)"
-
-**If `COMMIT_PLANNING_DOCS=true` (default):**
-
-```bash
-git add .planning/todos/done/[filename]
-git rm --cached .planning/todos/pending/[filename] 2>/dev/null || true
-[ -f .planning/STATE.md ] && git add .planning/STATE.md
-git commit -m "$(cat <<'EOF'
-docs: start work on todo - [title]
-
-Moved to done/, beginning implementation.
-EOF
-)"
-```
-
-Confirm: "Committed: docs: start work on todo - [title]"
-</step>
-
-</process>
-
-<output>
-- Moved todo to `.planning/todos/done/` (if "Work on it now")
-- Updated `.planning/STATE.md` (if todo count changed)
-</output>
-
-<anti_patterns>
-- Don't delete todos — move to done/ when work begins
-- Don't start work without moving to done/ first
-- Don't create plans from this command — route to /cook:plan-phase or /cook:add-phase
-</anti_patterns>
-
-<success_criteria>
-- [ ] All pending todos listed with title, area, age
-- [ ] Area filter applied if specified
-- [ ] Selected todo's full context loaded
-- [ ] Roadmap context checked for phase match
-- [ ] Appropriate actions offered
-- [ ] Selected action executed
-- [ ] STATE.md updated if todo count changed
-- [ ] Changes committed to git (if todo moved to done/)
-</success_criteria>