Add session task tools for progress visibility

Integrate Claude Code's task tools (TaskCreate, TaskUpdate, TaskList)
into skills and agents to provide spinner updates during multi-step
operations like morning routines, weekly reviews, and batch processing.

- Add task tools to allowed-tools in daily, weekly, goal-tracking skills
- Add task tools to 4 agents (inbox-processor, weekly-reviewer, etc.)
- Create task-tracking.md rule with naming conventions and best practices
- Document progress patterns with concrete spinner output examples
- Update CLAUDE.md and README.md with progress visibility feature

Task tools are session-scoped progress indicators that complement (not
replace) the existing markdown checkbox system in daily notes.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Bill Allred
2026-01-23 09:59:33 -08:00
parent c2ee446009
commit 1a128f071f
10 changed files with 283 additions and 7 deletions

View File

@@ -1,7 +1,7 @@
---
name: note-organizer
description: Organize and restructure vault notes. Fix broken links, consolidate duplicates, suggest connections, and maintain vault hygiene. Use when managing vault organization or cleaning up notes.
tools: Read, Write, Edit, Glob, Grep, Bash
tools: Read, Write, Edit, Glob, Grep, Bash, TaskCreate, TaskUpdate, TaskList
model: sonnet
---
@@ -65,6 +65,27 @@ Always provide a summary of proposed changes before executing:
Wait for user confirmation before making changes.
## Progress Tracking
Track proposed changes as tasks before execution:
```
[Spinner] Scanning vault structure...
[Spinner] Identifying orphan notes...
[Spinner] Checking for broken links...
[Spinner] Auditing tag consistency...
[Done] Analysis complete (4/4 checks)
Proposed changes:
- Task: Move 3 files to Projects/
- Task: Fix 2 broken links
- Task: Consolidate 5 duplicate tags
[Awaiting confirmation]
```
Each proposed change becomes a task, giving visibility into what will be modified before confirmation.
## Integration
Works well with: