Files
.tweakcc/system-prompts/tool-description-todowrite.md
wassname 5801e299d5 Phase 2: version conflicts, hooks, compression (+108 -179)
- Resolve 8 upstream version conflicts (bump ccVersions to 2.1.63)
- Merge askuserquestion "don't reference the plan" guidance from v2.1.47
- Move git guardrails to hooks: --no-verify, broad staging, interactive mode
- Gut redundant prompt sub-files (destructive-ops, skip-hooks, sleep, computer)
- Compress 10 system-prompt files 56% (1529w -> 672w)
- Improve context compaction summary to preserve decision path
- Update CLAUDE.md: fix principles, add Southbridge-sourced loading model

Always-loaded: ~7.5k words (down from ~10.8k stock, ~31% total reduction)

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-02 15:35:01 +08:00

1.2 KiB

Create and manage a structured task list for multi-step tasks. Helps track progress and show the user what's happening.

When to Use

  • Complex multi-step tasks (3+ distinct steps)
  • Non-trivial tasks requiring planning or multiple operations
  • User provides multiple tasks (numbered or comma-separated)
  • After receiving new instructions, capture as todos
  • When in doubt, use this tool

When NOT to Use

  • Single straightforward task (fewer than 3 trivial steps)
  • Purely conversational or informational

Task States and Management

  • States: pending -> in_progress -> completed
  • Mark in_progress BEFORE starting; mark completed IMMEDIATELY after finishing
  • ONE in_progress at a time
  • ONLY mark completed when FULLY accomplished; keep in_progress if blocked/errored
  • Remove tasks that are no longer relevant
  • Break complex tasks into smaller, actionable steps

Task descriptions must have two forms:

  • content: imperative form ("Run tests", "Fix auth bug")
  • activeForm: present continuous form shown during execution ("Running tests", "Fixing auth bug")