checking-todos

<user_command>/kata:check-todos</user_command>

Enables reviewing captured ideas and deciding what to work on next.

If count is 0:

No pending todos.

Todos are captured during work sessions with /kata:add-todo.

---

Would you like to:

1. Continue with current phase (/kata:check-progress)
2. Add a todo now (/kata:add-todo)

Exit.

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:
- `/kata:check-todoss [area]` to filter by area
- `q` to exit

Format age as relative time.

If valid: load selected todo, proceed. If invalid: "Invalid selection. Reply with a number (1-[N]) or q to exit."

## [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.

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

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" — /kata:add-phase with this scope
  • "Brainstorm approach" — think through before deciding
  • "Put it back" — return to list

Add to phase plan: Note todo reference in phase planning notes. Keep in pending. Return to list or exit.

Create a phase: Display: /kata: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.

ls .planning/todos/pending/*.md 2>/dev/null | wc -l

Update STATE.md "### Pending Todos" section if exists.

Check planning config:

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):

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]"

<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 /kata:plan-phase or /kata: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>