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

@@ -24,6 +24,7 @@ A complete personal knowledge management system that combines Obsidian's powerfu
- **📏 Modular Rules** - Path-specific conventions for markdown, productivity, projects
- **🧠 Output Styles** - Productivity Coach for accountability
- **📊 Status Line** - Vault stats in terminal (note count, inbox, uncommitted changes)
- **👁️ Progress Visibility** - See spinner updates during multi-step operations like morning routines
## 🚀 Quick Start

View File

@@ -1,7 +1,7 @@
---
name: goal-aligner
description: Analyze alignment between daily activities and long-term goals. Identify gaps, over/under-investment, and suggest rebalancing. Use for goal audits and priority checks.
tools: Read, Grep, Glob
tools: Read, Grep, Glob, TaskCreate, TaskUpdate, TaskList
model: sonnet
---
@@ -82,6 +82,22 @@ When analyzing, surface these insights:
- "You're spending 3x more time on [X] than [Y], but [Y] is ranked higher."
- "This goal has been 'in progress' for 6 weeks with no measurable advancement."
## Progress Tracking
Track multi-file analysis with session tasks:
```
[Spinner] Reading 3-year goals...
[Spinner] Reading yearly goals...
[Spinner] Reading monthly goals...
[Spinner] Scanning 7 days of daily notes...
[Spinner] Analyzing activity patterns...
[Spinner] Calculating alignment score...
[Done] Goal alignment analysis complete (6/6 steps)
```
Task tools provide visibility when analyzing the full goal cascade across multiple files.
## Integration
Works well with:

View File

@@ -1,7 +1,7 @@
---
name: inbox-processor
description: Process inbox items using GTD principles. Categorize, clarify, and organize captured notes into actionable items. Use for inbox zero and capture processing.
tools: Read, Write, Edit, Glob, Bash
tools: Read, Write, Edit, Glob, Bash, TaskCreate, TaskUpdate, TaskList
model: sonnet
---
@@ -109,6 +109,19 @@ Confirm? (y/n/modify)
4. Link to relevant goals when possible
5. Add context tags for filtering (#work, #personal, etc.)
## Progress Tracking
When processing multiple inbox items, create a task for each item to show batch progress:
```
[Spinner] Processing item 1/5: Meeting notes...
[Spinner] Processing item 2/5: Book recommendation...
[Spinner] Processing item 3/5: Project idea...
[Done] Inbox processing complete (5/5 items)
```
Task tools provide visibility into batch processing. Each inbox item becomes a session task that shows status as it's categorized and filed.
## Integration
Works well with:

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:

View File

@@ -1,7 +1,7 @@
---
name: weekly-reviewer
description: Facilitate comprehensive weekly review process. Analyze past week's daily notes, calculate goal progress, and help plan next week. Use for Sunday/Monday weekly reviews.
tools: Read, Write, Edit, Glob, Grep
tools: Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, TaskList
model: sonnet
---
@@ -79,6 +79,25 @@ When Productivity Coach output style is active, include probing questions:
- "How does next week's plan differ from patterns that didn't work?"
- "What's the ONE thing that would make everything else easier?"
## Progress Tracking
Track the 3-phase review process with task dependencies:
```
Task 1: Collect - blocked by nothing
Task 2: Reflect - blocked by Task 1
Task 3: Plan - blocked by Task 2
[Spinner] Phase 1: Collecting from daily notes...
[Done] Phase 1 complete
[Spinner] Phase 2: Reflecting on goals...
[Done] Phase 2 complete
[Spinner] Phase 3: Planning next week...
[Done] Weekly review complete (3/3 phases)
```
Dependencies ensure phases complete in order. Task tools provide visibility into the 30-minute review process.
## Integration
Works well with:

View File

@@ -0,0 +1,120 @@
---
paths: "**/*.md"
---
# Session Task Tracking Conventions
These conventions govern the use of Claude Code's session task tools (`TaskCreate`, `TaskUpdate`, `TaskList`) for providing progress visibility during multi-step operations.
## Key Distinction
**Session tasks ≠ Your actual tasks**
- **Session tasks**: Temporary progress indicators that exist only during a Claude session
- **Your tasks**: Markdown checkboxes in daily notes that persist across sessions
Session tasks show *what Claude is doing*. Markdown checkboxes track *what you need to do*.
## When to Use Session Tasks
Use session tasks for operations with 3+ distinct steps:
### Good Use Cases
- Morning/evening routines (4+ steps)
- Weekly review phases (3 phases)
- Batch inbox processing (multiple items)
- Multi-file analysis (goal cascade)
- Vault organization audits
### Skip Session Tasks For
- Single file reads/writes
- Quick lookups
- Simple edits
- 1-2 step operations
## Task Naming Conventions
### Subject (Imperative)
```
Create daily note
Pull incomplete tasks
Calculate goal progress
Process inbox item
```
### activeForm (Present Continuous)
```
Creating daily note...
Pulling incomplete tasks...
Calculating goal progress...
Processing inbox item...
```
The `activeForm` appears in the spinner while the task runs.
## Task Dependencies
Use dependencies when order matters:
```
Task 1: Collect (no dependencies)
Task 2: Reflect (blockedBy: Task 1)
Task 3: Plan (blockedBy: Task 2)
```
This ensures phases complete in sequence.
## Progress Patterns
### Sequential Steps
```
[Spinner] Step 1 of 4: Creating daily note...
[Spinner] Step 2 of 4: Pulling tasks...
[Spinner] Step 3 of 4: Surfacing goals...
[Spinner] Step 4 of 4: Setting time blocks...
[Done] Morning routine complete (4/4)
```
### Batch Processing
```
[Spinner] Processing item 1/5: Meeting notes...
[Spinner] Processing item 2/5: Book idea...
...
[Done] Inbox complete (5/5 items)
```
### Phased Work
```
[Done] Phase 1: Collect complete
[Spinner] Phase 2: Reflect in progress...
[Pending] Phase 3: Plan (blocked)
```
## Status Transitions
```
pending → in_progress → completed
```
- Set `in_progress` when starting a task
- Set `completed` only when fully done
- Never mark incomplete work as completed
## Best Practices
1. **Create tasks upfront** - Create all tasks at the start of a multi-step operation
2. **Update as you go** - Mark tasks in_progress before starting, completed after finishing
3. **Use activeForm** - Always provide spinner text for user visibility
4. **Keep it lightweight** - Don't over-task simple operations
5. **Trust markdown for persistence** - Session tasks disappear; use checkboxes for real work
## Integration with PKM
Session tasks complement but don't replace:
| Concern | Tool |
|---------|------|
| Progress during session | Session tasks (TaskCreate/Update) |
| Actual to-do items | Markdown checkboxes in daily notes |
| Goal tracking | Percentages in goal files |
| Project status | Project CLAUDE.md files |

View File

@@ -1,7 +1,7 @@
---
name: daily
description: Create daily notes and manage morning, midday, and evening routines. Structure daily planning, task review, and end-of-day reflection. Use for daily productivity routines or when asked to create today's note.
allowed-tools: Read, Write, Edit, Glob, Grep
allowed-tools: Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, TaskList
user-invocable: true
---
@@ -181,6 +181,29 @@ Organize daily notes by month/year:
Daily Notes/2024/01/2024-01-15.md
```
## Progress Tracking
The daily skill uses session tasks to show progress during multi-step routines:
### Morning Routine Progress
```
[Spinner] Creating daily note...
[Spinner] Pulling incomplete tasks from yesterday...
[Spinner] Surfacing relevant goals...
[Spinner] Setting time blocks...
[Done] Morning routine complete (4/4 tasks)
```
### Evening Shutdown Progress
```
[Spinner] Updating task statuses...
[Spinner] Generating reflection prompts...
[Spinner] Preparing tomorrow's preview...
[Done] Evening shutdown complete (3/3 tasks)
```
Task tools provide visibility into what's happening during longer operations. Tasks are session-scoped and don't persist between Claude sessions—your actual work items remain in your daily note markdown checkboxes.
## Integration
Works with:

View File

@@ -1,7 +1,7 @@
---
name: goal-tracking
description: Track progress toward 3-year, yearly, monthly, and weekly goals. Calculate completion percentages, surface stalled goals, connect daily tasks to objectives. Use for goal reviews and progress tracking.
allowed-tools: Read, Grep, Glob, Edit
allowed-tools: Read, Grep, Glob, Edit, TaskCreate, TaskUpdate, TaskList
---
# Goal Tracking Skill
@@ -119,6 +119,23 @@ When adding tasks to daily notes:
2. [Nearly complete goal - finish it]
```
## Progress Tracking
The goal tracking skill uses session tasks when generating comprehensive progress reports:
### Progress Report Generation
```
[Spinner] Reading three-year goals...
[Spinner] Reading yearly goals...
[Spinner] Reading monthly goals...
[Spinner] Scanning recent daily notes...
[Spinner] Calculating completion percentages...
[Spinner] Identifying stalled goals...
[Done] Goal progress report complete (6/6 steps)
```
This provides visibility when analyzing the full goal cascade across multiple files. Task tools are session-scoped and don't persist—your actual goal progress is tracked through markdown checkboxes and percentages in your goal files.
## Integration Points
- Weekly review: Full progress assessment

View File

@@ -1,7 +1,7 @@
---
name: weekly
description: Facilitate weekly review process with reflection, goal alignment, and planning. Create review notes, analyze past week, plan next week. Use on Sundays or whenever doing weekly planning.
allowed-tools: Read, Write, Edit, Glob, Grep
allowed-tools: Read, Write, Edit, Glob, Grep, TaskCreate, TaskUpdate, TaskList
user-invocable: true
---
@@ -163,6 +163,31 @@ Calculate habit success rates from daily notes:
- Communicate changes
- Celebrate wins
## Progress Tracking
The weekly skill uses session tasks to show progress through the 3-phase review:
### Phase Progress with Dependencies
```
[Spinner] Phase 1: Collecting daily notes...
[Spinner] Phase 1: Extracting wins and challenges...
[Done] Phase 1: Collect complete
[Spinner] Phase 2: Calculating goal progress...
[Spinner] Phase 2: Analyzing alignment gaps...
[Done] Phase 2: Reflect complete
[Spinner] Phase 3: Identifying ONE Big Thing...
[Spinner] Phase 3: Planning daily focus areas...
[Done] Phase 3: Plan complete
Weekly review complete (3/3 phases)
```
Tasks use dependencies to ensure phases run in order—Reflect is blocked until Collect completes, and Plan is blocked until Reflect completes. This provides visibility into the 30-minute review process.
Task tools are session-scoped and don't persist between Claude sessions—your actual weekly review content is saved in the review note.
## Integration
Works with:

View File

@@ -39,6 +39,18 @@ Skills are invoked with `/skill-name` or automatically by Claude when relevant.
| `goal-tracking` | (auto) | Track progress across goal cascade |
| `obsidian-vault-ops` | (auto) | Read/write vault files, manage wiki-links |
### Progress Visibility
Skills and agents use session task tools to show progress during multi-step operations:
```
[Spinner] Creating daily note...
[Spinner] Pulling incomplete tasks...
[Done] Morning routine complete (4/4 tasks)
```
Session tasks are temporary progress indicators—your actual to-do items remain as markdown checkboxes in daily notes.
## Available Agents
| Agent | Purpose |
@@ -92,3 +104,12 @@ See `CLAUDE.local.md.template` for format.
*See @.claude/rules/ for detailed conventions*
*Last Updated: 2026-01-10*
*System Version: 2.1 (Unified Skills)*
<claude-mem-context>
# Recent Activity
<!-- This section is auto-generated by claude-mem. Edit content outside the tags. -->
*No recent activity*
</claude-mem-context>