You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: replace deprecated TodoWrite with Task tools (#190)
## Description
Replace all references to the deprecated `TodoWrite` tool with the new
Task tools (`TaskCreate`, `TaskUpdate`, `TaskList`) that were introduced
in Claude Code. This update ensures the plugin-dev documentation and
commands use the current Claude Code API.
## Type of Change
- [x] Documentation update (improvements to README, CLAUDE.md, or
component docs)
## Component(s) Affected
- [x] Commands (`/plugin-dev:*`)
- [x] Documentation (README.md, CLAUDE.md, SECURITY.md)
## Motivation and Context
Claude Code replaced the `TodoWrite` tool with a new suite of Task tools
(`TaskCreate`, `TaskUpdate`, `TaskList`, `TaskGet`). This was announced
by Boris Cherny (Claude Code creator) and documented in GitHub issues
#5332 and #6891. The old `TodoWrite` tool is no longer available in
current Claude Code versions.
References:
- Boris Cherny: "We're turning Todos into Tasks in Claude Code"
- GitHub issue #5332: TodoWrite tool unavailable
- Official docs now list TaskCreate, TaskUpdate, TaskList, TaskGet
## How Has This Been Tested?
**Test Configuration**:
- Claude Code version: Current
- OS: macOS
**Test Steps**:
1. Searched for all `TodoWrite` references with `rg -n "TodoWrite"`
2. Verified all occurrences were updated
3. Ran `markdownlint` on all modified files - passed
4. Verified conceptual "todo list" references were also updated to "task
list"
## Checklist
### General
- [x] My code follows the style guidelines of this project
- [x] I have performed a self-review of my own code
- [x] My changes generate no new warnings or errors
### Documentation
- [x] I have updated the documentation accordingly (README.md,
CLAUDE.md, or component docs)
- [x] I have updated YAML frontmatter (if applicable)
- [x] I have verified all links work correctly
### Markdown
- [x] I have run `markdownlint` and fixed all issues
- [x] My markdown follows the repository style (ATX headers, dash lists,
fenced code blocks)
### Testing
- [x] I have tested the plugin locally with `claude --plugin-dir
plugins/plugin-dev`
## Files Changed
| File | Change |
|------|--------|
| `commands/start.md` | `TodoWrite` → `TaskCreate, TaskUpdate, TaskList`
in allowed-tools |
| `commands/create-plugin.md` | Updated allowed-tools + 4 conceptual
references |
| `commands/create-marketplace.md` | Updated allowed-tools + 3
conceptual references |
| `docs/workflow-security.md` | Updated tool list in design contrast
section |
| `SECURITY.md` | Updated last updated date to January 2026 |
| `.github/pull_request_template.md` | Fixed reference to non-existent
"Quick Reference section" |
## Additional Notes
The only remaining "todo" references in the codebase are:
- "TODO comment in README" (code comment placeholder, not tool-related)
- "todo app" examples (application name, not tool-related)
- CI checks for TODO comments in code
These are unrelated to the TodoWrite tool and should remain unchanged.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
---------
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
The entry point command uses `disable-model-invocation: true` and restricts tools to `AskUserQuestion, Skill, TodoWrite` since it only routes to other commands. The workflow commands need broader access because they perform the actual file creation work.
29
+
The entry point command uses `disable-model-invocation: true` and restricts tools to `AskUserQuestion, Skill, TaskCreate, TaskGet, TaskUpdate, TaskList` since it only routes to other commands. The workflow commands need broader access because they perform the actual file creation work.
@@ -15,11 +15,11 @@ Guide the user through creating a complete plugin marketplace from initial conce
15
15
-**Load marketplace-structure skill**: Use the Skill tool to load the marketplace-structure skill for schema and pattern guidance
16
16
-**Use plugin-validator agent**: Leverage the plugin-validator agent for comprehensive marketplace validation
17
17
-**Follow best practices**: Apply patterns from this repository's own marketplace.json
18
-
-**Use TodoWrite**: Track all progress throughout all phases
18
+
-**Use Task tools**: Track all progress throughout all phases using TaskCreate, TaskUpdate, and TaskList
19
19
20
20
**Initial request:** $ARGUMENTS
21
21
22
-
**Security note:** This workflow has broad file system access to create marketplace structures. It can write files and create directories within your permission scope. Review the target directory before starting, and see [docs/workflow-security.md](../../docs/workflow-security.md) for details.
22
+
**Security note:** This workflow has broad file system access to create marketplace structures. It can write files and create directories within your permission scope. Review the target directory before starting, and see [docs/workflow-security.md](../../../docs/workflow-security.md) for details.
23
23
24
24
---
25
25
@@ -29,7 +29,7 @@ Guide the user through creating a complete plugin marketplace from initial conce
29
29
30
30
**Actions**:
31
31
32
-
1. Create todo list with all 8 phases
32
+
1. Create task list with all 8 phases
33
33
2. If marketplace purpose is clear from arguments:
34
34
- Summarize understanding
35
35
- Identify marketplace type (team internal, community, single-plugin, multi-plugin)
0 commit comments