--- name: checking-todos description: Use this skill when reviewing pending todos, selecting a todo to work on, filtering todos by area, or deciding what to work on next. Triggers include "check todos", "list todos", "what todos", "pending todos", "show todos", "view todos", and "select todo to work on". metadata: version: "0.1.0" user-invocable: false disable-model-invocation: false allowed-tools: - Read - Write - Bash --- \/kata:check-todos<\/user_command> 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> @.planning\/STATE.md @.planning\/ROADMAP.md <\/context> ```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 \/kata:add-todo. --- Would you like to: 1. Continue with current phase (\/kata:check-progress) 2. Add a todo now (\/kata:add-todo) ``` Exit. <\/step> Check for area filter in arguments: - `\/kata:check-todoss` → show all - `\/kata:check-todoss api` → filter to area:api only <\/step> ```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: - `\/kata:check-todoss [area]` to filter by area - `q` to exit ``` Format age as relative time. <\/step> 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> 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> ```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> **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" — \/kata:add-phase with this scope - "Brainstorm approach" — think through before deciding - "Put it back" — return to list <\/step> **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: `\/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. <\/step> 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> 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> - Moved todo to `.planning\/todos\/done\/` (if "Work on it now") - Updated `.planning\/STATE.md` (if todo count changed) <\/output> - 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> - [ ] 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>