todo-write
TodoWrite-driven plan that the agent commits to before generation.
58
67%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./plugins/_official/atoms/todo-write/SKILL.mdTodo write
Before writing any artifact files, the agent commits to a numbered plan via the TodoWrite tool. The plan is the audit trail; subsequent turns either tick items off or rewrite the plan. The atom's prompt fragment teaches the agent to:
- Keep todos atomic (one verb per todo).
- Reorder freely as the picture sharpens.
- Mark a todo complete only after the matching artifact lands.
- Surface blockers as todos — never silently skip.
The Open Design daemon does not enforce a particular tool name; the agent is free to use TodoWrite (Claude Code) or an in-prompt list. The atom's job is to keep "make a plan first" in the system prompt so non-trivial workflows don't skip the planning step.
- Repository
- nexu-io/open-design
- Commit
f2760fd
- Last updated
- First committed
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.